Release Information

Release Information - Version 1.13

Job Trigger - Allow Pause Service

A new option have been added to a Job trigger, which can be used to pause a service when some specific failure occurs.

This could be used to handle problems early and avoid processing a lot of Jobs when for example there is a connectivity problem with the remote system. Pausing the service will put the jobs on hold until the issue can be resolved.

job trigger pause service
Figure 1. Pause Service Option

Stop Running Job

A new option to request interruption of a running Job has been added.

If the job is running, the job progress view will show a Stop button.

stop job
Figure 2. Send Stop Request

Clicking this will open a confirmation dialog.

confirm stop
Figure 3. Confirm Stop Request

Once confirmed, the Stop request is sent and if the current Job type supports interruption it will be interrupted and the job status will be set to Failed.

job stopped
Figure 4. Job Stopped

Cancel Waiting Job

A job that is in the state Waiting, will get a new button visible on the Job progress page. This button allows the user to cancel the Job request.

cancel job
Figure 5. Cancel Job

Once clicked a confirmation dialog will be shown.

confirm cancel
Figure 6. Confirm Cancel Request

If confirmed, the Job will be cancelled.

Triggering a Job via REST

When triggering a Job via a synchronous REST call, some new response headers have been added to give the caller some more information of the execution status.

These are:

TIF-Job-Status-Code

Contains the job exit/status code

TIF-Job-Status-Message

Contains the job result message

Long Running Jobs

In order to prevent jobs from getting stale or stuck, a limit of how long a job can be running is now introduced. This limit is set to 2h and if a job is executing for longer time than this, it will be stopped.

A Job that has been triggered via a synchronous REST call will not be allowed to run for more than 10 minutes.

Replay 3DX Event

Within the table showing the 3DX events received (Monitor → DSX Source Event Table), a new function have been added that allows replaying a past event.

replay dsx event
Figure 7. Replay Event

Java Script API

Http API - Save/Use Cookies

The HTTP API have been enhanced allow configuring to use/save cookies.

This is enabled by calling the useCookies(true) method when configuring the Http Client, like shown below:

const request = context.httpAPI()
    .newRequestBuilder()
    .post(mqConnectionProps.baseURL + mqConnectionProps.loginEndpoint)
    .useCookies(true) (1)
    .jsonBody(JSON.stringify({
        "username": userName,
        "password": password
    }))
    .build();
1 Enable cookies, e.g. save any cookies returned OR send cookies valid for the domain

JSON Path Evaluation

The JSON API have been extended to allow evaluating JsonPath expressions on some arbitrary object.

This API can be used like the example below:

const jsonPath = context.jsonAPI().jsonPath(engItem);
let partNumber = jsonPath.evaluate("$['dseng:EnterpriseReference']['partNumber']");
if (partNumber !== null) {

}
let attributeValue = jsonPath.evaluate("$['dseno:EnterpriseAttributes']['attributeName']");

Fixed Bugs / Minor Improvements

Version 1.13.3

  • Minor fix in the DSX REST Client API related to getting the realized changes of a Manufacturing Item

Version 1.13.2

  • Replaying an event caused duplicated event entries to be created within the TIF database.

  • Fix for breaking changes within the DS REST API

    • The getAll method on the EngInstanceService stopped working due to changed behavior in the DS REST API.

      • This is now fixed and the getAll method will return all Engineering Instance’s and not only the first 100.

      • Another method in the API was added to support using the paginated approach.

  • Fix issue with file names containing special characters

    • The Local File API failed to create files with special chars

  • Code tester tool

    • Show result code from the code execution within the code tester tool

Version 1.13.1

  • Error messages from the code executor did not clearly show the reason for the fault

  • Added support for new Event Classes from the 3DX Platform

Version 1.13.0

  • Fix issue with copy of text from the source event details page

  • Fix issue with regeneration of events with Status as input