------------------------------------------------ Release notes for Transaction Director Series 5.3.2 ------------------------------------------------ Copyright (c) 2004-2005 Cyclone Commerce, Inc. All rights reserved. This information supplements the user documentation. ----------------- Table of contents - What's new for 5.3.2 1. Agent permits document filtering by attribute name 2. New file store API 3. Alert actions have text file options 4. Direct uploads of aXML files allowed ------------------------------ - Known issues 1. The same document triggers multiple alerts 2. Subtracting user management authority can affect user 3. Do not delete a document type in a report 4. On UNIX copy aXML Agent install files to the computer 5. Manually set up server parsing of large XML documents 6. System sometimes cannot generate reports 7. Do not run DB2, Transaction Director on same computer 8. Do not use large sample documents with XPath wizard 9. Search details may not display as expected 10. Document resubmit works on second try ------------------------------ - 5.3.2 resolved issues 1. Socket connections in Close Wait or Time Wait state 2. Incorrect loop parsing 3. Agent tried to consume large files before fully written 4. Minimum set at 5 seconds for SLA alert schedules 5. Agent tuned to improve performance 6. User names now have unique IDs 7. Spurious agent events suppressed ------------------------------ - What's new for 5.3 1. Print buttons for reports added to UI 2. Alert rules can be made active or inactive 3. Transaction search performance improved 4. SLA alert notifies which rule condition failed 5. Filestore directory rolls according to date, time 6. Action attribute can perform lookup action 7. Splitting ignores excess characters after last segment ------------------------------ - 5.3.1.0.12 resolved issues 1. Unexpected returns, characters affected processing 2. Parent documents displayed improperly 3. Document type for split documents dynamic ------------------------------ - 5.3.1.0.10 resolved issue 1. Detail parser ignored small documents ------------------------------ - 5.3.1.0.7 resolved issues 1. directResubmit tool did not work on UNIX 2. Updating lifecycle page could lead to faulty result 3. Extra character added when splitting EDIFACT document 4. Invalid segment in EDI document caused splitting loop 5. XML document could be lost when split from original 6. XML document rejected after splitting failed ------------------------------ - 5.3.1.0.5 resolved issues 1. Searching by time adjusted for daylight savings time 2. Bind IP addresses control was not working ------------------------------ - 5.3.1.0.2 resolved issues 1. Server generated names too long for Oracle 2. Detail parser could not parse single line flat file 3. Endless splitting of batch documents resolved 4. "Remember my user ID" check box persists setting 5. Flat files displayed without line breaks 6. Alert processing performance improved 7. EDI splitter can handle larger documents 8. Documents got stuck in agent and could not upload ------------------------------ - 5.3.0.0.1 resolved issues 1. EDI documents with 80-column widths did not split 2. First split ST segment erroneously discarded 3. Partner status alert generated in error 4. Trailing spaces caused detail parser rule to fail 5. Parsing an already parsed value caused exception 6. EDI document could not be viewed in text format 7. Milliseconds display on transaction lifecycle page 8. Primary keys added to all database tables 9. Different EDI separators caused splitting errors ------------------------------ - What's new for 5.2 1. Filters can be assigned to many users at once 2. Lifecycle view allows "and" conditional search 3. Detail parser handles EDI, Idocs and flat files 4. Easier upgrades 5. Web service allows access by third-party applications ------------------------------ - 5.2.0.0.16 resolved issue 1. Detail parser failed to operate ------------------------------ - 5.2.0.0.12 resolved issues 1. Detail parser performance improved 2. Plain, formatted document display views available 3. CRLF supported as separator in EDI documents ------------------------------ - 5.2.0.0.11 resolved issues 1. Uploaded documents could become stuck in process 2. Search values can contain special characters 3. Server put two documents in filestore instead of one 4. Documents with different separators did not split 5. Linking by document type displayed improperly ------------------------------ - 5.2.0.0.6 resolved issue 1. Node status incorrectly shown on system management page ------------------------------ - 5.2.0.0.5 resolved issues 1. Agent used lower case filename attribute for MQ, JMS 2. Agent may write temporary files to bin directory ------------------------------ - 5.2.0.0.3 resolved issues 1. Transaction configuration permission caused UI error 2. Document uploads were allowed with wrong node 3. Purging did not completely remove records 4. Limited user sessions could affect processing 5. Document type was blank in e-mailed reports 6. Views of unformatted EDI payloads were inconsistent 7. Payloads of split documents could not be viewed ------------------------------ - 5.2.0.0.2 resolved issue 1. EDI splitting was not working properly ------------------------------ - 5.2.0.0.1 resolved issues 1. Document upload processing stalled 2. EDI payloads did not display in formatted views ------------------------------ - What's new for 5.3.2 ------------------------------ ----------------------------------------------------- 1. Agent permits document filtering by attribute name A properties file has been added to the agent that lets you filter out documents you do not want to upload to the server based on attribute names and values. For example, you can exclude uploading any document containing the name- value pair Sender = CompanyA. The properties file to use is FilterByAttribute.properties in the agent's conf directory. 21037 --------------------- 2. New file store API A new file store API allows you to use a third-party application for file storage in lieu of the standard filestore directory. Sample Java code is at [install directory]\[build number]\samples\director. 20536 ---------------------------------------- 3. Alert actions have text file options When setting up an alert action to write a text file, more options have been added for how the file is produced. These options are: a. For each occurrence of the alert, append it to the specified file. b. For each occurrence of the alert, overwrite the specified file. c. For each occurrence of the alert, create a new sequentially named file based on the specified file. d. For each occurrence of the alert, create a new uniquely named file. 20645 --------------------------------------- 4. Direct uploads of aXML files allowed A directory has been added to the agent that lets you add already formatted aXML files for upload to the server. This allows you to bypass the agent's aXML packaging step. The new directory is named axmlonlyupload. 20953, 20952 ------------------------------ - Known issues ------------------------------ --------------------------------------------- 1. The same document triggers multiple alerts Alerts that trigger according to a schedule can result in duplicate alerts being produced for the same document, even one that entered the system some time ago. This does not occur when an alert is configured to check documents upon entering the system, rather than using a schedule. 9104 -------------------------------------------------------- 2. Subtracting user management authority can affect user If a user with a role that allows user management changes to a role without such authority, the user no longer can navigate in the user interface. An administrative user should make this type of role change for the user. 8920 -------------------------------------------- 3. Do not delete a document type in a report After configuring a report, do not delete any document types upon which the report is based. If you do so, you cannot change or delete the report. Before deleting a document type, change the report configuration so the report no longer relies on it. 9134 -------------------------------------------------------- 4. On UNIX copy aXML Agent install files to the computer If you are installing aXML Agent on a computer with a UNIX operating system and are using an installation CD, copy the files from the CD to a directory on the UNIX computer before proceeding. 9156 -------------------------------------------------------- 5. Manually set up server parsing of large XML documents Using the user interface controls, you might not be able to set up XPaths for parsing attributes of XML documents that are approximately 1 megabyte or larger in size. If this occurs, see the user documentation for configuring server parsing with the manual method. 9592 ------------------------------------------- 6. System sometimes cannot generate reports The system sometimes cannot generate reports. This can occur when the system must process a large number of records or report a large number of attributes or both. 9304 -------------------------------------------------------- 7. Do not run DB2, Transaction Director on same computer When the platform is AIX, do not run the DB2 database and Transaction Director on the same computer. Transaction Director cannot connect to the database. Instead run DB2 and Transaction Director on separate computers. 9204 ------------------------------------------------------ 8. Do not use large sample documents with XPath wizard The XPath wizard in the user interface cannot be used when the sample XML document is large (1 megabyte or more). As a work-around, use a smaller sample document with the XPath wizard or manually configure server parsing by following the instructions in the user manual. 9592 --------------------------------------------- 9. Search details may not display as expected After performing a search and clicking to view a document's details, the system may not return information about all related documents and generate an error. 9779 ----------------------------------------- 10. Document resubmit works on second try If you resubmit a rejected document, the first attempt to do so does not work, but the second attempt does. 9847 ------------------------------ - 5.3.2 resolved issues ------------------------------ ------------------------------------------------------ 1. Socket connections in Close Wait or Time Wait state The agent often would not close socket connections after uploading documents to the server. This resulted in many sockets in a Close Wait or Time Wait state. This issue has been resolved so that sockets are closed within 1 minute of inactivity. 20746 ------------------------- 2. Incorrect loop parsing When performing loop parsing, some values were parsed incorrectly after the loop was reset. This issue has been resolved. 20577 ---------------------------------------------------------- 3. Agent tried to consume large files before fully written In the case of large documents written to the agent's data directory, the agent tried to consume the files before they were fully written to the directory. This resulted in such files failing to process. This has been resolved by implementing a fix that ensures the agent does not consume files until fully written. 20749, 20632 --------------------------------------------------- 4. Minimum set at 5 seconds for SLA alert schedules SLA alert scheduling has been changed so SLA alerts cannot be set to trigger at less than 5-second intervals. If you try to set a shorter time, a message displays that the time is invalid. This change was made after it was found that setting an interval of 0 seconds resulted in an alert never triggering. 20499 ------------------------------------- 5. Agent tuned to improve performance A number of tuning changes have been made to the uploading agent to improve performance in processing large documents and large volumes of documents. 20710 --------------------------------- 6. User names now have unique IDs Unique IDs are assigned to user names to enable the system to distinguish between users who have the same user name. 20540 ----------------------------------- 7. Spurious agent events suppressed The JMX logic included from the common.jar produced INFO and ERROR events upon starting the agent because JMX configuration files by design are not included in the agent conf directory. These spurious events caused no harm, but have been suppressed to avoid confusion. 20644 ------------------------------ - What's new for 5.3 ------------------------------ ---------------------------------------- 1. Print buttons for reports added to UI Buttons that let users print reports have been added to the user interface. 10620 --------------------------------------------- 2. Alert rules can be made active or inactive After defining an alert rule, the rule can be enabled or disabled, depending on whether a user wants the rule to be active. 10607 ------------------------------------------ 3. Transaction search performance improved The performance of the transaction search page has been improved so that search results are returned faster. 11191 ------------------------------------------------- 4. SLA alert notifies which rule condition failed For a text message for an SLA alert, you can use a code that extracts an unmet condition in the alert rule and makes it part of the message. This can be helpful when rules have multiple conditions and you want to trace the condition that was not met. The code to use is {AlertCondition}. 10596 ---------------------------------------------------- 5. Filestore directory rolls according to date, time The filestore directory creates subdirectories by date and time to better organize stored documents. The subdirectories are created in the order of year, month, day, time. 10694 --------------------------------------------- 6. Action attribute can perform lookup action With the detail parser, the ability to supply an action attribute for performing a lookup action has been added. The following is a sample rule to illustrate how this works. 854.Attribute3.Name = ID 854.Attribute3.Segment = ISA 854.Attribute3.StartPosition = 7 854.Attribute3.Parseable = Y 854.Attribute3.OverWrite = N 854.Attribute4.Name = Receiver 854.Attribute4.Segment = ISA 854.Attribute4.StartPosition = 8 854.Attribute4.Action = CONCAT 854.Attribute4.ActionAttribute = ID 854.Attribute4.Parseable = Y 854.Attribute4.OverWrite = N 854.Attribute5.Name = ReceiverId 854.Attribute5.Segment = ISA 854.Attribute5.Action = PARSELOOKUP 854.Attribute5.LookupFile = LookupFile.properties 854.Attribute5.ActionAttribute = Receiver 854.Attribute5.Parseable = Y 854.Attribute5.OverWrite = N The following is the flow of this rule. 1. The value of the ID attribute is parsed from the ISA segment element 7. For example, say the parsed value is "ZZ". 2. The value of the Receiver attribute is parsed from the ISA segment element 8. For example, say the parsed value is "Acme". That value is concatenated with the value of the ID attribute to become "ZZAcme". 3. Upon reaching the rule for the ReceiverId attribute, the action attribute of Receiver directs the parser to take the Receiver value of "ZZAcme" and look up the matching value in the lookup.properties file. For example, say the matching value is "Acme Store #1". That is the value that gets assigned to the Receiver attribute. 20559 --------------------------------------------------------- 7. Splitting ignores excess characters after last segment Splitting has been improved so that excess characters after the last valid document segment are ignored. This results in fewer documents being rejected when invalid characters are encountered. 20877 ------------------------------ - 5.3.1.0.12 resolved issues ------------------------------ ----------------------------------------------------- 1. Unexpected returns, characters affected processing Documents were failing to correctly parse or split when the server encountered unexpected carriage returns, special characters or excess characters at the end of a document. This issue has been resolved so processing occurs successfully. 20993 ---------------------------------------- 2. Parent documents displayed improperly When viewing many original, unsplit parent documents as plain text with link breaks in the user interface, the documents did not display properly. This issue has been resolved. 20995 -------------------------------------------- 3. Document type for split documents dynamic In the detail parser, the DetailDocType was static, so that all split documents had the same document type. This has been changed so that DetailDocType can be set to any attribute, making the document type dynamic for split documents. 21018 ------------------------------ - 5.3.1.0.10 resolved issue ------------------------------ ---------------------------------------- 1. Detail parser ignored small documents Small but valid documents of 200 bytes or less were ignored by the detail parser. This issue has been resolved. 20892 ------------------------------ - 5.3.1.0.7 resolved issues ------------------------------ ------------------------------------------- 1. directResubmit tool did not work on UNIX The directorResubmit tool did not work on UNIX because of an error in the UNIX script. This issue has been resolved. 20694 ------------------------------------------------------ 2. Updating lifecycle page could lead to faulty result Updating the view on the transaction lifecycle page after selecting multiple common attributes for an "or" condition could result in faulty search results. This issue has been resolved. 20771 -------------------------------------------------------- 3. Extra character added when splitting EDIFACT document Splitting an EDIFACT document at the UNG segment resulted in an extra character being added to the new UNG segment of the split document. This issue has been resolved. 20782 -------------------------------------------------------- 4. Invalid segment in EDI document caused splitting loop If an EDI document being split had invalid segments, the document was split over and over again. To resolve this, the splitter now checks whether the last segment is invalid, missing, too long or has too many separators. If so, an exception is produced that the document cannot be split. 20794 ------------------------------------------------------ 5. XML document could be lost when split from original When splitting an XML document, a child document could be lost. This has been corrected so that all documents split from the original batch document are preserved. 20833 ----------------------------------------------- 6. XML document rejected after splitting failed When an XML document was uploaded, the system tried to split it, regardless whether it needed to be split. If the system could not split the document, the document was rejected. This has been resolved so that XML documents are correctly handled. 20825 ------------------------------ - 5.3.1.0.5 resolved issues ------------------------------ ------------------------------------------------------- 1. Searching by time adjusted for daylight savings time Searches using date and time conditions were not returning records with the times being sought. This issue has been resolved to account for daylight time zone differences. 20552 -------------------------------------------- 2. Bind IP addresses control was not working A system properties control in the user interface did not work. This control lets you bind all IP addresses to CYC_NETWORK_NAME rather than to all IP addresses on all network interfaces. This issue has been resolved. 20579 ------------------------------ - 5.3.1.0.2 resolved issues ------------------------------ --------------------------------------------- 1. Server generated names too long for Oracle The server was generating names referencing database tables that were too long for an Oracle database to handle. This issue has been resolved. 20118 ------------------------------------------------------ 2. Detail parser could not parse single line flat file The detail parser could not parse a flat file with a single record line and without carriage return or line feed at the end of the line. This issue has been resolved. 20212 ------------------------------------------------ 3. Endless splitting of batch documents resolved In rare instances, batch documents would split endlessly, causing the filestore directory to fill. This issue has been resolved. 20311 --------------------------------------------------- 4. "Remember my user ID" check box persists setting The "remember my user ID" check box on the log on page of the user interface was always selected, even after clearing the box. This has been resolved so the option always displays as checked or unchecked, depending on the last action. 20094 ------------------------------------------- 5. Flat files displayed without line breaks When viewed in the user interface, uploaded flat files were displayed without line breaks. This issue has been resolved. 20278 ---------------------------------------- 6. Alert processing performance improved Alert processing performance has been speeded up significantly. 20381, 11308 ------------------------------------------- 7. EDI splitter can handle larger documents The server's EDI splitter could not split EDI documents larger than 25 megabytes. The splitter has been changed to handle documents as large as 2 gigabytes. 20411 ---------------------------------------------------- 8. Documents got stuck in agent and could not upload When running as a Windows service, the agent application sometimes stopped processing with documents in the queue. This issue has been resolved by increasing the heap memory size. 20340 ------------------------------ - 5.3.0.0.1 resolved issues ------------------------------ ---------------------------------------------------- 1. EDI documents with 80-column widths did not split EDI documents with 80-column width formats failed to split. This issue has been resolved. 10638 ----------------------------------------------- 2. First split ST segment erroneously discarded For EDI documents requiring splitting, the first split ST segment was being discarded. This has been resolved so the correct number of documents is split from an original batch document. 10644 ------------------------------------------ 3. Partner status alert generated in error A partner status alert was generated when a document satisfied the alert rule condition. This issue has been resolved. 10691 ---------------------------------------------------- 4. Trailing spaces caused detail parser rule to fail Trailing spaces in a rule for the detail parser caused the rule to fail. This has been resolved by allowing trailing spaces, which the parser trims upon executing the rule. 10788 --------------------------------------------------- 5. Parsing an already parsed value caused exception When using the detail parser, if a rule was set to false for overwrite and the parser encountered an already parsed value, an exception occurred and the last defined attribute was not parsed. This issue has been resolved. 10791 -------------------------------------------------- 6. EDI document could not be viewed in text format An EDI document could not be displayed in plain text format in the user interface. This issue has been resolved. 11416 ----------------------------------------------------- 7. Milliseconds display on transaction lifecycle page On the transaction lifecycle page in the user interface, milliseconds now are reported as part of the time interval between documents in a transaction. This does not occur, however, when Oracle is the database; Oracle reports milliseconds as "000". 10515 -------------------------------------------- 8. Primary keys added to all database tables Modifications have been performed to make sure all database tables have primary keys and indexes. 10199 --------------------------------------------------- 9. Different EDI separators caused splitting errors In a multi-part interchange EDI document if the separators in the different ISA segments, the splitter did not split the files correctly. This issue has been resolved. 10908 ------------------------------ - What's new for 5.2 ------------------------------ ------------------------------------------------ 1. Filters can be assigned to many users at once Filters can now be assigned to roles as well as users. Previously, filters could be assigned only to users. The ability to assign filters to roles lets administrators to assign filters to many users at once. ------------------------------------------------- 2. Lifecycle view allows "and" conditional search In the transaction lifecycle view in the user interface, you can focus searches on documents that contain the same values for two attributes. This new "and" search ability extends the earlier "or" ability to search on documents that contain values for either of two attributes. Now you can use both options. -------------------------------------------------- 3. Detail parser handles EDI, Idocs and flat files A detail parser has been added for splitting and extracting attribute values from complex EDI documents as well as Idocs and flat files. The new parser combines the functionality of separate earlier parsers. Supported EDI documents are X12 and EDIFACT. ------------------ 4. Easier upgrades Upgrading has been made easier with enhancements to the installation wizard. See the user documentation for details about upgrading. -------------------------------------------------------- 5. Web service allows access by third-party applications Transaction Director has an optional web service API that enables a back-end system to search the database for records and retrieve payloads from the file store. There are two services: a. SearchRequest service has two methods that allow a search to be performed and to return one or more documents with attributes. b. PayloadRequest service will return a specific payload. 10324 ------------------------------ - 5.2.0.0.16 resolved issue ------------------------------ ---------------------------------- 1. Detail parser failed to operate When a document was submitted via integration with the trading engine, the detail parser did not work even though it was properly configured. This issue has been resolved. 11427 ------------------------------ - 5.2.0.0.12 resolved issues ------------------------------ ------------------------------------- 1. Detail parser performance improved The speed at which the detail parser can split and parse large EDI documents has been increased significantly. For example, a 5 megabyte document now takes several seconds. 11198 ---------------------------------------------------- 2. Plain, formatted document display views available When setting up a document type, a user can choose whether to view upload documents as plain or formatted text. This preference becomes the default view when a user searches for and views an uploaded document in the transaction search area. 11224 ----------------------------------------------- 3. CRLF supported as separator in EDI documents EDI documents could not be processed when CRLF was used as a separator in addition to a normal separator character. This issue has been resolved. 11228 ------------------------------ - 5.2.0.0.11 resolved issues ------------------------------ --------------------------------------------------- 1. Uploaded documents could become stuck in process When operating in a high-volume environment, roughly 1 in 10,000 documents could become stuck in process while uploading. This issue has been resolved. 10896 ----------------------------------------------- 2. Search values can contain special characters Searches for attribute values that included special characters such as % failed. This has been resolved so that searches can include non-alphanumeric characters such as %, &, $ and so on. 11012 ------------------------------------------------------- 3. Server put two documents in filestore instead of one When uploading documents from aXML agent, the server would write two documents to the filestore directory rather than just one. This issue has been resolved. 11071 ---------------------------------------------------- 4. Documents with different separators did not split EDI batch documents that contained different separators failed to split. This issue has been resolved. 11074 ------------------------------------------------ 5. Linking by document type displayed improperly Linking documents by document type did not display correctly in the transaction lifecycle view in the user interface. This issue has been resolved. 11084 ------------------------------ - 5.2.0.0.6 resolved issue ------------------------------ ---------------------------------------------------------- 1. Node status incorrectly shown on system management page The system management page could display the incorrect status of a node when operating in a cluster. For example, the page might report a running node as not running. This issue has been resolved. 10360 ------------------------------ - 5.2.0.0.5 resolved issues ------------------------------ ------------------------------------------------------- 1. Agent used lower case filename attribute for MQ, JMS When JMS or MQSeries were used for aXML Agent integration, the agent was writing the file name of payloads to property files using the lower case attribute "filename" rather than the correct camelcase form of "FileName." This issue has been resolved. 10642 --------------------------------------------------- 2. Agent may write temporary files to bin directory aXML Agent sometimes wrote temporary files to the agent's bin directory while uploading payloads. This issue has been resolved. 10660 ------------------------------ - 5.2.0.0.3 resolved issues ------------------------------ ------------------------------------------------------- 1. Transaction configuration permission caused UI error When a role that allowed only use of the transaction configuration permission was assigned to a user, the user interface did not display properly. This issue has been resolved. 9063 ------------------------------------------------ 2. Document uploads were allowed with wrong node With a user license that authorized both Transaction Director and the trading engine, the Transaction Director document upload wizard erroneously allowed uploads when only a trading engine node was running. This issue has been resolved. 9648 -------------------------------------------- 3. Purging did not completely remove records Records of purged documents were not removed completely from the database or deleted from the filestore directory. This issue has been resolved. 10033 ------------------------------------------------ 4. Limited user sessions could affect processing If a user license supported five or fewer concurrent user sessions for logging on to the user interface, some processes, such as alert generation, were not executed. This was because the system used multiple user sessions for its own purposes, contributing to the possibility that the session limit was reached. This issue has been resolved to allow as many user sessions as the license supports. 10046 ---------------------------------------------- 5. Document type was blank in e-mailed reports When a scheduled report was sent by e-mail, the document type field was blank for all records. This issue has been resolved. 10087 ------------------------------------------------------ 6. Views of unformatted EDI payloads were inconsistent Viewing of unformatted EDI payloads with line breaks worked inconsistently. This issue has been resolved. 10516 -------------------------------------------------- 7. Payloads of split documents could not be viewed Payloads of split documents could not be viewed in the user interface. This issue has been resolved. 10524 ------------------------------ - 5.2.0.0.2 resolved issue ------------------------------ ----------------------------------------- 1. EDI splitting was not working properly The embedded EDI splitter was not properly splitting multi- interchange documents, resulting in the server rejecting the split documents. This issue has been resolved. 10556 ------------------------------ - 5.2.0.0.1 resolved issues ------------------------------ ------------------------------------- 1. Document upload processing stalled After uploading 100 or more documents, the server would stop processing, generating an NoSuchElementException error. This issue has been resolved. 10468 -------------------------------------------------- 2. EDI payloads did not display in formatted views EDI payloads sometimes did not display properly in formatted views in the user interface. This issue has been resolved. 10477, 10487 ----------------- End release notes -----------------