|
Sets the Output File Name, overriding the default output file name
Requires:
A text value to use for the output file name
You may use static text or merge field names for the values to place in the filename. Use a plus sign (+) to represent literal spaces. Do not include symbols unsupported in filesnames, “\”, “/”, “>”, “<”, etc.
Example:
...&OFN={!Account.Name}+-+Quote
If the Account name is “ABC Corp.”, the resulting file name would be:
ABC Corp. – Quote.doc
Additionally, you may use a special field within the OFN parameter:
{Template.Label}
This can be used in a generic Conga Composer dialog box to refer to the template label (as defined in the Salesforce repository). If using a local template, the filename appears in place of the label.
** Note: Internet Explorer 7 will replace spaces in a filename with the characters “%20” if the output file is opened before saving to disk.
For example, the file above would appear as
ABC%20Corp. %20-%20Quote.doc
if the file is opened before saving to disk.**
Related Issue: Ampersands within the Data
The Conga Composer URL formula field uses ampersands (&) to identify parameters. If you reference fields that might contain ampersands within the formula, you must replace the ampersands with a substitute value, “{~~~}”. Here's how:
A typical Conga Composer / Conga Workflow formula often references the Account Name field in the OFN parameter. Since some Account Names might contain an ampersand character, use a SUBSTITUTE( ) function in the Conga Composer URL field to handle ampersands within the data, as shown here:
Incorrect:
"&OFN=" + Account.Name
Correct:
"&OFN=" + SUBSTITUTE (Account.Name, "&", "{~~~}"
|