Frequently Asked Questions - FAQ

Upon installing Mambo Merge from the AppExchange you will be given access to a 30 day free trail of our Full Speed tier. This will unlock all the features and functionality available for the during of the trial to use as you see fit. After the Trail expires the Free(Style) tier will kick in there after.

It's our base and complete tier that offers features and functionality to work with DOCx files within a Salesforce Org. Does not require a subscription and its free to use.

Its our complete tier which unlocks all features and functionality available within Mambo Merge. It helps Salesforce Orgs do more by automating your document-generation needs. It requires an annual subscription but gets included as part of our 30-day Trial upon installation from the AppExchange.

This is our enterprise tier which unlocks an even greater set of features and functionality which are tailored around development and support. This tier is not for everyone and will require a minimum of 50 user licenese on a 12-month contract to get you started. For those looking for dedicated collaboration on an enterprise level this is the tier that will meet your needs.

Our Free(Style) tier is intended to be used by anyone in the Salesforce ecosystem, free of charge. Our Paid tiers require a 12-month contract renewed on an annual basis. The Trial tier is a way to test out our Paid tiers without the need to commit to a contract, leverage all the features and functionality and see for yourself what our app can do for your Org. Lastly, the Performance tier is intended for enterprises looking for dedicate development and support along with state of the art features that may require 3rd party services and dues. With a mininum of 50 user licenses on top of the 12-month contract plus 3rd party fees.

An instance of Mambo Merge added to any Custom/Standard Object Page. This will grant you the ability to create/modify Templates along with build Routines and use our friendly and helpful Template Builder.

A set of instructions created to help Mambo Merge understand what actions to take when a trigger is made. Such as pressing a button or selecting a dropdown. Routine instructions include what Objects, Records, Relationships, Templates, Backup Dancers, and Layout a Component will utilize at the time of a trigger. They can be assigned to many Components at once, but Components can only be assigned a single Routine any any given time.

A document that contains merge field syntax which Mambo Merge will use in order to identify what field data is requested within a Salesforce Object record. This record field data will be the merged with a Template. Once a Template is merged it becomes a Merged Document.

Once Mambo Merge takes a Template and replaces the merge field syntax with the actual values retrieved from Salesforce it becomes a Merged Document. Meaning it no longer has merge field syntax but actual values from the record retrieved. Merge Documents may consist of but are not limited to quotes, contracts, work orders, or invoices.

A helpful and built-in tool that identify all the merge syntax within an Object/Record selection. Use within Routines to modify existing Templates. If starting from scratch, head over to a Component and choose a record to build out your next Template.

Quickly manage all Routines active throughout all your Components at the push of a button. Our Mambo Studio provides you with a step-by-step wizard of intructions to create, edit, clone or delete Routines - quick and simple.

Identify Lookup Fields or Related Lists within the current Object by setting Relationships. Gather merge field data outside the Object’s scope when certain parent/child or custom field data is needed. We help simplify the process by providing the option to set these up within Routines.

After a Template becomes a Merged Document you can let Mambo Merge know to deploy additional actions such as updating fields within an Object, creating tasks, sending out emails, or even initiating screen flows. These actions help automate the next steps required to keep the pipeline moving along. We simplify the process by providing the option to set up Backup Dancers within Routines.

Each Routine must define what record(s) data will be used to create a Merged Document. A Single Record Routine tells Mambo Merge to create a Merged Document by using the record where the Component was triggered.

Provides the ability to merge multiple documents at once by creating conditions to define what records data will be utilize to merge multiple documents at once. A Records Where Routine tells Mambo Merge to traverse a series of records to meet the conditions set before creating a Merged Document from each of those records data.

Within Routines you can use Backup Dancers to achieve this. Whether you need a record field updated, a task created, email sent or screen flow launched our Backup Dancers are there to have your back.

You can create as many Templates as you need. However, our intention with Templates is to utilize conditional formatting in order to identify slight differences when generating one type of document versus another. This way one Template can be used to generate multiple documents and the differences between each document generated is based on conditions met or not met when merging field values.

