You can use the following optional parameters to enhance your Salesforce buttons:

• templateid: Sets the template to be used when sending out a transaction. Retrieve the template ID from the Conga Platform by navigating to the desired template and copying the string after "/templates/" in the URL. Example: &templateid=d88tPOJgcT175aJCDZ5dkvFZ2IQ=
  Note:

  The templateid parameter must always be placed last in the parameter lineup. The = sign causes errors if placed it elsewhere in the lineup.

• transactionname: Sets the name of the transaction. Example: &transactionname={!Opportunity.Name}+-+Quote
  Note:

  The transactionname parameter can be used in place of idprecordname but one of these parameters must be present for the solution to work.

• recipient[1-20]: The 18 digit ID of a transaction recipient set via a User ID, Lead or Contact. You can designate up to 20 separate recipients, defined by incrementing numbers. Example: &recipient1=00Q3C000006U****,&recipient2=0053C000005yn****, etc.
  • As recipient IDs need to be 18 digits, you can use the CASESAFEID function in your Salesforce button to assure the value is accurate. Example: &recipient1={!CASESAFEID(Opportunity.Primary_ContactID__c)}
    Note:

    Based on the ID given, the First Name, Last Name, and Email must be taken from the record and populated into the respective fields of the recipient.

• recipientName[1-20]: The first and last name of an intended recipient that is outside of your Salesforce organization. You can designate up to 20 separate recipients, defined by incrementing numbers. Example: &recipientName1=Bob Smith , &recipientName2=Mary Jane Smith, etc.
  • The name value must have the First Name value designated as everything before the first space. In the case of Bob Smith, the value is first name, "Bob", last name, "Smith". In the case of more complex names such as Mary Jane Smiths, the first name is "Mary", last name "Jane Smith".

    Note: RecipientID[x] and RecipientName[x] can be integrated together. You must increment the names respectively. For example, recipientName1=Bob Smith, recipientID2=0053C000005yn Each recipient must use only one identification method, either ID or Name, not both.

    If you are using recipientName, it must work alongside recipientEmail[x].

• recipientEmail[1-20]: The email address of an intended recipient that is outside of your Salesforce organization. You can designate up to 20 separate recipients, defined by incrementing numbers. Example: &recipientEmail1=bob.smith@domain.com , &recipientEmail2=mj.smith@domain.com, etc.
  Note: RecipientEmail must be paired with recipientName

• recipientLanguage[1-20]: Indicates the language of the recipient indicated through the matching recipientID or recipientName. For example, &recipientLanguage1=en, &recipientName=Bob Smith, &recipientLanguage2=fr, &recipientName=Jean Luc. The parameter must include one of the following ISO language codes.

  • bg (Bulgarian)

  • en (English)

  • en-gb (English-UK)

  • da (Danish)

  • de (German)

  • es (Spanish)

  • es-ES (Spanish - Spain)

  • fr (French)

  • it (Italian)

  • nl (Dutch)

  • nb (Norwegian)

  • pt (Portuguese)

  • pl (Polish)

  • ro (Romanian)

  • ru (Russian)

  • el (Greek)

  • zh-CN (Chinese - Simplified)

  • zh-TW (Chinese - Traditional)

  • ja (Japanese)

  • ko (Korean)

  • ar (Arabic)

• reassignedAllowed[1-20]: Allows the indicated recipient to reassign signer responsibilities if the value is set to True, and will not allow it to be reassigned if the value is set to False.

  Note: ReassignedAllowed works in tandem with RecipientID or RecipientName. The number assigned to reassignAllowed must correspond to the number assigned to recipientID/recipientName. Example: &reassignAllowed1=True, &recipientID1=0053C000005yn, &reassignAllowed2=False, &recipientName2=Bob Smith.
• expireDays: When expireDays is set, any transaction created will expire x days after the created date timestamp, where x is the value set on expireDays between 1-999 days. The date determined by the expiration date respects the accounts timezone. Example: &expireDays=14
  Note: ExpireDays cannot combine with expireOn. If both parameters are included, it will result in an error: "Only one expiration parameter (expireDays or expireOn) may be set."
