Thread is blocking UI while creating job via Admin-UI
28 August 2018
The scheduler will prevent starting a new job, if there already is a job with the same ID running. E.g. if you have scheduled a task to run every 5th minute, and the execution took 7 minutes; a new job will be started on the next triggering time.
Necessary properties related to the transfer data jobs are saved to TIF DB. The transfer properties are visible when displaying a job in Admin UI.
Custom job event handler can be configured to throw exception without being ignored.
In create / update integration, object identity match can be done by object id or physical id.
Create / update integration is changed to use Saxon-HE version 9.7.0-11 that supports XPath 2.0 queries.
When the finest level of logging ("TRACE") is enabled, Create / Update integration provides more information to TIF’s log file. This might be useful for testing and development purposes.
With some ENOVIA versions, there has been some issues related to in what order a job is picked from its queue. The problem is in the ENOVIA API and to workaround this issue, a new polling strategy is available.
You can configure the default polling strategy via the ${TIF_HOME}/modules/enovia/etc/module.properties
file.
The property is named defaultQueuePollStrategy
.
Below is the list of fixed bugs as of this release.
Issue No | Description |
---|---|
431 |
Thread is blocking UI while creating job via Admin-UI |
457 |
File name encoding in REST file read operation |
453 |
Configurable REST service fails with class located under lib folder of ENOVIA module |
484 |
Inconsistent UI |