...
Admins can now configure products to allow guests to assign products to group members on Cloud UI PDPs. When enabled, guests can also create group members on Cloud UI PDPs.
...
We’ve added a couple of enhancements to our Cloud Header. These are available through Theme Designer, so talk with your Aspenware Service Agent if you are interested in these options.
...
We have added ‘transaction ID’ to the unity API so clients can utilize for financial reporting purposes, if needed.
New Order Status for Enhanced Troubleshooting
Aspenware introduces a new status in the order queue admin view to better understand and address order issues. Orders that do not successfully process are marked as Failed and allow for the admin to set the order to “ready” status and have the order processor attempt to try to re-process the order. On rare occasions, a failed order set to the “ready” status returns as a “success” despite not having fully processed into RTP. This could lead to guest arrival with an incomplete order and result in confusion for both admins and Aspenware Customer Service trying to address the issue.
Now, if failed orders are retried and and the order does not fully populate in RTP during reprocessing the order will return with a status of “Incomplete” and an error log is included that helps indicate the source of the processing issue. Because these issues usually result in partial orders that must be remediated in RTP, the order no longer gives a false positive and cannot be reprocessed. This should cut down on admin confusion and help with troubleshooting. Report any orders that are in this state to Aspenware so that we can help resolve them.
Note that this setting is available in Commerce 3.4 or later.
For information on all order statuses see Order Statuses on the Customer Hub.
Resolved Issues
Multiple Type Codes in RTP
...