System events that trigger workflows
As mentioned earlier, one of the ways that an asynchronous workflow can be launched is for a system event to happen to a record. When a system event happens to a record, if there are any workflows associated with the system event and the business object that was used to create the record, then those workflows are launched.
- Associate
- An Associate system event happens to a record when it becomes associated with another record. When a workflow is launched as a result of an Associate system event, the other record that the record is becoming associated with is accessible from the workflow's tasks as the Secondary BO of the workflow's Start task.
- De-Associate
A De-Associate system event happens to a record when its association with a record is removed. When a workflow is launched as a result of a De-Associate system event happening to a record, the record that was on the other end of the association is accessible from the workflow's tasks as the Secondary BO of the workflow's Start task.
There are two other situations in which a De-Associate system event happens to a record:- If a record is removed from a smart section, that triggers a De-Associate system event even though its association with the record that contains the section still exists.
- An association may indicate that a record's existence is dependant on another record. If a record is deleted because a record it depends on deleted, a De-Associate system event happens to the dependant record.
- SCHEVENTCREATE
- A SCHEVENTCREATE system event happens to a record when a time-based event is scheduled to happen to the record. Time-based events are discussed in Calendar and time-based events..
- SCHEVENTEND
- A SCHEVENTEND system event happens to a record at the end of a time based event that happens to a record. Time-based events are discussed in Calendar and time-based events..
- SCHEVENTSTART
- A SCHEVENTSTART system event happens to a record at the start of a time-based event that happens to a record. Time-based events are discussed in Calendar and time-based events.
- SYSTEM DC PROCESS JOB
- This event is used by the DataConnect Agent when a DataConnect Job is ready to run. The agent triggers the workflow associated to the corresponding DataConnect Job record and the SYSTEM DC PROCESS JOB event.
- WF Q Accept
- A WF Q Accept system event happens to a record when a recipient accepts an action item associated with the record.
- WF DELETE FROM MGR
- A DELETE FROM MGR system event happens to a record when it is
deleted using a system delete from a navigation item or a report action. For more information, see
Configuring the user experience.
For more information about reports, see Reporting in Maximo Real Estate and Facilities.
- WF USER LOGIN
- For every login ID in IBM Maximo Real Estate and Facilities, there is a corresponding My Profile record to describe the login ID. When a person signs in, a WF USER LOGIN system event happens to the person's My Profile record.
- WF USER LOGOUT
- For every login ID in IBM Maximo Real Estate and Facilities, there is a corresponding My Profile record to describe the login ID. When a person signs out, a WF USER LOGOUT system event happens to the person's My Profile record.
- WF WIZARD CANCEL
- A WF WIZARD CANCEL system event happens to a record when a user editing the record closes the form. This event triggers an asynchronous workflow on the Cancel or X action of a record. However, this event will not fire on a new record in the null state.