Configuration Overview
On this page you'll find a high-level overview of the steps needed to configure and use a review process with Reader Rx.
Define the Application Object
Reader Rx is “object agnostic” when it comes to what object you choose to serve as your candidates’ application. Any object can play this role. You configure this on the Reader Rx Configuration tab.
Define Application Feedback Record Types/Field Sets
You will probably need different feedback forms for different types of applications and reviewers. Each one of these forms is defined by an Application Feedback Record type and a corresponding field set. You will write Workflow rules to assign record types to Application Feedback records and the record type will determine what fields are shown to the reviewer (i.e. the ones in the field set that is named after the record type).
Define Help Text for Feedback Fields
You may want to offer guidance for giving feedback and ERX Reader allows you to define several styles of help text to accompany each Feedback item.
Define Application Review Steps
Set the steps and their sequence as shown in the left navigation panel in the Reader UI. This is explained in detail below under Create Steps/Sections.
Create Field Sets on Review Step Objects
On each object that you configured as a Review Step, you must create two field sets:
ReviewAppTabFields
and ReviewAppDivFields
. These determine what fields to display to the
user in Tabular view and Detail View when reviewing the application.
Define Summary Sections
Configure a cover page to show a one-page summary of the application for the reader. The items to be shown in summary can be dynamic based on Application Feedback record type. Configuring Summary Sections is explained here.
Create Profiles and/or Permission Sets
You will need to give users permissions by editing their profiles or defining and assigning Permission Sets.
Configure the Custom Setting
You must create three records in the Custom Setting called OnlineReadingApp Setting.
Assign Licenses
If your license for Reader Rx is not a site license, but, rather, for a set number of users, then you must assign licenses to the users who will use Reader Rx.
Assign Reading Permissions
Every reviewer and every reviewer queue (use standard Salesforce queues) using Reader Rx must be given one or both of two permissions: Review Applications and Reassign Applications. These permissions are set through the Reading Permissions tab, but first you must list the profiles of potential reviewers in the custom setting.
Configure Columns
Each user may select the columns to display on his/her Assigned Applications tab. This can be done through the Configure Columns tab. The administrator may also copy column configurations from one user to other users, using the button called “Column Configurations” on the Configure Columns tab.
Create Notification Email Template
When a user or queue is assigned an application to review, Salesforce’s Approval Process sends an email to the assignee(s). You must create an email template for this purpose. You must not accept the default email template, for it will circumvent Reader Rx by leading your reviewers mistakenly to Salesforce’s standard approval UI.
Create Approval Processes
Reader Rx uses Salesforce’s Approval Process routing engine. You will build Approval Processes to automate the routing of Applications for review.
Configuring Approval Process Entry Criteria Fields
You will also configure Approval Process Entry Criteria Fields, telling Reader Rx which fields to monitor in order to determine when an application should be automatically submitted for review.
Create Application Update Criteria
These allow you to configure updates to the application to occur whenever a feedback record is saved or submitted. The advantages of this feature over Process Builder are:
- All updates to the Application are done in a single transaction, which minimizes the firing of triggers and other operations fired when saving the Application. This eliminates the risk of governor limit errors, which can occur when using Process Builder to perform multiple updates to the application, each of which is a separate transaction with separate firings of application update triggered processes.
- It is in one place so you can easily see what is happening in the Reader Rx context without opening Process Builder and reading through all the processes.
Create Sharing Rules
Create Sharing Rules for Applications, Application Feedback records, and Reading Permissions so that users see just the records that they should.