CC/Observer Feature - Addon
DRTE CC/Observer Feature
How to setup and configure - CC/Observer Feature
This feature allows non-signing stakeholders to view the progress and final version of e-signature requests in real-time.
Salesforce Setup > Installed Packages showing "CC_Observer"
- First, navigate to your Salesforce Setup and verify that the 'CC_Observer' managed package is correctly installed. You should see version under the 'drte_ext' namespace. Ensure the publisher is listed as CodeyLabs.
List of Permission Sets with an arrow pointing to "DRTE Observer - Admin User"
- "Next, we need to handle access. Locate the 'DRTE Observer - Admin User' permission set. This is critical for users who will be managing the observer records and configuration."
- Assign the Admin permission set to the appropriate users. Here you can see a successful assignment. Without this, users won't have the necessary CRUD permissions for the observer objects.
Object Manager for "E-Signature Request"
- Now we need to update the user interface.
- Go to the Object Manager and select the 'E-Signature Request' object. We are going to modify the page layout to include the observer related list.
- Within the Page Layout editor, click on 'Related Lists'.
- Drag the 'E Signature Observers' related list down onto the page layout. This allows signers and admins to see who else has access to view the document.
- Once saved, verify the layout.
- You should now see the 'E Signature Observers' section. It includes the Observer Name, Contact, Status, and the unique Observer URL that will be sent to the stakeholder.
- Now let's configure the communication side.
- Open the App Launcher and search for 'Email Templates'. We need to identify the specific template used for observer notifications.
- In the 'DRTE Email Template' folder, look for 'DRTE: Action Required: Review Request - Observer Access'.
- This is the template that contains the secure link for your observers."
- Open the template and copy the unique ID from the URL (the string starting with '00X').
- We will need this ID for our Custom Settings in the next step.
- Go back to Setup and search for 'Custom Settings'.
- Click 'Manage' next to 'DRTE Settings'. This is where we link the engine to our specific email template.
- Find the field labeled 'Observer Email Template Id' and paste the ID you copied earlier.
- This tells the system exactly which template to use when a new observer is added.
- Now we need to create a dedicated page on your Experience Cloud site. Navigate to 'All Sites' and click 'Builder' for your E-Signature Portal.
- Inside the Experience Builder, open the Pages menu at the top and click the '+ New Page' button at the bottom of the dropdown."
- Select 'Standard Page'.
- We want to create a clean, custom layout that isn't strictly tied to a standard Salesforce record detail.
- Choose 'New Blank Page' to ensure we have full control over the component placement without any default clutter.
- For the content layout, select the 'EsignThemeForExperienceSite'.
- This ensures the observer view matches the branding and styling of your signing portal.
- Name the page 'Observe'.
- The URL should be '/observe'. This path is what the system appends to your site URL to generate the observer links.
- From the Lightning Components palette, find the 'DRTE - Observer View' custom component.
- Drag and drop it into the main content area of your new page.
- Don't be alarmed if you see 'Access Denied' in the builder.
- This is normal because there is no active token in the URL during configuration. The component is active and waiting for a valid request.
- The final step is to click 'Publish'.
- Once live, any new 'E Signature Observer' record created will automatically trigger an email to the stakeholder with a secure link to this page."
With the site published, we must now ensure guest users have the right permissions to view the documents.
In the Experience Builder, go to 'Settings', then 'General', and click on the 'Guest User Profile' link. This will take you to the profile settings in Salesforce Setup.
Hit View Users to get to the guest user record.
Now we need to assign the specific guest permission set.
Locate the 'DRTE Observer - Guest User' permission set.
This set is pre-configured with the minimum necessary read-only access to the observer and request objects for external stakeholders.
Assign DRTE Observer - Guest User permission set to the guest user
Finally, most important step, go to DRTE Settings (Custom Setting) and manage org wide record to define the Observer Site Page name.
For instance, we are setting ‘observe’ in the Observe Site Page field value. That’s it, we are done with the setup and configuration.
https://www.youtube.com/watch?v=LgF_BQbxm44