Skip to main content
Conga Support

OFP

Output Parameter

Active 1

0 Release 7

1  Release 8

OFP

Parameter Value: [path]

* Requires:    &GoogleVisible=1 or &SC1=Google or &BoxVisible=1 or &SC1=Box or &BigTinCanVisible=1 or &SC1=BigTinCan or &OneDriveVisible=1 or &eslvisible=1

&GoogleVisible=1

&OFP=Corporate+Docs/{!Opportunity.Name}

Output File Path

Specifies the file path within the file storage system where the merged output files will be saved. Each folder name should be separated by a backslash or forward slash. We recommend using forward slashes because backslashes can cause issues in Salesforce Lightning and Salesforce formulas (see tip below).

Box Integration

For the Box integration, the file path must be &OFP=RootFolder/Folder+Name/File+Name. Also, avoid using spaces in the Salesforce Opportunity name.

The Box OFP parameter is case-sensitive; the value must exactly match the folder definition in Box. 

Single backslashes work as expected in Conga Composer Button URLs. When used in formulas, single backslashes cause the formula to fail. When converting button URLs to formulas, use a double backslash (\\). In formulas, the backslash is an escape character that specifies that the character that follows should be taken literally.

BigTinCan Integration

For the Bigtincan integrations, the filepath must be &OFP=Channel/Story+Name.

There is no need to reference the tab. 

The OFP parameter must be two segments only. The two segments must represent the channel/story. The channel must be created through the bigtincan hub. The story can be dynamically created .

  • Was this article helpful?