• expireOn: When expireOn is set, any transaction created will expire on the date matching the designated date timestamp. Formatting for dates must be in YYYY-MM-DD, or referenced from a Salesforce merge field. When expireOn is set with a specified date, the created transaction will expire on the date at 23:59:59 in the accounts timezone. The merge will fail if you attempt to put a date in the past or input an invalid date format or a merge field that does not resolve in a date. Example: &expireOn=2027-09-12; &expireOn={!Opportunity.CloseDate}.
  Note: ExpireOn cannot combine with expireDays. If both parameters are included, it will result in an error: "Only one expiration parameter (expireDays or expireOn) may be set."
• reminderDays: When reminderDays is set, the system will send an automatic reminder email x days after the recipient received the transaction, where x is a value in days from 1-999. Non-numeric values, negative, zero or values exceeding 999 encounter an error message. Example: &reminderDays=28
  Note: If you are using the expireOn/expireDays parameters and the reminderDays value exceeds the expiration date value, you will encounter a warning: "First reminder will not be sent because it is scheduled after transaction expiration."
• repeatReminderDays: When repeatReminderDays is set, repeated reminders are sent to the transaction recipient every x days after the first reminder is sent, where x is the number of days specified from 1-1000. ReminderDays is a prerequisite parameter and must be set and valid for repeatReminderDays to function. Non-numeric values, negative, zero or values exceeding 1000 encounter an error message. RepeatReminderDays will stop automatically when the transaction expires or all recipients have completed their actions. Example: &reminderDays=10, &repeatReminderDays=10.

  Note:

  • If repeatReminderDays is populated but reminderDays is empty, the system shall display an error: "Reminder Days must be set to use repeat reminders".

  • If repeatReminderDays is populated but totalReminders is empty, the system shall display an error: "Total Reminders must be set to use repeat reminders".

• totalReminders: When totalReminders is set, x additional reminder emails are sent after the first reminder, where x is the total value from 1-5 is sent after the first reminder. ReminderDays and repeatReminderDays are prerequisite parameters for this parameter to function. Non-numeric values, negative, zero or values exceeding 5 encounter an error message. TotalReminders will stop automatically when the transaction expires or all recipients have completed their actions. Example: &reminderDays=10, &repeatReminderDays=10, &totalReminders=3.

  Note:

  • If totalReminders is populated but repeatReminderDays is empty, the system shall display an error: "Repeat Reminder Days must be set to use total reminders"

  • If totalReminders is populated but reminderDays is empty, the system shall display an error: "First Reminder Days must be set to use total reminders"

• documentIds: Allows documents from your Salesforce org to be attached to the outgoing transaction. You can designate up to a maximum of 10 separate documents, defined by a comma delimited list. Example: &documentIds=0693C0000****,0678C0000****,etc.
  Note:

  The documentIds parameter must adhere to the following limitations:

  • Of the 10 documents, the consent document must be excluded from the list.
  • Templates added via the templateId parameter count toward the 10 document limitation.
  • If the OneSpan email delivery setting is enabled, an uploaded document may not exceed 5MB in size.
  • If the OneSpan email delivery setting is disabled, an uploaded document may be a maximum of 16MB in size.
• salesforcefieldname: Stores the latest Package ID from the specified field in Salesforce.
• isbackgroundmode: When set to True, this allows the Transaction to be sent without interacting with the Create Transaction UI. When enabled, the launching user is redirected to a loading screen and notifies the user of the success.
  • isbackgroundmode=true: Sends the transaction without directing the user to the Create Transaction UI after the button is clicked.
  • isbackgroundmode=false: Creates a transaction and redirects the user to the Create Transaction UI after the button is clicked.
    Note:

    The following prerequisite parameters are required for this parameter: &templateID, &recipient

NOTE:

The templateid parameter allows you to identify a single Template ID when creating a new transaction. If a template needs to be selected dynamically based on the values of each individual record, you can use a Salesforce formula to accomplish this. For example, if you want to select a template based on the “Type” field when running your solution from an Opportunity, you can create a new formula field with the following details:

Data Type: Formula

Field Label: SignTemplateSelection

Field Name: SignTemplateSelection

Formula Return Type: Text

Formula Body: IF( ISPICKVAL( Type , 'Existing Business') , 'HnHJRtWnmgjUkeNDiRDu7-zWfeA=', 'VPlJwVw2qDJZonetQsHZvwLGmBc=')

Once the formula is created, use a merge tag to populate the templateid parameter. Following the example above, the parameter would be set as: &templateid={!Opportunity.SignTemplateSelection__c}