Release Notes Scribe Insight

Transcription

1 Release Notes Scribe Insight Requirements Version 7.0 and Release Date July 29, 2010 Supported Operating Systems Windows 7 Server Enterprise/Standard Editions (x32 and x64) Windows 2008 Server Enterprise/Standard Editions (x32 and x64) with Service Pack 2 Windows 2008 Server Enterprise/Standard Editions R2 Windows Vista Business Edition Service Pack 2 32bit Windows 2003 Server Enterprise/Standard Editions (x32 and x64) with Service Pack 2 Windows XP Professional with Service Pack 3 32bit Microsoft Windows components Microsoft.NET Framework 3.5 Service Pack 1 or later (the Insight installation provides you with an option for installing Microsoft.NET Framework 3.0 if it is not already installed) Microsoft IIS 6.0 if using remote connectivity to the Scribe server via web services Microsoft Message Queuing Service (MSMQ) if using publishers Database Microsoft SQL Server 2008 Microsoft SQL Server 2008 R Scribe Software Corporation Revision A / 8Sep10 1

2 Microsoft SQL Server 2005 with Service Pack 2 Microsoft SQL Server 2005 Express Edition For Scribe products, the SCRIBEINTERNAL database is supported only on Latin_General collation orders (either casesensitive or noncasesensitive). You may be required to restart the computer as part of the installation process. Please plan accordingly. You will need your Scribe Serial Number as part of the registration process. Your Serial Number can be found in the Help>About menu of the Workbench. You can also contact your Scribe Sales rep if you have any questions: sales@scribesoft.com. Release Notes Scribe Insight 7.0 and

