Release Information

Release Information - Version 1.12

Administration UI Improvements

General Improvements

Most dialogs are now displayed in a modal drawer to improve rendering and take advantage of vertical space.
UI containers have been updated to use the outlined variant of form fields.

Improvements to Job Filter Screen

There is now a button for resetting all job filters. The reset button is available on the screen where job filters are selected.

Job filter fields now also include a clear button for the selected value.

In addition, a number badge is displayed on each tab to indicate the number of currently selected filters.

Scheduled Task Groups

The creation of scheduled task groups is moved, see screenshot below.

Figure 1. Create Scheduled Task Group

Job Progress - Paginated View

A pagination control is now shown on the Job Progress screen when there are many log items to display.

Job Execution Logging

During the execution of a Job, the logger may be used too excessive. As of this release, if the logging data exceeds one or both of the below criteria, the logging in the UI is suspended and the complete log is attached as a file to the Job instead.

Maximum nr of log entries: 150
Total nr of characters logged: 100k

In the Administration UI, if the log is exhausted it will indicate so like below:

Figure 2. Exhausted Logger

The complete log is attached to the job as a file.

Figure 3. Attached Log

If a single log message exceeds 1k characters, it will be truncated.

Job Archivation

Starting from this release, completed jobs that are older than 3 months will be marked as obsolete / archived. That means, these will not appear in the job table within the Administration UI per default. To display these, one needs to use the filter dialog to show these.

Figure 4. Job Filter Dialog Options

Jobs will stay in the archive for an additional 3 months before they finally are tided up.

REST Mapping Changes

The changes related to the REST mappings and invocation of a job through REST are mentioned below.

Wait Timeout

The setting 'Wait Timeout' on the REST Mapping entities has been removed as it is no longer used or needed.

Synchronous Execution vs Paused Service

If a REST mapping is configured for synchronous execution but the Service that it’s using is paused, the requester will get a status 503 (Service Unavailable) response.

Executor API Improvements

Resolve Source Object

When a Job is triggered via an event, the source object information is normally part of the DS Event data, and by so the Job is associated with a source object automatically.

However, when invoked via a REST call, the source object which the job is operating on is not known. As of this release, the executing code can manually set the source object for the Job by using the below API:

context.jobAPI()
    .setSourceObject(id, type, name, revision, state, extraInfo);

Mark Failed Jobs as Resolved

In case a job is failing, the executing logic may in some cases determine the reason automatically. In such cases, the code can also set the resolved flag with the resolution as part of the execution.

The API to use for this is shown below:

context.result()
    .failed(true)
    .markResolved(true, 'This is the resolution of the problem');

Delays

In some cases, a need for applying some delays in the execution may be needed.

To support this, a new method called sleep on the ExecutionContext has been added. However, there are some rules to be aware of:

You can never sleep for more than 30 seconds at a time.
Calling the sleep repeatedly is possible, but the total sleep time may not exceed 5 minutes.

If the rules above are not followed, an exception will be raised and the job execution will be terminated.

Usage example:

context.sleep(10000); // sleep for 10 seconds

Other Improvements or Fixes

On the Job summary view, a direct link to the main configuration has been added
Fix issue related to changing the tenant URLs on the cloud settings page