Completion Event Types
Completion event types are used to define the completion events that capture closeout information received from an external application.
Completion event types are referenced on activity types to indicate which completion events are valid and should be included as part of the lifecycle of activities of that type and can be defined as optional or required. As examples, this can affect when service history is created for an activity and the disposition of the assets on an activity as the activity is processed.
Note:
You will need to add the completion event type to the activity type using the Activity Type portal in order to set the completion event types as optional or required. Also, setting a Default Event Date Time on the completion event type controls whether or not the completion event can be created automatically without user input.
Work activities received from an external system require the following completion event types to be listed on the activity type:
• Update Worked Assets (W1-MobileUpdateWorkedAssets)
• Remove Tracked Asset (W1-RemoveTrackedAsset)
• Remove Non-Tracked Asset (W1-RemoveNonTrackedAsset)
• Install Tracked Asset (W1-InstallTrackedAsset)
• Install Non-Tracked Asset (W1-InstallNonTrackedAsset)
• Attach Component (W1-AttachComponent)
• Create Operational Reading (W1-CreateOperationalRead)
• Create Any Service History (W1-CrAnyServiceHistComplEvtTyp)
Note:
Removal completion event types must be listed before installation completion event types to support proper processing of asset exchanges.
Parent topic