Approver role
Use the approver role for additional control over which users can publish draft surveys. The approver role is an additional but complementary feature to survey drafts. Once enabled, only users with approver role are able to publish surveys. Users without the approver role are no longer able to publish drafts. This adds a governance layer for customers who need more control over which content is being published to production.
When enabled for a property, different Digital roles have the following capabilities:
- Users with the approver capability can publish survey drafts.
- Users without the approver capability cannot publish draft surveys. These users are able to draft surveys, but not publish them and are referred to as drafters.
To illustrate with an example, this leads to a workflow where:
- One or more drafters create or edit survey drafts. These users do not have the approver capability, therefore the survey context menu does not show the Publish option.
- A user with the approver capability reviews the draft survey, either in the editor or using the preview. When they are happy with the draft, the approver can publish it. Users with the approver capability do see the Publish option in the survey's context menu.
- After some time, another user without the approver capability notices a way to improve the survey. They create a draft, make their changes and notify the user with the approver capability.
- Again the user with the approver capability reviews the changes, and possibly objects to a specific change. Instead of publishing the draft they reviewed, this user proposes a different change by sending a modified draft to the group of users without the approver capability.
- When the changes are agreed on, the user with the approver capability publishes the updated draft.
The result is that users with the approver capability are responsible for publishing draft surveys, which they or drafters create and edit. This ensures a level of governance where a user with the approver capability must approve changes, usually from a group of users without the approver capabilty.
When the approver capability is enabled, you can download a spreadsheet to compare the differences between the draft and published versions of a survey. Use this spreadsheet to get a full insight into what has changed in a draft version before publishing. Other administration teams can use the spreadsheet to create an audit trail for experience program updates to achieve regulatory governance and compliance.
Users and roles
For the approver capability to function as expected it is important to understand the different permissions that need to be assigned to the users who can and cannot approve drafts to be published. The process of assigning these roles to users follows the usual Experience Cloud Roles and Permissions process.
To define a user as an approver of draft surveys in Experience Cloud, the user's Primary Role requires the Advanced Digital Survey Management capability.
To define an drafter in Medallia Experience Cloud, the user's Primary Role requires the Digital Survey Management capability.
To use this feature there should be at least one user with the approver capability and one more more users without the approver capability.
Alternatively, it is possible to use the classic user capabilities screen to set the capabilities for a Digital user. An approver requires the Digital CX Group Manager permission and drafters require the Digital CX Manager permission.
Comparing the draft and published version
Each survey form can have one draft and one published version, and throughout the Digital Command Center you can compare the two versions. A toggle between "Edit Draft" and "View Published" modes is available in the following:
- Survey editor
- Targeting settings
- Form settings
- Translations
- App Rating Settings modal
Generally, when you are in Edit Draft mode the Digital Command Center functions in the way it would if the draft surveys feature is not enabled. When you are in View Published mode you cannot change most settings to ensure the published version is static. Use the View Published mode to check the design of the current published version, how it is targeted and what settings are in place. Toggling back to the draft shows the differences.
Additionally, for properties where the approver capability has been enabled, you can select Export from the context menu to download a detailed spreadsheet which contains a comparison between the form elements in the published and draft version of the survey.
The comparison spreadsheet contains four separate worksheets:
- Form Builder - details of the form structure such as fields, questions, configuration, and so on.
- Form Settings - details of the form settings modal such as buttons, thank you page, and so on.
- Form Targeting - details of the form targeting settings, display options, and so on.
- Translations - shows whether there has been a change in translated forms or changes in the default languages. Tip: In order to compare between translations of a draft and published versions, toggle between the draft and published versions and export the translations spreadsheet for each version.
- Field Name - the field or setting name.
- Draft - the value of this field in the draft version of the form.
- Published - the value of this field in the published version of the form.
