Skip to main content
Conga Support

Creating a Step that Creates a Record

When a step of this type executes, a standard or custom object record is created. In the Step Edit screen, you need to define the record type to create in addition to the other step parameters.

 If you already have steps in the Definition, you can either use the New Child link next to the Step name while viewing the Definition or you can use the New Child Step button while viewing the existing Step (towards the bottom of the page).

  1. Navigate to the Definition where you desire to place this step.
  2. In the Steps section of the screen, click the New Step button.
  3. Complete the following fields:
    • Step Name - Enter the name for this Step. This field copies into the Subject when the process executes.
    • Step Type - Select Create Record.
    • Status Managed By - select one of the following picklist values :
      • Approvals - Select Approvals to manage the status of the step based on whether the step was approved or rejected. For more information, see Managing the Status of a Step with an Approval.
      • Checklist - Select Checklist to manage the status of the step using a checklist.
        • When the Step Checklist Items section displays, review the information provided. During process execution, the completion of all configured checklist items determines when a step's status is updated to Completed.
      • Status Field - Select Status Field to manage the status of a step with the Status field located in the step Information section of the Step. 
      • Create Record Only - Select Create Record Only if you do not want to have the status of the step determined by additional criteria. 
    • Parent Step - Use Lookup to define the parent step, which is the step that must be completed before the Create Record step is initiated.
      • Leave the field blank if the Create Record step needs to be initiated as soon as the process starts.
    • Parent Stage - If a parent step is part of a Parent Stage, all of the steps in the stage must complete before the Create Record step is created.
    • Definition - Field is automatically populated based on the Definition.
    • Stage - Use Lookup to select the Stage to associate with the Create Record step, if applicable.
    • Object Type to Create - Select the type of object that should create when this step executes.
    • Object Record Type to Create - Select the record type that should be assigned to the record that is created when this step executes. This field dynamically displays the record types from the object you specify in the Object Type to Create field.
    • Assignee Type - Select the type of Assignee to whom the step should be assigned. See Assignee Types for more information. 
    • Assignee - Use Lookup to select the person who should be assigned to the step.
    • Generate Email Notification - Select the check box to send an email message to the Assignee, notifying them that the step was created.
    • Due Date Adjustment Base Date - Select the option that should be used to calculate the due date of this step.
      • Current Date - Calculation is based on the current date, which is the date the step is created.

      • Parent Object - Calculation uses the Due Date field on the object specified in the Object Name field in the Definition screen. If the Object Name field is set to Lead, Campaign, or Opportunity, the current date is used in the calculation.
      • Parent Event - Calculation uses the Event date as the base date for the calculation. This only applies if the step is a child of an Event Placeholder step.
      • Date Field - Calculation uses any Date or DateTime field from the Related Account, Contact, or Process Object.
    • Due Date Adjustment - Enter a negative (before date) or positive (after date) number to add or subtract from the date in the Due Date Adjustment Base Date field.
      • For example, if you enter 5, the due date of this step will be calculated by adding five days to the date in the Due Date Adjustment Base Date field. A common example is the steps that need to be due prior to a parent event, such as meeting preparation steps. Enter -3 if this step should be due three days before the meeting. This step would need to be a child of an Event Placeholder step and the Due Date Adjustment Base Date would need to be set to Parent Event.
    • Delay Creation - Select the check box to delay creating this step.
      • Delay Creation

        - Select the check box to define the conditions that must be met before the email is sent, or specify a certain date the email is sent.

        • Populate the adjusted due date fields:
          • Send Date Adjustment Base Date - The date selected in this field will be used to calculate when the delayed email alert will be sent.
            • Parent Object - Calculation uses the Due Date Field on the object specified in the Object Name field for the Definition.
            • Current Date - Calculation is based on the current date. Current date is the date that the Send Step is created.
            • Parent Event - Calculation uses the Event date as the base date. This only applies if the current step is a child of an Event Placeholder Step.
            • Date Field - Calculation uses any Date or DateTime field from the Related Account, Contact, or Process Object selected.
          • Send Date Adjustment - This number will be added to the date specified in the Send Date Adjustment Base Date field.
    • Skip if Past Due - Select the check box to skip the step if the calculated due date is in the past (earlier than today).
    • Copy Subject From Parent Process Object - Select the check box to copy the Subject from the Parent Process Object instead of the Step Name field.
    • Deletable - Select the check box to allow users to delete this step in an executing process. The default is unchecked and will prevent a user from deleting a step in a process.
    • Stop Process if Status Set To - Select a value to stop the process when that Status occurs.
  4. Configure any needed Step Creation Conditions.
  5. Configure any needed Step Field Validations.
  6. Step Loop Back Criteria - Use Conditional login to determine if the process loops back to a previous step or stage.
    • Go Back to Step - Select a preceding step to loop the process back to.
    • Go Back to Stage - Select a preceding step to loop the process back to. 
    • Add Loop Back Criteria - Create a conditional statement, referencing specific objects and fields, to determine if the step will loop back. 
  7. Enter applicable process information in the Capture Object Information section.
    • For example, if Task is chosen as the Object Type to Create, you can add specific instructions to the Description field telling the user what they need to do in order to complete the step. When this step executes in a process, the task is created and these instructions show in the Comments field on the task.
  8. Select the Save button.
  • Was this article helpful?