Skip to content

Scheduling Optimization Triggers

Triggers are required to be enabled for handling changes happening after the initial Full Load command has been transferred to IFS Planning and Scheduling Optimization (PSO).

The triggers are created when the Scheduling Model is installed. A trigger is created for each of the Insert, Update and Delete operations for each table within the Scheduling Model having Change Detection defined.

A trigger with Prompt Update set will send the detected changes immediately rather than waiting for the Database Task Send Scheduling Optimization Dataset updates to run.

Change handling is not used for Static datasets, including Static Scheduling Optimization using an IFS.ai account. The triggers will not create change messages for these datasets.

Triggers for a selected dataset can also be opened using the View Triggers command on Scheduling Optimization Datasets.

Read more about Scheduling Optimization.

Activities In Scheduling Optimization Triggers

Enable/Disable Trigger

It is possible to disable specific triggers if required. This is not recommended as it will prevent change messages from IFS Cloud to IFS PSO from being created.

On enabling a trigger the Send Full Load command will be issued for all enabled datasets for the selected Scheduling Model(s).

Disable/Enable All Triggers

Disabling all triggers for the selected Scheduling Model is advised when data loading into IFS Cloud. This will then prevent unnecessary change messages from being sent during this period. Once the data loading is completed the triggers should be re-enabled for the selected Scheduling Model using the Enable All Triggers command.

On enabling all triggers the Send Full Load command will be issued for all enabled datasets for the selected Scheduling Model(s).

Redeploy Triggers

This will redeploy all triggers for the selected Scheduling Model(s) into the database.