Date: Fri, 29 Mar 2024 13:28:09 +0000 (UTC) Message-ID: <1171775327.1.1711718889508@6a29d823d38c> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_0_1377627775.1711718889484" ------=_Part_0_1377627775.1711718889484 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Fields mappings are a dynamic feature of Cloudoko Forms that enable you = to populate your target CRM form with specific data.
You must be editing a Form in order to view the Field Mappings defined a= gainst it.
You can find them on the 3rd tab of the Manage Form&nbs= p;screen.
Clicking on this tab, you will notice that the Field Mappings are divide= d into 4 categories, each one dictating when it will be executed:
Think of these as field mappings that you get for free .
When we setup your Cloudoko Forms environment, we will define a number o= f default field mappings that will be made available to all forms you create in future.
By and large the purpose of the default mappings is to ensure that any c= ustomer data captured by your Cloudoko Form will be automatically copied in= to corresponding fields defined by your target CRM Form (e.g. Lagan E-Form)= .
In future, as we add more features to Cloudoko Forms, we may ext= end the default field mappings across our customer environments so= that new data is automatically made available for consumption by your form= s.
These will execute just before we show the first page of your CRM form.
Depending on the Form Behaviour that you set, this will either be:
See the diagram below for more explanation.
These will execute just before we execute a save action= specified by your CRM form.
You would typically define a mapping here if you wanted to populate cert= ain data just before the request is created on CRM.
These will execute just after we have executed a = ;save action specified by your CRM form.
You would typically define a mapping here if you had information that is= only available once the request is created on CRM (e.g. your case referenc= e number).
The example below shows the pages and workflow that a typical Cloudoko F= orm might have and where field mappings are executed.
Pages in blue are those that are defined by Cloudoko (and appear dependi= ng on the Form Behaviour settings you choose for your Form= ).
Pages in grey are those that are imported from your CRM form.