Sales Order Auditing and Versioning (Processing Constraints)
Is it possible to enable both audit history and versioning for a single Attribute?
Client requirement is to enforce two actions for a single attribute. For example for a given Entity / Attribute - Order Header / Shipping Instructions (Operation=Update), enter two constraints, one with an user action of 'Require History' and the other with user action of 'Generate Version and Require Reason'.
The reason is to take advantage of the Audit History form (considered to be a better inquiry tool than the version history form), but still record a new version on the sales order.
From my testing it is possible to set up but, the versioning seems to take precedence, i.e. the version is recorded by no audit history is recorded.
Client requirement is to enforce two actions for a single attribute. For example for a given Entity / Attribute - Order Header / Shipping Instructions (Operation=Update), enter two constraints, one with an user action of 'Require History' and the other with user action of 'Generate Version and Require Reason'.
The reason is to take advantage of the Audit History form (considered to be a better inquiry tool than the version history form), but still record a new version on the sales order.
From my testing it is possible to set up but, the versioning seems to take precedence, i.e. the version is recorded by no audit history is recorded.
0