This is actually not a question, just a remark. I'm really missing the Id for the target state in the UpdateChangeOrderLifeCycleStateCommandEventArg
This event is triggered by the CommitChangeOrderActivity function call. The event args match the parameters on the function call.
So that leads to the next question: Why does CommitChangeOrderActivity use the activity ID instead of the target state ID?
It goes back to how the database tables are set up on the Vault server. In the case of change orders, things are indexed to lookup based on the activity.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register