Activity Group defines related activities either as pre-requisites, co-requisite, or combined activities, or as a suggested ordering between the activities. The type of activity group is indicated by the value in attribute pre_co_req.
Syntax:
[ DynamicComponentDependency ] activitygroup ActivityGroupName {
[ TimeSpanUOM ] [ TimeZoneOverride ] [ ChangeDetection ] [ CustomChangeHandler ] #SqlDml.QueryBlock ;
}
Column Name | Data Type | Description | Default Value |
---|---|---|---|
activity_id1 | String(32) | Specifies the id of the activity this relates to. | |
activity_id2 | String(32) | Specifies the id of the pre-requisite or co-requisite activity. | |
pre_co_req | String(20) | Defines the type of link being made between the activities. |
Column Name | Data Type | Description | Default Value |
---|---|---|---|
all_or_nothing | Number (0 = False, 1 = True) | Specifies that this activity can be allocated only if all pre-requisites can also be allocated. | False |
min_delay | Number (minutes by default) | Defines the time delay that activity 1 must wait to start after pre-requisite activity 2 has started. | 00:00:00 |
same_resource | Number (0 = False, 1 = True) | Defines whether the same resource that performs the pre-requisite must perform activity 1. | False |
keep_splits_together | Number (0 = False, 1 = True) | For co-requisites that are splittable this determines whether the individual visits should all start at the same time, or just the first visits. | |
max_delay | Number (minutes by default) | Defines the time delay after start of pre-requisite activity before which activity must commence. | |
order_incentive | Double | Defines a multiplier on the value of scheduling the activities if the DSE follows the suggested order of the two activites. | |
overlap_allowed | Number (0 = False, 1 = True) | Specifies whether the dependent activity is allowed to start at the same time or after the start of its prerequisite activity |
activitygroup ActivityGroup {{SelectName}} { SELECT .. activity_id1, .. activity_id2, .. pre_co_req, -- optional columns .. all_or_nothing, .. min_delay, .. same_resource, .. keep_splits_together, .. max_delay, .. order_incentive, .. overlap_allowed FROM {{sourceTableName}} WHERE ...; }
Note: All selected columns must have correct aliases that match a IFS Scheduling ActivityGroup.
Syntax:
<Identifier>
This page is generated from IFS Developer Studio at 2021-08-13 08:48.