Data Modeling
Data Modeling is the first step in creating our Valorx Fusion App. Data Modeling provides the ability to search and add objects and fields to the app. At the same time it also provides the ability to create maps and queries for selected objects. Click on Data Modelling from the Valorx Fusion Ribbon tab. On the right side, a workflow is being built automatically.
Data Modeling screen
Search Bar
- Click on Search Objects bar to search for the objects which you need for the App.
- Select the object and Click on Save and Close.
Search bar to search Objects
Object Summary: Object Summary basically shows overview of Object usage in the app.
Object Summary
- FIELDS: This field will show the number of Fields included in the App. Click on FIELDS to add any additional fields. A pop up will open select the fields and add them to the Objects.
- QUERY: This field will show us the number of Query tasks created for this Object.
- MAPS: This field will show the number of Maps created for this Object.
- Data Modeling automatically creates Queries and Maps for selected objects in parallel which is then will be used to create basic workflow. The bottom part of the Object summary displays the Map details created for the Object.
- Data Modeling creates query for selected object too and in the context of other objects and fields added it shows recommendation to add Object/Field and update the relevant query to filter the data accordingly. This bell icon indicates if such recommendation is available.
- The link icon opens a Relationship explorer which allows the User to search related Objects and add them with relevant fields to establish relationships. It also updates the query filters based on relationship. This component is explained in detail below.
Object Details is expanded when an Object is selected from Summary list. It gives more details of the Object and ability to modify the Queries and Maps of that Object.
Object Details
1) FIELDS section shows total number of fields included and total number of available fields for the Object. Click on Manage Fields to add or remove the fields.
2) QUERY section shows the dropdown with all the Queries of the Object and the details of the filters created for the selected query. When Data Modeling creates the Query and uses that query for the basic workflow it is marked as default. User can also modify Query.
3) MAP section shows the dropdown with all the Maps of the Object and the details of the selected Map. When Data Modeling creates the Map and uses that Map for the basic workflow it is marked as default.
4) RECOMMENDATIONS section shows the possible recommendations of either Object or Field to be included on the basis of other selected objects and fields. It also updates the query filter when recommendation is used by clicking “filter by” hyperlink.
5) Sync button allows User to sync Object with CRM to get newly added field or any other changes.
6) Relationships link button is same Relationship walker which allows User to explore related Objects and add them.
This section displays the Default Workflow created using Data Modeling screen. The sequence shows the Query sequence and Display sequence. It also provides ability to remove Object out of Default workflow and to skip creation of Map for any Object. By default it creates Display and Save workflows but can be turned off anytime.
Default Workflow
There are two more components in the Data Modeling screen which are explained in details below.
As you may have seen above there is a button provided in Object Summary and Object Details to explore relationships of the selected Object.
Relationship Explorer
It allows user to explore Parent/Child relationship to Nth level and it also creates relationship based filter in Query task created for default workflow when relationship is included.
In Data Modeling screen there is a way to edit Form Map which allows user to map fields without interacting with Excel Sheet.
Form Map Editor
1) Available Field list for mapping
2) No. of columns and rows as per Layout
3) Relevant option to add either Column/Row (based on Layout)
Last modified 1yr ago