Difference between revisions of "Extensions.StateMachineProcedure.Trigger"
Jump to navigation
Jump to search
(ref #9361) |
(refs #9361 - change 'shall' to 'will') |
||
| Line 6: | Line 6: | ||
A trigger defines the wait action for a state. A trigger mainly consists of one or more event sources. It has the same behaviour as the [[WaitForEvent]] action in OTX [[EventHandling]] extension. An arbitrary number of triggers can be defined for each state. A trigger can be referred to by one or more transitions. | A trigger defines the wait action for a state. A trigger mainly consists of one or more event sources. It has the same behaviour as the [[WaitForEvent]] action in OTX [[EventHandling]] extension. An arbitrary number of triggers can be defined for each state. A trigger can be referred to by one or more transitions. | ||
| − | After execution of the entry flow the state blocks the thread of execution until it receives an event from one of its trigger event sources. As soon as an event becomes available in one of the sources event queues, the condition in the referenced transitions | + | After execution of the entry flow the state blocks the thread of execution until it receives an event from one of its trigger event sources. As soon as an event becomes available in one of the sources event queues, the condition in the referenced transitions will be checked in order of occurrence in XML. |
{{Important| A trigger can be referenced by the target attribute of a transition trigger. Therefore the name attribute is mandatory for triggers (unlike the base type NamedAndSpecified where it is optional). This is enforced by <xsd:key> constraints specified in the OTX schema.}} | {{Important| A trigger can be referenced by the target attribute of a transition trigger. Therefore the name attribute is mandatory for triggers (unlike the base type NamedAndSpecified where it is optional). This is enforced by <xsd:key> constraints specified in the OTX schema.}} | ||
Latest revision as of 04:42, 20 January 2022
Classification
| Name | Trigger |
| Short Description | A trigger defines the wait action for a state. |
| Class | Named And Specified |
| Base Data Type | |
| Default Value | Empty |
| Provide a Literal | No |
| SpecifiedBy | ISO 13209-4 |
| Standard Compliant | Yes |
Description
A trigger defines the wait action for a state. A trigger mainly consists of one or more event sources. It has the same behaviour as the WaitForEvent action in OTX EventHandling extension. An arbitrary number of triggers can be defined for each state. A trigger can be referred to by one or more transitions.
After execution of the entry flow the state blocks the thread of execution until it receives an event from one of its trigger event sources. As soon as an event becomes available in one of the sources event queues, the condition in the referenced transitions will be checked in order of occurrence in XML.
|
Important: A trigger can be referenced by the target attribute of a transition trigger. Therefore the name attribute is mandatory for triggers (unlike the base type NamedAndSpecified where it is optional). This is enforced by <xsd:key> constraints specified in the OTX schema. |
Sample
trigger : Trigger1
{
EventHandling.TimerExpiredEventSource(1000)
}