Skip to main content
Conga Support

Fields for Custom Objects as Process Objects

Conga Orchestrate requires the following fields and rules when using a custom object as a process object.

Note: You can customize the Field Labels, but the Field Names must match the object in this table (the "__c" is added automatically by Salesforce). Also, the specified object must have the ability to relate activities to the object.

Object: Field Name

Data Type

Related To

Rules

Auto_Close__c

Date / Time

N/A

Read Only on page layouts.

Business_Account__c

Lookup Relationship

Account

N/A

Client__c

Lookup Relationship

Contact

This field must be required from the master (and all other) page layouts.

Completed_By__c

Lookup Relationship

User

Read Only on page layouts.

Completed_Date__c

Date / Time

N/A

Read Only.

Due_Date__c

Date

N/A

This field must be required from the master (and all other) page layouts.

ownerid__c

Formula – Text

N/A

This field is optional and only needs to be created if your custom object is the detail record in a master-detail relationship. The formula field should retrieve the OwnerId from the master object. The structure of the field will be dependent on how the relationship is named. For example, if your object is related to the account object through a master detail the formula is: Business_Account__r.OwnerId.

PCE_Definition__c

Text

N/A

Up to 18 characters. Must define length - this field is populated by Conga Orchestrate.

pce_definition_lookup__c

Lookup Relationship

PCE – Definition

N/A

Process_Initiated__c

Date / Time

N/A

Read Only on page layouts.

Recurring_Business_Process__c

Lookup Relationship

Recurring Business Process

N/A

Skipped_Steps__c

Long Text Area (32768)

N/A

Read Only. Maximum number of characters (32,728). Should not be visible on page layouts.

Status__c

Picklist

N/A

Requires Open, Completed, and Canceled values.

Subject__c

Text

N/A

Up to 80 characters in length. This field must be required from the master (and all other) page layouts.

Loop Object Lookup Field You also need to create a Lookup field on the Loop object (FSTR_Loop_c) that looks up to any custom object used as a Process Object. For example, if you are setting up a custom Legal Agreement object as a Process Object, you must create a Lookup field on the Loop object that looks up to the Legal Agreement object.