sp102_activity_conflicts
- Jason Andrew
Owned by Jason Andrew
Oct 02, 2024
1 min read
Loading data...
This table is used to determine how the system should handle an activity when it is first input or when it is modified such that it overlaps (i.e. is concurrent with) another activity for the same employee. The way in which two such "conflicting" activities are resolved depends on the type of the existing activity and of the newly input (or newly modified) activity. The options are either to allow the overlap; or to warn the user of the existing activity and prompt him to confirm the details of the new activity; or to forbid the overlap.
Â
Table Definition
Field | Type | Default | Nullable |
|---|---|---|---|
| current_activity | number(2) | Â |  |
| new_activity | number(2) | Â | |
| resolution | number(2) | Â |  |
KeysÂ
unique (current_activity, new_activity)Â
foreign key (current_activity) references sp105_activity_types (activity_type)Â
foreign key (new_activity) references sp105_activity_types (activity_type)
Column Descriptions
| Field | Description |
|---|---|
| current_activity | A number identifying the type of the existing activity. A null value in this column is taken to match any activity type. |
| new_activity | A number identifying the type of the new (or newly modified) activity. A null value in this column is taken to match any activity type. |
| resolution | A number indicating how the conflict should be handled - 0 = silently allow the overlap. 20 = prompt the user to confirm before allowing it. 30 = forbid the overlap |
Â
Â