Glossary - Understanding The Terms and Lingo

1.27.2 | 5/12/2023
Post-Installation, Document Generation, Terms, Naming Convention


Our glossary page helps you build a better understanding of the terms used within our Mambo Merge app along with Salesforce terms that Mambo Merge engages with from start to finish when generating documents.

FREE Edition

Our based edition with sufficient features to instantly build professional, data-rich documents.

Standard Edition

Our extended edition provides a wider range of customization and Merge Functions for creating documents.

PRO Edition

Our complete edition with full customization, Mass / Batch Reports, PDF / XLSX output, Image Merge Function and pretty much anything your mind can come up with. (Certain functions require custom code only available in Enterprise Edition (or higher) of Salesforce.)


An instance of Mambo Merge that gets added to a lightning page for use.


A set of instructions that gets stored and used to tell Mambo Merge the object, records, templates, relationships, post-merge actions, and layout a component will consist of.

Configuration Wizard

A series of steps to take in order to properly create, delete, import, export, clone, and edit configurations.

Template ID

Used to insert a file ID or a configuration name to activate a component.


A file that includes merge fields which Mambo Merge will use to generate and create data-rich documents each time a component is used.


The ability to tell a component to fetch data outside its current object’s scope. Where field data may be obtained and used to generate documents. Whether it’s a parent/child or a custom object, you’ll be able to tell Mambo Merge where to go and obtain the data you need.

Post-Merge Actions

Instructions to tell Mambo Merge what actions to take after a document is merged. Actions such as updating field data, creating tasks, or emailing recipients.

Template Builder

The menu used to identify the merge field syntax that will be required to retrieve specific data from fields located within standard or custom objects.


The menu used to launch the configuration wizard.


Menu to identify the number of times Mambo Merge has been used within your Salesforce org. Allows you to connect with our Mambo team for support issues or inquiries.

Merge Field Syntax

The syntax that is used to insert within templates to generate merged documents. It starts and ends with a double curly brace notation followed by the merge field name.

Debug Mode

A checkbox that enables a component to activate its debug mode for helping our support team troubleshoot issues within Mambo Merge.


Special merge field syntax built-in to help provide or automate beneficial information such as today’s date, upper or lower case text, rich text, images, and much more.

File ID

15 - 18 alphanumeric characters unique identifier used within Salesforce to identify a file stored within your org.



A user interface that contains fields that store data related to that entity.


A specific instance of an object, which represents a real-world entity.


A specific piece of information stored in an object, which represents a real-world entity

Lightning Page

Standard or custom object page used to add components within a Salesforce org.

Custom Component

A custom app that has been added to an org and used to insert an instance of the app within a lightning page.

Component Visibility

The ability to set conditions that determine when a component is visible within a lightning page by either field, user, or specific criteria.


A Salesforce org central location to upload, store, and collaborate on files such as documents, presentations, images, and videos.


A remote website that the org can invoke from within Salesforce.