Allowed operations in participant

Allowed operations in ACM-participant for the participant developer point of view.

The table show the the allowed values using the "updateAutomationCompositionElementState" method.

Method	StateChangeResult.NO_ERROR		^{StateChangeResult.FAILED}
Method	DeployState	LockState	DeployState	LockState
undeploy	UNDEPLOYED	null	DEPLOYED	null
deploy	DEPLOYED	null	UNDEPLOYED	null
lock	null	LOCKED	null	UNLOCKED
unlock	null	UNLOCKED	null	LOCKED
delete	DELETED	null	UNDEPLOYED	null
update	DEPLOYED	null	DEPLOYED	null
migrate	DEPLOYED	null	DEPLOYED	null
handleRestartInstance DEPLOYED/UNLOCK	DEPLOYED	UNLOCK
handleRestartInstance DEPLOYED/LOCK	DEPLOYED	LOCK
handleRestartInstance DEPLOYING	DEPLOYED	null	UNDEPLOYED	null
handleRestartInstance UNDEPLOYING	UNDEPLOYED	null	DEPLOYED	null
handleRestartInstance UPDATING	DEPLOYED	null	DEPLOYED	null
handleRestartInstance DELETING	DELETED	null	UNDEPLOYED	null
handleRestartInstance LOCKING	null	LOCKED	null	UNLOCKED
handleRestartInstance UNLOCKING	null	UNLOCKED	null	LOCKED

Suggestions
Implement actions as delete, updeploy and update as idempotent actions. As example in a deleting or updating query (if they doesn't contain non-deterministic functional call) are idempotents.
In a scenario of an instance with more than one elements, and there is a failed undeployment, the user can try again, and the ACM-participant will try to undeploy all elements.

The table show the the allowed values using the "updateCompositionState" method.

Method	StateChangeResult.NO_ERROR	^{StateChangeResult.FAILED}

Method	StateChangeResult.NO_ERROR	^{StateChangeResult.FAILED}
prime	PRIMED	COMMISSIONED
deprime	COMMISSIONED	PRIMED
handleRestartComposition PRIMED	PRIMED
handleRestartComposition PRIMING	PRIMED	COMMISSIONED
handleRestartComposition DEPRIMING	COMMISSIONED	PRIMED

Note:
"handleRestartInstance" and "handleRestartComposition" will be deprecated after the implementation of the BD for participants.