How does Job Scheduler work?

The Job Scheduler (JS) validates the scoping conditions set in each Journey Schedule and if they are met, will launch relevant Journeys.

Example:

The Journey scheduled here is named “Send Client Onboarding Docs to Documentum”

In the above image, the journey type has been set is Documentum Journey.
​
Moreover, the user can define the Journey Schedule Scoping Conditions to trigger the journey.
Based on the conditions given, user can set out the logic for this scheduled Journey to Launch. 
​
Currently, the Journey Schedule can only work on ‘AND’ conditions. This means that we cannot add any ‘OR’ conditions in Journey Schedule.

For Date fields in conditions, we have included the following Operators:

In the above example, the cifcreationDateTime field is set as the condition.

Scoping Conditions:

For the current entity, If the cifcreationDateTime is greater than 2 days in the past from today

For the current entity, If the cifcreationDateTime is less than or equal to 7 days in the past from today.

For the current entity, If the field “Are all docs uploaded to Documentum” is not defined within the tenant.

Here “Is not defined means the field must be null for the condition to be true.”

What does Is Defined mean?

It means that there is no value attached to a Datakey. If the user puts Yes or No - this means that there is a value defined. 
​

Let us look at other operators:

Equals: The field’s value must match the user-entered value for the condition to be true

Not Equals: The field’s value must NOT match the user-entered value for the condition to be true

Finally, if all those scoping conditions explained above are true then the Journey Scheduler will launch the relevant journey.
​

The scheduler first checks to ensure there is no journey of the same type running and then triggers the journey in scope.