Deal Registration Forms Reference
This page provides reference material for administrators who are configuring deal registration forms, including merge field expressions, built-in functions, the security model, and best practices for form configuration. The merge fields, functions, and sharing options described below are used by administrators when defining default values, visibility expressions, and HTML/JavaScript content on the form; partners interact only with the rendered form output.
Using Merge Fields and Functions in Deal Registration Forms
Merge fields and built-in functions allow administrators to add dynamic behavior to deal registration forms — such as auto-populating fields with the current user's data, showing or hiding fields based on conditions, or inserting calculated values into HTML content. They can be used in the following places on a deal registration form:
- Default Values tab — to auto-populate Lead fields when the form is submitted (for example, setting the Partner Account field to
{!$User.AccountId}). - Visibility expressions on fields and sections — to conditionally show or hide parts of the form based on the user's role, device, or other values.
- HTML Snippet and JavaScript elements — to insert dynamic content into custom markup or scripts placed on the form.
In each of these places, merge fields are available through the -Fields- dropdown and use the syntax {!FieldName} for Lead fields or {!$Category.FieldName} for system categories. Functions are available through the -Functions- dropdown and use the syntax {!FunctionName(parameters)}.
For the complete reference — including the full list of merge field categories, every available built-in function with its signature and parameters, syntax rules, usage examples, and troubleshooting guidance — see the official Magentrix documentation:
Security Model
- New forms default to Limited Access — only the owner can see them until sharing is configured.
- The owner of the form is automatically set to the user or organization that created it.
- Use the Sharing settings to grant View access to specific security roles and groups.
- Active Pages used within forms must also be independently shared with the appropriate security roles.
If a form references an Active Page that has not been shared with the partner's security role, the partner will not be able to access the form — even if the deal registration form itself has been shared.
Best Practices and Recommendations
- Configure your form layout and default values before sharing the form with partners — this ensures partners see a complete, functional form from the start.
- Use the Hidden section for fields that should be auto-populated (such as Partner Account, Lead Ownership, or Review Status) but not visible or editable by partners.
- Set meaningful default values using merge field expressions (e.g.,
{!$User.AccountId} for the Partner Account field) to reduce manual data entry for partners. - Use visibility expressions to show or hide fields dynamically based on the user's role, device, or other conditions — this keeps forms clean and relevant for different partner types.
- Always preview the form using the Preview Form option (via the Get Link button) before sharing it with partners to verify the layout and behavior.
- When creating a new deal registration form with the Custom Form type, select --New Form-- to start with a fresh layout rather than reusing a layout that may already be customized for another purpose.
← Editing Deal Registration Forms