Within any Custom or Standard Object Page Layouts you can add as many as you see fit. Each Component can be configured separately from the rest.

Using Salesforce built-in conditional visibility you can filter what Components show up on a Page Layout based on field, user, or condition.

There is no limit to the number of documents Mambo Merge can generate within each Component. However, the amount of storage available within your Salesforce org may place a limit based on the total number of documents stored plus any additional documents you plan to generate in the future.

Our paid editions unlock the ability to generate these types of documents.

Currently, only our paid and trial editions allow merging rich text formatting. However, we are always adding more functionality, and maybe something available in our Free(Style) edition in a future installment.

Our Templates utilize the double curly brace notation merge field syntax with a field name callout as the default. There are options to change the notation within a component to match that of your mail merge template. However, we always recommend double-checking each mail merge callout to ensure the field name matches the syntax utilized within Component.

Our paid editions unlocks the ability to create Routines with dropdown lists or multiple buttons within a Component. However with built-in Salesforce funtionality you may be add several Componets to a Page Layout to access multiple Templates at once.

Field merge syntax notation is basically the Salesforce field name within each object. One way to identify what syntax to use is by going into Salesforce, locating the field, and retrieving its API name. Another way is by using our friendly and helful Template Builder to identify both merge field syntax and data available within each record of an Object.

We adhere to and respect Salesforce security measures so any field not accessible by a user will not display data from any merge field request within any document. However, if another user with merge field access generates a Merged Document for a record and the user without access to the fields has access to the document they will be able to see the merged field data. There is no field security within a file, best practice is to save Merged Documents in Libraries with secured permissions sets and user profiles.

Mambo Merge is a 100% native app within Salesforce which means your data never leaves your org from start to finish.

Mambo Merge contains zero custom objects and builds around a low footprint that seamlessly integrates within Salesforce

Within a Routine you can choose to convert a Merged Document into a PDF at which point you will have the option to generate a preview. Currently, we only offer previews while converting documents into PDFs but may add to other types of documents in a later installment.

Yes it does, by using our paid edition you can go ahead and sync up a Template with either AdobeSign or Docusign.

Our paid editions provide a Records When Routine which allows you to define conditions that will be met to generate documents for each record that meets those conditions. You can generate a Merged Document for each record or combine all Merged Documents into one larger file.

This function takes the existing values of height and width and adjusts them by the percentage values passed. Meaning that if your existing image size is 500 x 400 pixels and you pass a percentage value of 50% for both height and width the output image will be resized to 250 x 200 pixels. You must take into account the original image size when resizing the height and width to ensure the image displays correctly within your document.

The information within an IF statement does not have to be related to the condition evaluated. In the case of a contact record the IF statement is not that complex but when creating documents for invoices, quotes, or orders that is where you start to see more variations of conditions evaluated. For example, based on a particular payment plan display certain information, or if there is a discount on a quote display a discount column with the amount.

By using one of our paid editions you can set Relationships that tell Mambo Merge how to handle parent and child objects. Based on what Object a Component is installed, Relationships identify Look Fields or Related List data available for you to merge within Templates

The simplest way to do this is by using a formula or roll-up field to pass the field data to a related object so Mambo Merge can identify the field and pull it up within the Template Builder.

Each Component displays the edition and version currently installed by going to the dropdown icon and selecting the Support option. Each edition is either a Trial, Free(Style) or Paid edition while the version number usually begins with 1.xx.xx or 2.xx.xx

We tend to release new updates to Mambo Merge 2-3 times a year. However, changes are pushed to Free(Style) users and can be scheduled for paid users. You can always update to the latest by heading to the AppExchange and downloading it.

If a contract expires and does not get renewed before the expiration date, your paid edition will revert back to a Free(Style) edition which may impact your day to day while using Mambo Merge. We recommend you reach out to our helpful sales team at sales@mambomerge.com to renew and moving in the right direction.