The CIM_ActionSequence association is used to define a series of operations that either transitions the software element, referenced by the CIM_SoftwareElementActions association, to its next state or removes the software element from its current environment. The CIM_Action classes participating in this association must have the same value for the Direction property since they are either part of a sequence to transition a software element into its next state or to uninstall a software element. The next-state actions and uninstall actions associated with a particular software element must be a continuous sequence. Since the CIM_ActionSequence is an association the loops on the CIM_Action class with roles for the 'prior' action and 'next' action in a sequence, the need for a continuous sequence implies: (1)Within the set of next-state or uninstall actions, there is one and only one action that does not have an instance of the CIM_ActionSequence association referencing it in the 'next' role. This is the first action in the sequence. (2) Within the set of next-state or uninstall actions, there is one and only one action that does not have an instance of the CIM_ActionSequence association referencing it in the "prior" role. This is the last action in the sequence. (3) All other actions within the set of next-state and uninstall actions must participate in two instances of the CIM_ActionSequence association, one in a prior role and one in the next role.
Prior property is in 1 class (CIM_ActionSequence) of ROOT\cimv2 and in 2 namespaces
CIM_ActionSequence Qualifiers
Name
Value
ToInstance
ToSubclass
Overridable
Amended
Local
Abstract
True
✗
✗
✓
✗
✓
Association
True
✓
✓
✗
✗
✓
Description
' The CIM_ActionSequence association is used to define a series of operations that either transitions the software element, referenced by the CIM_SoftwareElementActions association, to its next state or removes the software element from its current environment. The CIM_Action classes participating in this association must have the same value for the Direction property since they are either part of a sequence to transition a software element into its next state or to uninstall a software element. The next-state actions and uninstall actions associated with a particular software element must be a continuous sequence. Since the CIM_ActionSequence is an association the loops on the CIM_Action class with roles for the 'prior' action and 'next' action in a sequence, the need for a continuous sequence implies: (1)Within the set of next-state or uninstall actions, there is one and only one action that does not have an instance of the CIM_ActionSequence association referencing it in the 'next' role. This is the first action in the sequence. (2) Within the set of next-state or uninstall actions, there is one and only one action that does not have an instance of the CIM_ActionSequence association referencing it in the "prior" role. This is the last action in the sequence. (3) All other actions within the set of next-state and uninstall actions must participate in two instances of the CIM_ActionSequence association, one in a prior role and one in the next role.'