Engage configuration tab was introduced in Archer to easily configure some of the fields and reduce human error that may occur while configuring the custom object. We are committed to making the Engage configuration easier by supporting fields like the 'Request Identifier' and 'Publish Language' with the latest Archer release 6.13.0.2.
The configuration tab now also supports the third-party contact cross-reference fields for internal users. This enhancement was made to address the scenario for publishing to internal users added as a contact.
Please note that the Publish Language configuration will work with Engage once Engage 4.0.0 release is deployed.
Field Mappings
Taking a quick look at the field mapping section of the Engage configuration tab, there are two new fields added in the last row, 'Request Identifier' and 'Publish Language'.
Request Identifier option can be used to select any field (other than the key field) that you want to publish as a unique identifier of that record in Engage. Publish Language option will be used to select the language in which you want to publish a particular record to Engage.
On click of these controls, a dropdown opens with the list of fields in the application/questionnaire and the user can select an appropriate field for mapping.
These are non-mandatory fields, and you will be able to publish using Engage configuration tab without populating these fields.
Supporting contacts for internal users
When publishing to internal users, we now have the capability to publish to third-party contacts along with the existing user group and record permission fields.
Once third-party contacts is selected from the dropdown in the contacts section, there will be an additional set of fields that will appear below it, allowing users to provide more details.
