Since we released the first version of Record Creation in April 2022, we have introduced a few more incremental enhancements leading up to a much-improved user experience in the Archer Engage v3.0.0 and Engage Agent v2.0.0.
To support the user experience and for Risk Managers and Archer Admins to effectively manage Engage Record Publication, we have added the following improvements.
1) Controlling who can create new records using Archer Engage:
We introduced the concept of trusted and untrusted domains in Archer Engage V1.2.0. With that change, Risk Managers and Archer Admins can configure Custom Objects to publish templates to Archer Engage, using these properties to control who can and cannot create new records through Engage.
Here is the code snippet from the Custom Object that shows how to set up this property through the Custom Object code:
If the "AccessConfig" value is:
Allow: Only the Engage users logging in from the account with an email domain matching one of the domains in the domains list can create a new record.
Deny: All Engage users except the ones logging in from the account with an email domain matching one of the domains in the domain list can create a new record.
None: Any user can create a new record. If this option is selected, the Domains list can be empty.
2) History of Record Creation:
We also extended the History Tracking for Assessments and Published records feature to support History tracking for Record Creation. Admins can now add the History Tracking Sub-form and its fields in the Custom Object code for publishing the template. Here is the code snipped Custom Object code with History Tracking:
3) Deleting or updating a template:
The latest releases also allow Risk Managers and Archer Admins to revoke the template. Once revoked, users cannot use Archer Engage to create new records using the revoked template.
Here is the Custom Object code for revoking the template:
Republishing the template after an update is even simpler. Risk Managers or Archer Admins can use the existing Publish Custom Object and publish the template again.
4) Creating a new Record from Engage Portal
Before Archer Engage v3.0.0 and Engage Agent v2.0.0, users could create new records only if they had the link to create new records.
In v3.0.0, we added the feature to enable users to create records from the portal UI.
For the templates published with explicit "Allowed" domain lists control, users with an email address from one of the "Allowed" domains will see the option to create new records from the Engage Portal.
For example, in the following image, Org 1 publishes Templates for App1, App2, and App3.
If User1 (u1@domA.com) and User2 (u2@domB.com) receive the direct link to create new records, they can create records for App1, App2, and App3.
However, only App1 has a domain list with the "AcceeConfig: Allow" setting. Hence, When User1 and User2 log into the Engage Portal, the only Application they can create records for is App1.
Similarly, Org2 has published a template for App4 with the "AccessConfig: Allow" setting for the domA. Hence User1 (u1@domA.com) will see the option to create records for App4 in the Engage Portal.
Finally, users belonging to domX.com will be unable to create records for App2. However, anyone with the link to create the App3 can create records.
We have also made the package with a complete script to create records, publish, and delete templates on the Archer Community. For more details, you can also access online help documents from Archer Help Center.
These features are now available for both - Archer Engage and Archer Engage for Vendor portal v3.0.0 and Archer Engage Agent v2.0.0 onwards.
We look forward to your suggestions, feedback, or questions in the Comment Section below.
