Release notes for Optimizely CMS and Customized Commerce updates

Fixed an issue where the requestor received redundant notifications about a request to change expiration settings.

Fixed an issue that displayed the wrong language assignment in the change approval message. If you opened a page that was configured for an approval sequence and set the expiration on the language version (such as Swedish) in English, the EN language code was displayed in error.

Fixed an issue that displayed the wrong content language when you created content with more than one version, went to the other language version but it only displayed English in the breadcrumbs.

CMS UI 11.21 made many changes to the CMS UI styling. To match these changes, Change Approval needs to change in the following places:

• The Approve Changes button text is now bold.
• An arrow icon below the Approve Changes button.

Upgrade to new CMSUI version; apply new platform navigation and styling.

Steps to reproduce:

1. Edit the approval sequence of a content item, such as an Alloy Track page.
2. Add Editor1 as reviewer of step #1.
3. Check "Prevent users from approving their own changes".
4. Save.
5. Editor1 starts a change approval corresponding the content. For example, he changes the expiration date.
6. Editor1 views the change details and approves the changes.

Expected:
Editor1 is unable to approve his own change since "Prevent users from approving their own changes" was checked

Actual:
Editor1 gets a message "This command is not available for approval".

This change lets you apply the "four eyes" principle to change approval. This means that the person who made a change is not allowed to approve it.

To configure this, check the Prevent users from approving their own changes box for the approval sequence. In this case, if an approver starts an approval sequence, he or she does not receive a notification, nor the approve or decline button.

If you do not want to institute the "four eyes" principle, do not check the Prevent users from approving their own changes box for the approval sequence.

Note: The bug only happens on the daily site if the Change Approval package is installed.

Precondition: User A is an approver of the content.

Steps to reproduce:

1. Create a content item.
2. Define an approver for the content and require the comment for approving or declining.
3. User A sets content to review.
4. User A approves the content with a comment.
5. Open the Notification list.
6. Click on any notification or on the tree page.
7. Select another content item.

Expected
Should navigate to the selected content.

Actual
Nothing happens, or you have to wait for a long time.

Make Change Approval compatible with CMS 11
EPiServer.CMS.Core >=11.9.2
EPiServer.CMS.UI.Core >= 11.5.4

1. Allow all kinds of changes to be applied for the IT system regardless of a reviewers' access rights after an approval sequence is approved at the last step. Reviewers need the minimum access right to access change details view. This minimum value should be Read.

2. For moving related changes:

• After a sequence is approved, the admin log should show a requester's identity as the action trigger, not a reviewer's.
• If content is moved to Trash, then "deleted by" information in trash should show requester's identity as well.