Skip to main content
Conga Support

About Definition Initiators

Definition Initiators allow you to take process execution to the next level. When setting up an Initiator, you simply tell Conga Orchestrate what Object (Account, Contact, or Event) and what Operations (Insert and / or Update) on that Object you desire to monitor. Additionally, you provide rules (Criteria) about when the Initiator should run based on the Definition you select. Finally, you provide the information (Assignment, Due Date, custom / standard field settings) that you want the initiated process to contain. Conga Orchestrate waits and initiates your process when all Definition Initiators criteria is met.

For example, you can initiate a Client Onboarding process when an Account’s Type field changes from Prospect to Client, or you can create a Definition Initiator that starts an Address Change process when the address is updated on the Contact or Account.

Definition Initiators perform in a specific manner:

  • If your Initiator is monitoring updates (i.e. Account Updates), Conga Orchestrate only initiates a process the first time the fields specified in your criteria are modified and match the Initiator. Subsequent updates to the record that match the Initiator, will not run additional processes unless the fields are modified again.
  • Definition Initiators have an Operator in the Criteria called “Is Changed”. If you select this Operator for your Criteria item, Conga Orchestrate verifies if the field value changes and evaluates the criteria to see if it is true. This enables you to initiate a process if a field, or series of fields, changes regardless of to what they were changed.
  • If you are creating a Definition Initiator to monitor the Contact Object, you can create criteria that evaluate fields from the Contact and Account Objects. This allows you to be very specific when initiating processes from Contact record changes by joining information from its related Account.
    To gain maximum visibility within Salesforce, relate all processes to an Account or Contact.
  • If you are creating a Definition Initiator to monitor the Events, create the events using a Contact specified in the Name field on the Event. This ensures that the process that is initiated is associated with the correct Contact and Account.
  • Definition Initiators automatically attempt to select an associated Contact record when they initiate a process. To do so, Conga Orchestrate initially looks for the following (in this order):

    initiator-contact-field-setting2.jpg

    • A specified Contact Lookup field on the monitored Account. Create a custom Contact Lookup field on the Account object, edit the Conga Orchestrate Setup setting labeled "Initiator Custom Object - Contact Field" and "Initiator Custom Objects" as shown in the screen shot, and populate the new Contact Lookup field on all Account records.

      initiator-contact-field-setting.jpg

    • Contact Roles related to the monitored Account. If a Contact is specified in a Contact role and is set as Primary, it is used first.
    • If neither Contact Roles nor a specific Contact Lookup have been configured on the monitored Account, Conga Orchestrate queries all related Contacts alphabetically, based on the full name, and selects the first one returned.
    • If there are no Contacts related to the monitored Account, the Contact field is left blank on the initiated process.
    • If using a Custom Object as the monitored object on the initiator, Create a custom Contact Lookup field on the Custom Object, edit the Conga Orchestrate Setup labeled "Initiator Custom Object - Contact Field" and "Initiator Custom Objects", and populate the new Contact Lookup field on all records.
  • Was this article helpful?