Add Views are designed for creating new objects in a track. Typically, users access Add Views from List Views. To set this up, create an Add View and configure it as the default Add View for the List View. Once done, users can simply click the Create New button from the List View to access the Add View and add a new in that track.
Configuring an Add View
To create an Add View:
Open the Add Page and click Create New.
The view type will be pre-selected and cannot be changed.
Available to Guests
Enable this option if you want the guests to have access to the view in the portal. They are users who can access the portal without login credentials (neither agents nor clients).
Text On The Button
Each Add View includes a customizable button to guide users through the object creation process. This feature is especially useful when multiple Add Views are linked together using the Default Next Screen feature.
For example, the button text on intermediate steps can be set to Next, while the final step can display options like Create, Save as Draft, or Add Object. Customizing the button text enhances clarity for end users, helping them understand the purpose of each step in the workflow.
Field Groups
Click the + icon to add the desired field groups. Each group will appear as a subsection in the add view, with the group name as the header. The fields within the group will be displayed beneath it.
Disable Mandatory Field Checks: If you want to bypass the mandatory check for required fields in a specific field group during object creation, enable the Disable Mandatory Field checkbox for that group.
Rearranging Field Groups: Customize the order of field groups by dragging and dropping them into the desired sequence.
Removing Field Groups: To remove a group, simply click the X button next to the field group.
Agent and Client User Roles
Assign agent and client roles to control who can access the display views. Use the dropdown to select the specific roles that should have access to the view. This ensures that only authorized users can see and interact with the display view content.
Screen Rules
Screen Rules provide flexibility and control over the flow of object creation in Add Views. These rules allow you to manage multiple Add Views for a single object, guiding users through different screens based on conditions, validations, or configurations. Below are the key features under Screen Rules:
Default Next Screen:
This feature allows linking multiple Add Views to create a single object, providing a step-by-step process for seamless object creation. After completing one screen, users are automatically redirected to the next predefined Add View. Buttons can be customized with labels like Next or Save to guide users through each step, while the final screen can have options like Create or Save as Draft to complete the process.If the Default Next Screen is set to Final Screen, an additional option, Redirect to View, becomes available. This dropdown lists all the Display Views and List Views in the track. Based on the selection, the system redirects users to the specified view after completing the final screen, enhancing navigation and usability.
If the user does not have access to the view specified in redirect to view, the object will be created and the user will be redirected to an โUnauthorized view accessโ error page .
If no display view is specified in Redirect to View, the user is taken to the list view the user was on after object is created.
Disallow Continue:
This option is useful when validations fail during object creation. If enabled, users cannot proceed to the next screen. Only Cancel and Go Back buttons are available on this screen. To implement this, create a "Disallow Continue" screen and add it to the Screen Rules section where the validation check is performed.Auto Redirect:
Ideal for scenarios where data is collected at the relationship (child track) level, but object creation begins from the parent track. If an Add View in the parent track contains no field groups and Auto Redirect is enabled, users are automatically redirected to the display view configured in redirect to view. Note that Screen Rules override this feature if both are configured.Validation-Based Rules:
Screen Rules allow you to define specific conditions or validations during the object creation process. Depending on these validations, the system dynamically determines the next screen, providing a flexible, rule-driven flow for creating objects.
Example
Screen 1 Settings
This configuration is designed so that in the first Add View screen, when the Serial Number choice field is selected as "Not on List," the user is redirected to a Disallow Continue screen upon clicking the Next button. On the other hand, if the serial number selected is valid (not "Not on List"), the user is directed to the Default Next Screen, which is configured as Add View 2.
Screen 2: Disallow Continue
Screen 3: Final Screen and the default Next View of Screen 1
In this screen's settings, the Default Next Screen is set as the Final Screen, indicating the last step in the object creation workflow. Once the user clicks to proceed, the object will be created, and the system will redirect them to the selected view specified in the Redirect to View option. This ensures a smooth transition to the appropriate display or list view after completing the workflow.
Illustration of above configuration in an agent portal
Initiation of object Creation
From the List View, click on the Create New button. This action opens the first Add View screen, where the user is prompted to enter the Serial Number.
Scenario 1: Validation for "Not on List":
In the Serial Number field, select the choice "Not on List".
Click Next.
Since a rule is configured to check if the Serial Number is set to "Not on List", the system redirects the user to the Disallow Continue view. This view notifies the user that the object cannot proceed further
On the Disallow Continue view, click the Back button.
The system takes the user back to the previous screen (the initial Add View).
Scenario 2: Alternate Serial Number Entry
Modify the Serial Number field to any valid value other than "Not on List".
Click Next.
The validation succeeds, and the system redirects the user to the Default Next Screen, which is Add View 2.
Final Screen:
On Add View 2, enter the required data.
Click Create to finalize and save the object.