Fields for Custom Objects as Process Objects and Steps
Conga Orchestrate requires the following fields and rules.
For any other custom fields that you create on this object, do not include text that matches the API name on your lookup fields. In addition, do not include text in your fields that matches any of the other fields you are creating below. For example, if you have a Case lookup field, do not create a custom field on this object called "My_Case_Status__c". This would match the lookup field to Case and the status fields defined below. You must abbreviate the field name (the label can be any text you desire). Abbreviate your custom field, such as My_Cse_Sts__c.
|
Object: Field Name |
Data Type |
Related To |
Rules |
|---|---|---|---|
|
Status__c |
Picklist |
N/A |
Requires Completed and Canceled Values. Requires at least one additional value indicating an “Open” status and can include additional status values. |
|
Process_Instance__c |
Lookup Relationship |
Process Instance |
N/A |
|
Parent Object Lookup Field(s) |
You must create lookup fields to all the parent objects you will use this object as a step with. For example, to use this object as a step in a process running on the Business Process object; then you must create a lookup field between this object and the Business Process object. The field name must match the object API name, such as Business_Process__c, Case__c, Campaign__c, or Opportunity__c. The field label can be whatever you desire. To use the custom step object as a step in PCE - Definitions, a Lookup field to the object the PCE - Definition is defined against must exist on this object. | ||
|
Loop Object Lookup Field |
You must create a Lookup field on the loop object (FSTR_Loop_c) that looks up to any custom object used as a process object and process step. For example, if you are setting up a custom Legal Agreement object as a process object and step, you must create a lookup field on the loop object that looks up to the Legal Agreement object. | ||
