On Monday December 12th, the IDE/DV/QA environments for Platform1, Platform2, Platform3, and Platform4 will be upgraded to DesignTime Revision 2484 and RunTime Revision 1140. Platform1, Platform2, and Platform4 will begin their upgrade at 3:00PM CST with an expected completion time of 3:30PM CST. Platform3 will begin its upgrade at 12:00PM CST with an expected completion time of 12:30PM CST.
On Wednesday December 14th, the PD environment for Platform1, Platform2, Platform3, and Platform4 will be upgraded to RunTime Revision 1140. Platform1, Platform2, and Platform4 will begin their upgrade at 3:00PM CST with an expected completion time of 3:30PM CST. Platform3 will begin its upgrade at 12:00PM with an expected completion time of 12:30PM CST.
DesignTime
Revision 2475: Trim Service and Functions
- Added a new service called Trim to the Data Conversion workshop which lets the user set the trim mode and trim a value.
- Added three new EASYProcess functions called Trim, LTrim, and RTrim to trim values respective sides.
- Brought the Adyen Workshop and services over to EASYProcess 5.1 by removing the existing records and updating them with newer services.
- The _LoopNode node in the Assistant tab for Loop canvas's does not always load. Proper checks have been added to determine if the node is loaded at different points and only load it if it isn't loaded already.
- The DataSize amount and TripsTaken now show up in the ECCLog node of the ECC service.
- Added a sort query on return of the table names to confirm that they are always sorted.
- When a ECC database service has an invalid table and the user opens the QueryBuilder it would timeout and freeze the page. Added code to throw an error immediately and not timeout and freeze the page.
- The Notify service's parameters node is showing like a CallMethod/CallSubMethod/Loop parameters node instead of as a normal node. The Notify service has been added into a check before setting up the custom parameters node.
- The "Run Process Till Selected" icon in the service editor has been removed and now solely displays on the main canvas.
- The run icons in the Logic Canvas have been cleaned up and changed slightly to better represent the action they are doing.
- The "Run" icon has not changed.
- The " Run Process In Steps" icon has changed to be the old "Run Process Till Selected" icon.
- The "Run Process Till Selected" icon has been changed to the seek forward icon of two triangles and a vertical line.
- The BatchJob Services workshop has deprecated a few services and added a few additional ones. The Get Current Status, Get Status, and Update Status services have been deprecated and replaced with the Read History and Write History services. These two services have been simplified for easy use with the Write History service only usable inside a BatchJob and it's attached logic and the Read History service usable anywhere and takes the BatchJob's name.
- The Write History service takes the following inputs:
- Message: A message appended to the existing message for the BatchJob run.
- ResetMessage: A True/False value defaulting to False indicating whether or not to reset the existing message for the BatchJob run.
- ProcessedCount: A number indicating how many records have been processed so far in the BatchJob.
- ResetProcessedCount: A True/False value defaulting to False indicating whether or not to reset the existing message for the BatchJob run.
- Services nodes that are arrays in arrays like the Format service and the Merge Targeted Nodes service don't get the click event to select the nodes on creation. Users must exit the service and reopen. And else statement has been added to catch these type of service nodes and add the proper event on creation.
- Methods with two services with the same name that are exposed cause the Recommended Values Name output for the CallMethod service to break and fails to show that name. The original check has been expanded to see whether a name has already been added or not to the Recommended values list.
RunTime
Revision 1139: Workflow Run Mode Auto Fix
- When a workflow status is in Run Mode = Auto any errors stop the logic and don't throw an error to the logs. This prevents others issues like ECC failing in these status events and CallMethod output issues from writing to logs.