The following are enhancements to the Data Protection features in Workflow Automation:

Modification to the Close Incident Action

In the Close Incident window, which you access by selecting the Close Incident action on the Incidents page or the Incident Details page, you must enter a resolution label to close the incident.

See image.

To learn more, see About Incidents and Viewing & Managing Incident Details.

Enhancement to Table Column Sort Settings

On the Incidents page, the incidents that have occurred in your organization display in a table. Using the column sort settings for the table, you can modify how the incidents are sorted and displayed in this table. These column sort settings are saved in local storage, allowing them to persist within the same browser, but they won't carry over to different devices and browsers. They are saved for each user. If you have multiple users sharing the same browser, then each user's settings are stored separately. In addition, these column sort settings stay with the users even if they refresh the page or if they log out of the Workflow Automation Admin Portal and log back in again.

See image.

To learn more, see Using Tables in Workflow Automation.

Enhancement to Custom Email Domains

A DNS record verification process is added to the Custom Email Domain functionality. When adding a custom email domain using the Custom Email Domain Setup wizard, Workflow Automation generates the DNS records required for domain verification. These records are displayed in a table on the Add DNS Record page. You must then publish those DNS records to your DNS provider. After you publish the DNS records to the DNS provider, the DNS server calls Amazon Web Services (AWS) to check whether the records are valid. If the records are valid, the custom email domain is added. If the records are not valid, or if there is a technical issue with verifying the records, the custom email domain is not added. As a result of this new verification process, new messages are displayed on the Add DNS Record page informing you of the status of the verification process. In addition, the custom email domain statuses have changed. The custom email domain statuses are:

• DNS verification pending: Domain is pending DNS record verification.
• Expired: Domain is expired. You did not publish the DNS records to your DNS provider within the 72-hour deadline.
• Failed: Domain failed DNS record verification and was not added.
• In Use: Domain is currently being used as the originating sender domain for user notifications.
• Success: Domain passed DNS record verification and was added.

See image.

Close

To learn more, see Managing Custom Email Domains.

On the Notification Template page in the Data Protection integration, the Client IP tag is added to the Merge Tags drop-down menu when adding buttons, text, and headings to an email notification template. The Client IP tag is also added to the Select Merge Tags drop-down menu when adding a Slack notification template and when adding a Microsoft Teams notification template.

See image.

To learn more, see Managing Notification Templates, Adding Email Notification Templates, Adding Slack Notification Templates, and Adding Microsoft Teams Notification Templates.

The following are enhancements to the Custom Email Domains feature in the Data Protection integration:

• On the Custom Email Domain page, you can revert back to the Zscaler domain (zsworkflow.net) by clicking Revert to Zscaler Domain. The status of the custom email domain that you previously selected as the default is changed from In Use to Verified. When you want to use your custom email domain again for the notifications, on the Custom Email Domain page, you can click the Make Default icon again next to your custom email domain.

  See image.

  

  Close

• On the Verify Custom Domain Setup page, when you select that you did not receive the test email, the Didn't receive an email? section appears at the bottom of the page. When you expand that section, a list of troubleshooting tips appears to assist you with correcting the issues you might have with your custom email domain setup.

  See image.

  

  Close

To learn more, see Managing Custom Email Domains.

On the Custom Email Domain page in the Data Protection integration, admins can configure custom email domains for their organization. Workflow Automation generates and sends email notifications for the various actions that you can perform, such as notifying the user of an incident, escalating an incident to an approver or manager, and performing bulk actions. After you add a custom email domain, Workflow Automation uses that custom email domain as the sender for these email notifications.

See image.

Close

To learn more, see Managing Custom Email Domains.

The following are enhancements to the Data Protection features in Workflow Automation:

Enhancement to the Account Settings Page

The Incident Management section is added to the Account Settings page. In this section, you can enable the Retrieve User Email from Primary Data Source option. When you enable this option, the user email address that appears for an incident on the Incident Details page is retrieved from the primary user data source—i.e., System for Cross-domain Identity Management (SCIM) or CSV attributes. Otherwise, the user email address associated with the incident appears for the incident.

See image.

To learn more, see Managing Account Settings and Viewing & Managing Incident Details.

Enhancement to Obfuscation Settings

On the Account Settings page, you can choose to obfuscate the phone number user attribute for incidents that have occurred in your organization. When you select the phone number for obfuscation, that affects the admin's visibility of this attribute associated with incidents on the Incidents, Incident Details, and workflow pages. In addition, you can override this phone number obfuscation setting by admin on the Admin Assignment page.

See image.

To learn more, see Managing Account Settings, Managing Admin Assignments, and Viewing & Managing Incident Details.