Novti - Client Admin Docs

# Configurations

When configuring your forms, you can customize them to suit your needs. This includes mapping fields, setting up validation rules, and prefilling customer data. This way, you can ensure that the information collected is accurate and relevant to your business.

Validation rules ensure that the data entered in the fields meets the criteria you've set. You can easily implement these rules for each field to make sure that everything is in the right format. This way, you can prevent incorrect data from being submitted.

Another useful feature is conditional logic, which allows you to set up instructions that will be triggered based on user input. This is especially useful if you have complex forms with multiple sections or if you want to personalize the user experience.

novti makes it easy for you to configure your forms to your exact specifications. With our simple and intuitive interface, you'll be up and running in no time!

Table of contents

# Creating a new Form Configuration and selecting a template

Additionally, when creating a new Form Configuration and defining the description/name and environment, you will have the option to select a predefined template from a curated list of form configurations provided by the Novti team. These templates utilize a default set of fields enabled by Salesforce or the corresponding connector. By selecting a template, you can quickly inherit all the necessary configuration options, allowing you to create a form configuration tailored to your needs within minutes.

Loading the image...

# Connectors Mappings

To make sure that you can easily link your connector fields to your novti form fields, we've created Connector Mappings, which enable you to do just that. Once you've linked the fields, they will automatically appear on the forms that use the form configuration you've selected.

Our Connector Mappings make it easy for you to integrate with various connectors, including some of the most popular ones like Salesforce (opens new window), FinDock (opens new window), and Marketing Cloud (opens new window). This way, you can easily connect your forms to the tools you use every day and streamline your data collection process.

Available Connectors which you can use are:

Loading the image...

# Configuration

Click on the "+" icon to configure a connector and select the connector you wish to configure or map.

Loading the image...

After selecting a connector a dialog menu opens in which you can configure the logic for the corresponding connector. The menu will provide the option to be able to configure Permissions and Trigger conditions.

# Permissions

In "Permissions" you will see the option to "Allow connector to update the transaction". Enabling this option means that you are allowing the connector to update the transaction with their responses.

For instance, suppose a connector provides you with a response containing information about the connector, such as its status. If you allow the connector to update the transaction, this information will be added to the transaction automatically.

To give an example, let's say you have a connector for a payment gateway, and you want to allow it to update the transaction with its response. If a customer makes a payment using the payment gateway, the connector will respond with information about the payment status. By allowing the connector to update the transaction, this payment status information will be automatically added to the transaction, providing you with up-to-date information on the payment.

In summary, enabling the "Allow connector to update the transaction" permission gives the connector permission to add their responses to the transaction.

Loading the image...

# Trigger Conditions

You can set up logic to define when the connector should be triggered.

If the option Trigger on create is selected, the connector will be triggered as soon as a customer submits a form.

If you want to use different logic, you can de-select Trigger on create and add data to the Condition set.

An example of a condition set will be seen in the image below. In this example, the condition set will validate if the status from the transaction is COMPLETE. You can create different condition sets depending on your needs.

Loading the image...

# Mapping

Once you have finished setting up your connector, it's time to map your Novti fields to the connector. Mapping refers to the process of linking fields in Novti to fields in the connector so that data can be shared between the two.

To start the mapping process, you need to create a [root] for each connector you want to map. This is simply a way of identifying which connector you are mapping. The specific documentation for the connector will provide instructions on how to format your mapping correctly.

To add a new field mapping, click on the + Add mapping button. Let's say you want to map the first name of a person from Novti to the connector. You would select the connector field you want to map to (in this case, firstName) and a dialog menu will appear. This menu allows you to configure the mapping with options like pairing, validation, and helpers.

# Pairing

For the pairing option, you can choose from various options such as "Has a default value" which lets you input a default value instead of using an Application Field. If you don't choose this option, you can select an Application field from a list of available Form Fields for your tenant.

For example, lets link the first name field in Novti with a Salesforce connector in an easy-to-understand way. First, you need to create a [root] for the Salesforce connector, which helps you identify which connector you are mapping. Then, you click on the + Add mapping button to create a new field mapping.

Next, you select the first name field from Novti, and choose the Salesforce field you want to map it to. You can pick the field from a list of available options. For instance, you might choose to map the first name field in Novti to the "First Name" field in Salesforce.

After that, you can choose the pairing option that best suits your needs. For example, if you select the "Has a default value" option, you can input a default value for the field, such as "N/A" or "Unknown." If you don't select this option, you can just choose the Salesforce field you want to map it to from the list of available options.

Overall, mapping fields in Novti to a connector like Salesforce is a simple process. Just create a [root] for the connector, select the Novti field you want to map, choose the connector field to map it to, and pick a pairing option that best fits your needs.

Loading the image...

In the validation settings you can determine to what validation rules your field should listen.

# Validation

The validation settings will give you the ability to add validation to the field. Validation can be configured with the help of Regular Expressions with the combination of switches.

# Remove on empty

This will give you the ability to remove the field from the connector mapping depending on if the value is filled in. This can be important if you don't want to overwrite the data in your connector with an empty value.

# Not Required

When setting up a form, you may need to specify whether certain fields must be filled in by the end user or not. This is known as setting a field as required or not required.

It's important to note that if the Not Required setting is turned off in the Form Configurations, you won't be able to change this within the form. However, if you turn on the Not Required setting, you'll be able to adjust whether the field is required or not directly within the form.

Loading the image...

# Helpers

In the Helpers view, you can choose a helper that will perform various adjustments to your data when mapping fields. For example, helpers can remove spaces or convert dates. When setting up a helper for a mapped field, you will be prompted to select a category. Each category offers different helper functions that produce different results.

If you choose the DateFormatter category, you can convert any date string (like Unix time or normal timestamps) to the desired format. Alternatively, if you choose the Converter category, you can convert a string to a different format. For example, you can convert the string "1" to the boolean value "true".

Each category offers multiple helper functions that can be used in various scenarios. With the help of these helper functions, you can manipulate your data to suit your specific use case.

Loading the image...

After clicking store it will save the configuration you have done for your field. You will be able to edit this later or even delete the field when you are not using it anymore.

# Connectors Instructions

# Static values

You will find you can configure static values. These are values needed for a connector service to properly communicate to their respective mappings.

Loading the image...

# Instructions

When you are working with the mapping process, you may want to define conditional logic. This means that you can set rules to control what happens to a field or object depending on certain conditions. These rules are called Instruction Helper functions.

There are different types of Instruction Helper functions, depending on whether they are Inheritors or Removers. Inheritors can take information from one field or object and pass it on to another field or object, while Removers can remove a field or object from the mapping based on a specified condition.

For example, let's say we want to remove the firstName field from the mapping if the lastName field is empty. To do this, we would click on the + Add Instruction button, select the removeIfConditionInTransactionIsMet function, and then click on the + Add condition group to set the condition. We would then configure the remover by clicking on the + Add remover button.

If you no longer need an instruction, you can remove it by clicking on the Remove instruction button.

Loading the image...

# Connectors Prefill

Documentation is on the way....

# General

# Description

The field has to be a unique value as you cannot create two Form Configurations with the identical name. After creating the Form Configuration you can start configuring the connectors.

# Use production environment

Enabling "Use production environment" will make it use the configured production environment of Salesforce and Marketing Cloud automatically. If you leave it disabled, it will use the sandbox environments.

In the related forms tab, you will find a view of all the forms that use your defined form configuration.

Loading the image...

# Revisions

Documentation is on the way....

← Regular expressions →