If you configure workflow subscription conditions based on life cycle states, the following definitions might help you identify the values.

Each message contains a lifecycleState element that is based on the IaaS machine state changes.

The element has the following structure in the message.

lifecycleState : {
    state : STRING,
    phase : STRING,
    event : STRING
Table 1. LifecycleState Elements
Property Description Format and Values Examples
state Contains workflow name and state name. {workflowName}.{stateName}
  • VMPSMasterWorkflow32.Requested
  • VMPSMasterWorkflow32.MachineActivated
  • BasicVmWorkflow.BuildComplete
phase Contains the phase that triggered a message. PRE, POST, EVENT
  • PRE. An event is published when entering this state.
  • POST. An event is published when exiting this state.
  • EVENT. An event is published when an IaaS event is received in this state..
event Contains the event. This property is optional and exists only when the phase is EVENT. {workflowName}.{stateName}.EVENT.{eventName}
  • VMPSMasterWorkflow32.Requested.EVENT.OnProvisionMachine
  • VMPSMasterWorkflow32.VMPSMasterWorkflow32.EVENT.OnBuildSuccess
  • BasicVmWorkflow.CreatingMachine.EVENT.OnCreatingMachineComplete