3 Upgrade Information If you are upgrading from Insight version , you must either upgrade to Insight 6.5 before upgrading to Insight 7.0 or upgrade directly to Insight DTS files that are upgraded to Scribe Insight 7.0 or later will not be backwards compatible with previous versions of Scribe. As with any upgrade, be sure to back up any DTS files and the SCRIBEINTERNAL database before upgrading the system. If you are upgrading from Scribe Insight or and are using the GetRowError() function (OpenMind Idea #57) as part of your Update Source logic, you will need to modify the Update Source setting after upgrading. Update Source will default to update only on success; you will need to manually change it to update on success or failure. Connection Names Beginning with Scribe Insight 7.0, you have the opportunity to name connections so that you can identify a given connection in the context of all your connections. DTS files that are upgraded will default to SOURCE for the current source connection, and TARGET for the current target connection. You can rename them Release Notes Scribe Insight 7.0 and

4 to be more meaningful to you. Connection names have a 32 character maximum length. Step Names truncated to 50 characters Insight enforces a maximum step name length of 50 characters in the Workbench. Existing step names longer than 50 characters will be truncated. What s new in Version Features This release of Scribe Insight rolls up the Scribe NAV and Scribe AX adapters into a single download. Customer defects reported since Scribe Insight 7.0 were also fixed. Insight Fixes Ticket Number Description When you upgrade a DTS to 7, formulas that use functions that are upgraded (such as DBLOOKUP or SQLQUERY) AND also use a string value of S, T, or I, the string values will be changed to SOURCE, TARGET, or INTERNAL Failover related SQL files are not installed with Insight. What s new in Version Features Scribe Insight 7.0 is a direct result of feedback we received from the Scribe user community. This release focuses on broadening features and use cases for integration and migration optimizing how users define and manage connections, and allowing users to extend integrations beyond the traditional one source to one target paradigm. Release Notes Scribe Insight 7.0 and

5 Support for multiple connections (OM Idea #7) OpenMind idea #7 represents the user s ability to define more than one target system for integrations. We have expanded on that idea to allow users to create multiple connections that can be used during the integration process. The ability to leverage more than one connection opens up a whole host of opportunities for integration. Below is a list of some of the more popular solutions that are now available to users of Scribe Insight 7.0: CRM<>ERP realtime integration A common request when integrating orders from CRM to ERP is that the order total be calculated in ERP and update in CRM in a timely manner. Today, you need to create separate DTS files to accomplish this goal; daisychaining them together to have one run after another. With Scribe Insight 7.0, you will be able to create a single DTS file that leverages connections to both systems. The order can be read out of CRM, integrated in to ERP & then updated in CRM with the calculated total as a single integration event. Call Web Service for Address Verification Users have asked for the ability to call out to a web service to perform additional logic as part of integrating data between two systems. For example you may want to validate a street address or address prior to integrating customer data in to ERP. Release Notes Scribe Insight 7.0 and

6 Scribe Insight 7.0 allows you to have connections to both your ERP data and a Web Service to facilitate this realtime data cleansing. Each connection is associated with a Target step, which contains the business logic that occurs if the web service step returns a message that the supplied address is invalid. Using other connections for DBLOOKUP functions (OM Idea #66) Users often need to reference a 3 rd party system for lookup related information as part of an integration between two systems. With Scribe Insight 7.0, you will be able to create connections whose sole purpose is for use in DBLOOKUP related functions. Support more robust use cases when updating source data (OM Idea s #215 & #142) Scribe Insight has supported the ability to mark a source row as having been successfully updated. Through OpenMind idea #142, users have asked for more flexibility around how this feature works. Scribe Insight 7.0 will allow you to leverage Insight s flexible step logic to update source data; enabling you to define and multiple source columns based on step logic; or to update your source even if you used a custom query as your source data set. Create and leverage multiple Cross Reference keys in a single DTS (OM Idea #356) With Scribe Insight 7.0, you can create your own logic for Cross Reference behaviors. Users can define more than one set of cross reference keys for crossplatform synchronization or customize how keys are created to meet your customer s unique needs. Release Notes Scribe Insight 7.0 and

7 Support for Windows 2008 R2 & Windows 2007 (OM Idea #280) Both Windows 2008 R2 & Windows 2007 operating systems were released by Microsoft since the last Scribe Insight release. These two operating systems are now officially supported by Scribe, allowing you to move forward successfully without having to manually work around installation or other issues. Added Windows 2008 R2 Failover support (OM Idea #163) We have built upon our existing Failover support to include Windows 2008 R2. As with previous supported Microsoft Clustering Services configurations, the Scribe Insight Installation Guide outlines how you can configure Scribe Insight to work in this environment. Suppress the AutoForeign Key assignment (OM Idea #178) Users have asked for the ability to turn off automatic foreign key assignment, that is to not have fields that are common across multiple steps automatically linked to the same data. While this feature usually optimizes data loading, there are some scenarios where you may not want to have this optimization occur. Automatically create required MSMQ Queue s if missing (OM Idea #239) Scribe Insight will now automatically create MSMQ Queues if required by the integration process (e.g. the ScribeIn message queue). Release Notes Scribe Insight 7.0 and

8 Message Processor Management A message processor is an.exe that runs a DTS in response to an event (such as a net change in a CRM System, or a file being added to a folder, or after an elapsed period of time). We have improved how these workhorses of the integration manage themselves, with the ultimate goal of making your life easier. Don t start a Message Processor if there are not enough system resources (OM Idea #139) Users can have many Message Processors running at any given time. In some extreme cases, when there is a very large amount of data to integrate, the number of message processors became unmanageable by the host system. In Scribe Insight 7.0, Message Processors will only be started if there are enough system resources to accommodate them. Cross Reference Lookup functions were not thread safe (OM Idea #381) With multiple Message Processors running, it is possible that two message processors can simultaneously make the same request to the Cross Reference Lookup table and both respond by creating duplicate records in the target system. With Scribe Insight 7.0, Cross Reference functions (XREFLOOKUP functions) have been improved to be thread safe. Improved Upgrade Management With Scribe Insight 7.0, you will be able to review your current product versions (for the Insight core product as well as each installed adapter) and review any updates available to your installed products. Available updates will be shown with any unmet prerequisites as well. You can also view the current state of your maintenance agreement (where a valid maintenance agreement is required to register updates). Release Notes Scribe Insight 7.0 and

9 Workbench UI Enhancements Per requests logged in OpenMind, there are a couple of UI changes in the workbench. Show a Splash Screen when opening workbench (OM Idea #249) In an attempt to relieve that moment of uncertainly when you ve opened the Workbench an nothing happens, we have added a Scribe Splash Screen that lets you know that the product is in the process of opening. Test Windows remember position and size (OM Idea #306) Insight 7.0 Fixes Ticket Number Scribe Insight now remembers the size and position of the test window. You will no longer be required to reposition the window each time you open it. Description Wrong data logged in the transactionerrors table when a row fails. In certain scenarios, information from the previous row was being logged Documentation around statistical functions is misleading Upgrading Insight removes the "Logon As" user information for Scribe Services. If you have changed from the default credentials for a Scribe Service, you will be given the opportunity to record these credentials prior to uninstalling Scribe. Failing to parse XSD correctly. Only the first record of XML data was being handled by Scribe (where there were many records). Alert Notification time setting does not allow changes. Selecting Minutes was still showing Hours when you reopened the alert. Release Notes Scribe Insight 7.0 and

10 33445, , , 31417, 31373, 30976, 33349, OpenMind Forum 32653, , , CRM Adapter issue with decimal on Source on Dutch system. Format was not sensitive to regional settings. Query based IP incorrectly caches data. The Allow NULL values to overwrite data option on the Operations Tab is now selected by default when an Execute step is added. Scheduled Integrations not picking up daylight savings time changes. GP metadata views need NOLOCK option to avoid deadlock. Bridge fails unless messages are forwarded. Enhanced the filename parsing to account for other parameters from within the MIME header string that contains the filename. Workbench hangs after entering an invalid preoperation formula on Target Configure Step Control tab. Error Updating SQL table with a space in the table name. Fix was made in OLEDB Adapter. Autoretry does not work in Console with Timed Based integration. If connectivity to the database in question was lost, no attempt was made to reconnect before resetting timer. When we log errors that are longer than the 4,000 character limit, we get a ([22001] SQL call failed. String or binary data would be truncated. The statement has been terminated.) error. Changed the datatype to be SQL TEXT field vs. varchar(4000). Time based Integrations turn into Query based under the covers. Release Notes Scribe Insight 7.0 and

11 35947 Rejected Row Table issue when source table fields have spaces. We are now putting brackets around these fields /TS parameter does not work OpenMind Forum , Source Key Feature does not work consistently. 7.0 has added source keys to the transaction error log when multiple source rows are involved in the transaction XSD DateTime type does not work. Wasn t accounting for time that included seconds with decimals. %XPath does not populate a variable. 7.0 now wraps value in quotes to accommodate any spaces. GUID types are Null with OLEDB connections Error installing on 2008 R2 64 bit server. Win2k8R2 is now supported with Insight 7.0 Rejected Row table fails to create when using timestamp in tablename. BR Bank Deposit Post Execute not getting Doc Num automatically. 7.0 now uses autoforeign key with Execute steps. Bulk Insert error: DEFAULT or NULL are not allowed as explicit identity values. In 7.0, Bulk insert uses same logic as Inserts do in these cases. Insight 7.0 and Known Issues Case Number Description Files larger than 128,000 bytes are truncated when using the Native SQL Adapter. Using the OLE DB Adapter to connect to a SQL data source will resolve this issue. This issue will be considered in a future release. Release Notes Scribe Insight 7.0 and

12 22515 Large Data Types are truncated when using the Native SQL connection. A work around for this issue exists. Visit the Scribe Knowledge Base for further details: When using the Import feature to make a collaboration (with a new name) on the same Insight server on which the export was performed, if the reconnection option is selected, the import will mistakenly update the original DTS files instead of the newly imported DTS files. You can read more about this issue in the Scribe Knowledge Base at: Scribe Workbench crashes if you have different connections across DTS files; that share common names. You can read more about this issue in the Scribe Knowledge Base at: The Getting Started.pdf guide installed with Scribe Insight 7.0 is obsolete. For the most up to date version of the Installation Guide, refer to the following OpenMind link: sightinstallationguide You may get an Unable to Open Clipboard error when opening DTS on a VPC image. You can read more about this issue in the Scribe Knowledge Base at: The Performance Report summary statistic is wrong. Operationbyoperation statistics are correct; but when they are all added up they do not equal the total reported (which is wrong). This issue will be considered for a future release. Release Notes Scribe Insight 7.0 and

13 Find/Replace in Scribe Workbench yields errors. This issue will be considered for a future release. The new KeyXRef functions return a blank value vs. #NULL! when there was no values listed as part of the key. You can read more about this issue in the Scribe Knowledge Base at: Variable steps are not honoring lookup links for Insert/Update or Delete operations. This issue will be considered for a future release. Rejected Row Table will not be created if source data contains multiple fields with the same name. You can read more about this issue in the Scribe Knowledge Base at: Goldmine to CRM Migration template users will need to remap the AccountID field of the Contact entity in Dynamics CRM. AccountID was depreciated in Dynamics CRM. Use the ParentCustomerID field instead. Upgrades from previous versions of Scribe may not register functions correctly. You can read more about this issue in the Scribe Knowledge Base at: Upgrades from older versions of GP and SalesLogix adapters may cause functions to not work. You can read more about this issue in the Scribe Knowledge base at: nsdontworkafterupgrading Release Notes Scribe Insight 7.0 and

14 Exporting DTS files lists a connection as Native Unknown. This is the Scribe Internal database connection and should be marked for Ignore during import. Please view the release notes for Scribe Insight v6.5.2 ( 2ScribeInsight) for details on the previous release. Feedback Scribe is very interested in hearing about your experiences with our products and documentation. We welcome your suggestions for improvement and encourage you to use the Scribe OpenMind community at to provide feedback. OpenMind also lets you see information on upcoming product releases and engage in online discussions with Scribe product management and other Scribe users. Request a logon at end Release Notes Scribe Insight 7.0 and