Defines the child schedule datasets to be created when using the DISTRIBUTED process type. A scheduling problem using this process type can have multiple child datasets attached to it which are processed according to different settings. Input data is always sent into the parent dataset, and the system will automatically determine which child datasets need to be updated as a result of any change.
Syntax:
[ DynamicComponentDependency ] childschedule ChildScheduleName {
[ TimeSpanUOM ] [ TimeZoneOverride ] [ ChangeDetection ] [ CustomChangeHandler ] #SqlDml.QueryBlock ;
}
Column Name | Data Type | Description | Default Value |
---|---|---|---|
child_dataset_id | String(32) | Dataset id for the child dataset. | |
process_type | String(32) | Identifies a particular process to be executed for this child schedule. |
Column Name | Data Type | Description | Default Value |
---|---|---|---|
appointment_window_duration | Number (minutes by default) | This specifies the duration of the appointment window. This is in addition to the scheduling window and starts after the scheduling window ends. | |
maximum_refresh_frequency | Number (minutes by default) | Specifies how often a static child schedule is updated. | |
profile_id | String(32) | The profile of the configuration parameters to use for the input. | |
schedule_end_time | Date | The child schedule end time. | |
schedule_start_time | Date | The child schedule start time. |
childschedule ChildSchedule {{SelectName}} { SELECT .. child_dataset_id, .. process_type, -- optional columns .. appointment_window_duration, .. maximum_refresh_frequency, .. profile_id, .. schedule_end_time, .. schedule_start_time FROM {{sourceTableName}} WHERE ...; }
Note: All selected columns must have correct aliases that match a IFS Scheduling ChildSchedule.
Syntax:
<Identifier>
This page is generated from IFS Developer Studio at 2021-08-13 08:48.