Job Executor

In TIF Cloud, the logic that performs the integration use case logic is called 'Job Executor'.

When you define an integration use case, you first decide how the use case is going to be invoked. E.g. is it invoked from an event within the 3DEXPERIENCE™ platform, or is it triggered by a Scheduled Job from within TIF itself or is it perhaps triggered via a REST call from another system.

Common among these alternatives, is that you point out a Configuration, which is defining the configuration details how to execute the job.

When you create a Configuration you will among others give it a type. Depending on the selected type, the content of the configuration itself needs to follow some rules.

The most commonly used executor is the Java Script Executor. When selecting the Java Script Executor as type, the content of the configuration will then be the integration use case logic expressed in the JavaScript language. There are certain APIs made available for the code to help implement the logic. Please read more about this in the JS Executor documentation.

There are other kind of Executors available that performs more specialized tasks. In those cases the content of the configuration might only consist of some configuration parameters in the format key=value with or without an assisting UI for filling in these parameters.