We are pleased to notify you of updates to the TIBCO Foresight Translator 3.5.0 HF1:

Closed Issues in TIBCO Foresight(r) Translator Standard and Healthcare Editions 

Release Version: 3.5.0_HF-001 (this Release)

FT-223

******IMPORTANT******

Changes required for FT-223 impact existing system behavior. Review the following

information before deploying Hotfix 3.5.0_HF-001.

Segment locking and unlocking via the Translator OutputControl rule was not being 

enforced as expected. The Java API was honoring the lock while the Translation 

tool was not, resulting in different output between the two tools. This has been 

corrected.

As part of this update, OS environment variable FS_DISABLELOCKCHECKING was added 

to allow for greater control of lock checking.

If FS_DISABLELOCKCHECKING=Y, YES, ON, or 1, lock checking is disabled.

If FS_DISABLELOCKCHECKING=N, NO, OFF, or 0, lock checking is enabled. (Default)

Note: Consult your OS documentation for information about how to edit Environment 

      Variables. For example, Windows platforms may use 

      Control Panel > System Properties > Advanced > Environment Variables 

If you are using locking via the OutputControl rule, review the following steps 

before deploying this Hotfix.

Step 1 - Run a representative sample of data through the existing maps, with 

         special emphasis on data and maps where lock/unlock and outputbyOrdinal 

         business rules are used. 

Step 2 - Deploy Hotfix3.5.0_HF-001.

Step 3 - Run the same sample of data through the updated Translator system.

Step 4 - Compare the output generated in Steps 1 and 3. 

         If the output is the same, no additional action is required.

         If the output is different, the correction made to locking behavior in 

         Hotfix3.5.0_HF-001 is exposing issues in your maps. Continue with Step 5. 

Step 5 - For testing purposes ONLY, set the operating system environment variable 

         to relax the lock: FS_DISABLELOCKCHECKING=Y, YES, ON, or 1      

Step 6 - Run the same sample of data through the Translator system.

Step 7 - If the relaxed lock method produces the expected output, a lock 

         mismatch/syntax error is present in the map. Work to correct the map.

TIBCO Foresight recommends using the relaxed lock method as a temporary 

workaround in the production environment. Once the maps have been corrected and 

are producing the desired output in the testing environment, deploy the maps to 

production.

FT-224

The ListSearch and ListSearchX rules were not allowing subrules. This has been 

corrected.

Updates can be downloaded from the TIBCO Product Support file transfer server, mft.tibco.com, using your username and password for the TIBCO Support Web.  You can use FTP, SFTP (FTP or SFTP use requires an FTP/SFTP client or command-line FTP), or your web browser at https://mft.tibco.com (requires JAVA applet support in your browser).

Once on the MFT site, downloads can be found: /AvailableDownloads/Foresight/Instream/8.5.0

Contact Us

Please direct any questions about this change to TIBCO Foresight Technical Support.
E-mail:  support@tibco.com
Web:  https://support.tibco.com 

(Note: Entry to this site requires a username and password. If you do not have one, you can request one. You must have a valid maintenance or support contract to use this site.) 

================================================================================