Automerge rules

This template defines conditions for merging tasks together, and how merging will influence visits.

For more information, see Automerge.

automerge_rules.csv
Column name	Required	Data type or format	Description and business rules
Source	Yes	Text field Maximum of 50 characters.	Task ID or a Task Type from the Task Definition template.
Source Type	Yes	[TASK_TYPE, TASK_ID]	Defines which type of value is used in Source.
Destination	Yes	Text field Maximum of 50 characters.	Merge destination for the source.
Destination Type	Yes	[TASK_TYPE, TASK_ID]	Defines which type of value is used in Destination.
Ignore Location Capabilities	Yes	[TRUE, FALSE]	Determines whether the scheduling engine can ignore the Source's Task Type when placing a merged task on a track. i.e. Whether the Source's Task Type can conflict with the Location's Task Type. If TRUE, the scheduling engine will place merged tasks based on the Destination's Task Type. The Source's Task Type will not be considered. If FALSE, the scheduling engine will place merged tasks based on the Destination and Source's Task Types. The Destination and Source's Task Types are defined in the Task Definition data. The Location's Task Type is defined in the Location Capability data.
Priority	Yes	Integer (whole number)	Priority of items to merge into the visit. If there are multiple destination candidate visits for a task to merge into, the engine choose the rule with the lowest priority. i.e. priority 1 would be the first preference, followed by priority 2, etc.
Move Destination Visit	Yes	[TRUE, FALSE]	Determines whether a Destination visit can be moved earlier to accommodate a Source merge task. If set to TRUE, a Destination visit can be scheduled earlier (sacrificing task yields) to meet the Source yield criteria. If set to FALSE, no Destination visits will be scheduled earlier to meet the Source yield criteria. The Source merge task will either be merged into a visit that already meets the Source yield criteria, or it will not be merged.
Visit Span	Yes	[ADD, NO_CHANGE]	Defines whether the visit span changes when a task is merged into it. If ADD, the merged task will add to the visit span. If NO_CHANGE, the visit span will not be affected by the merge.