Release r202607
What's new
This release contains the following new features:
Sequential package execution
A checkbox has been added to the package settings to enable sequential package execution:
When this option is enabled, only one execution of a package can be processing at a time. This can be very useful, for example, when a package is handling both creates and updates of records, and you want to ensure that the creation is finished completed before the update is attempted.
To avoid clogging the queue for events triggering this package, however, we recommend that you use this feature judiciously and limit its use to short-running packages, or packages with a relatively small number of events.
Making sequential execution possible has been a major technical undertaking which includes migrating to a new queueing system. When r202607 is deployed to production, the feature will initially be switched off. After we switch to the new queueing system, which is expected to happen a few days later, the feature will become available.
Navigate between packages and libraries
We have made it easier to navigate between packages and libraries. When you place the cursor on a function that is
defined in a library used by the package and press F12, you will now be automatically taken to the function definition
in the library.
In addition, when you place the cursor on the function name in the library and press F12, a dialog will appear with a
list of references to this function across all packages that use this library:
The screenshot above shows that the library function mapPriority is referenced once by the jira-to-xurrent package
and twice by the xurrent-to-jira package.
Double click on an entry in the dialog to navigate to the corresponding location in the referencing package.
Timeline
The deployments of the release will be performed on
| Environment | Date |
|---|---|
| Demo | Friday, March 13th |
| Production | Thursday, March 19th |
| Production (Sequential package execution) | Thursday, March 26th |
The deployment of the Production environments will be conducted outside of office hours (Central European Time Zone).