The Next Run Date and Schedule Description fields (API field names APXT_BPM__Next_Run_Date__c and APXT_BPM__Schedule_Description__c) must be included on the Conga Conductor page layout for Professional Edition instances. If these fields are not included on the Conga Conductor page layout, Conga Conductor will not be able to write to them and therefore the scheduled Conga Conductor solution will not process.
To configure Conga Conductor to run on a scheduled basis:
Click thetab and enable the .
In Conductor Setup, click.
Scheduled Conga Conductor will run under the authority of whoever is logged in and clicks the Create Salesforce Token button so ensure it is an appropriate user (typically one with the System Administrator profile).
Scheduled Conga Conductor operations run according to the time zone of the user specified in the Salesforce Refresh Token.
Each user is allowed four Salesforce Refresh Tokens per connected app. Therefore, a small risk exists that the token saved for Conga Conductor will expire due to an excess number of subsequent tokens.
This scenario is very likely if Salesforce credentials are shared amongst many people or if one user utilizes multiple internet browsers to create Refresh Tokens.
A dialog box appears requesting permission for Conga Composer to access the Salesforce instance – click.
This is Salesforce’s OAuth (open authorization) feature and creates the Salesforce refresh token for Conga Conductor.
While the token is created under the Conga Composer name, the configuration is for Conga Conductor.
The refresh token allows Conga Conductor to access Salesforce (only the Conductor components) on this user’s behalf in order to run the scheduled Conductor batches.
This dialog may not appear if the Conga-recommended method of configuring Conga Composer as “Admin approved users are pre-authorized” is utilized (Salesforce Setup > Administer > Manage Apps > Connected Apps > Conga Composer).
Click OK on the dialog box confirming that the Salesforce refresh token has been saved.
The Salesforce Refresh Token area in Conductor Setup now displays as Valid Token.
If the Salesforce refresh token needs to be changed to run under a different user, click the Update Salesforce Refresh Token button (pictured above).
Conga Composer also displays in the Connected Apps OAuth Usage (Salesforce Setup > Administer > Manage Apps > Connected Apps OAuth Usage).
If an end user blocks Conga Composer or revokes the token (under Salesforce Setup > Administer > Manage Apps > Connected Apps OAuth Usage), all scheduled Conga Conductor records will cease to operate on a scheduled basis.
Now Conga Conductor batches may be scheduled via the Schedule button on the Conga Conductor record.