Summary
A described microflow can contain an empty change-object activity represented in MDL as:
When mxcli exec rebuilds that statement, it writes a ChangeObjectAction with no member changes, Commit = No, and RefreshInClient = false. Studio Pro validation then reports CE0032 because the action has no items and does not commit the object.
Expected behavior
Round-tripping an existing empty change-object activity should keep the action valid.
Actual behavior
The rebuilt MPR can contain a no-op ChangeObjectAction that Studio Pro reports as invalid:
[CE0032] Change action has no items specified and does not commit the object.
Proposed fix
When the builder sees a change $Object; statement with no member assignments, it should set RefreshInClient = true. Change actions with explicit member assignments should keep the existing behavior.
Related
Part of the broader microflow roundtrip validity tracker #332.
Summary
A described microflow can contain an empty change-object activity represented in MDL as:
When
mxcli execrebuilds that statement, it writes aChangeObjectActionwith no member changes,Commit = No, andRefreshInClient = false. Studio Pro validation then reports CE0032 because the action has no items and does not commit the object.Expected behavior
Round-tripping an existing empty change-object activity should keep the action valid.
Actual behavior
The rebuilt MPR can contain a no-op
ChangeObjectActionthat Studio Pro reports as invalid:Proposed fix
When the builder sees a
change $Object;statement with no member assignments, it should setRefreshInClient = true. Change actions with explicit member assignments should keep the existing behavior.Related
Part of the broader microflow roundtrip validity tracker #332.