23D - History REST API - Use with the Standard Commerce Process

Summary:

The Standard process does not contain a ‘History Action’ by default, thus, in order to use the history API, an Administrator will need to create one. The History Action should have an .xsl associated with to so that the action can also be placed on the UI either for Admin or Sales user interaction.

Attached will be an .xsl history file you can use, and the JSON body of the REST API call necessary to retrieve the History information.

Use Case:

Suppose you wish to track/investigate the changes made to specific commerce attributes, or changes made by a specific user on a quote on a per action/modify basis. The History API can be queried broadly or filtered to provide the requested information in a JSON format.