Page Layout Configuration in CX Studio
A page layout allows you to control the layout and organization of detail and edit pages. It enables you to configure entity information on grid view, manage record-level entities, related lists (sections), and define rules for individual actions and fields. You can configure the following aspects of a page layout through CX Studio Lite:
- Managing data grid view.
- Managing content details view. For example, adding standard and custom fields when creating and cloning the clauses.
- Adding actions to page header.
- Applying rules.
- Cloning standard actions. When the action permissions are set, cloning standard actions such as Generate, Activate, Amend are displayed in the CX Studio.
When configuring layouts, keep in mind that the Edit option in the Clause Details page works only with the default layout. If you are using custom or cloned layouts, you must either delete and re-clone the layout from the default, or manually update the layout metadata to incorporate the change.
"saveActionFunc": "clause::onSave"
For more information, see CX Studio: Page Layout Editor.
Assign a Page Layout by Record Type and User Profile
You can also assign page layouts based on record type and user profile. You can configure different layouts for different contract types for the same user profile, or different layouts for the same contract type for different user profiles.
If the user has access to one record type, the page layout assigned to the record type or the user profile is displayed when the user initiates record creation. A user with access to more than one record type must select a record type based on which the corresponding page layout is displayed.
Control the Display of Owner and Owner Type Fields
You can control the display of the Owner and Owner Type fields in the page header. By default, these fields are visible. To hide them, disable the hide-contract-detail-page-header-owner
feature flag.
Validation and Visibility Rules
You can set visibility or validation rules for page header actions, page tabs, sections within a detail page, and fields. For example, configure validation rules for contracts such as:
- If a user enters a currency value, they must select a currency type, or the system displays an error message.
- For contracts with the "MSA" agreement type, display the "Additional Information" section.
- If the contract number is not provided, display an error message in the contract number field.
- Display or hide actions and custom actions on the UI based on defined rule criteria.
For more information about how to add rules to actions, sections of the record detail page, fields of the record detail page, and tabs, see Applying Rules.
Examples of Validation and Visibility Rules
You can fulfill the following validation and visibility scenarios using rule configuration:
- Make an optional field mandatory or vis-a-versa (through field-level error message) if the condition is met
- Disable or enable a field depending on the condition outcome
- Display or hide a field depending on the condition outcome
- Specify a default value for a field if there is no existing value (through JSON rule)
Business Scenario |
Add Criteria Option |
Configuration in the IF section |
Configuration in the Then section |
Configuration in the Else section |
---|---|---|---|---|
Hide the Contract Start Date and Contract End Date if the Contract Term Type is "Perpetual" |
Field Criteria |
Field = Contract Term Type Operator = Equals Value = Perpetual |
Action = Hide Component = Field Field = Contract Start Date Action = Hide Component = Field Field = Contract Start Date | |
On the new contract creation page, disable the Total Contract Value field if the Contract Category is "Others", else enable it |
Field Criteria |
Field = Contract Category Operator = Equals Value = Other |
Action = Disable Component = Field Field = Total Contract Value |
Action = Enable Component = Field Field = Total Contract Value |
On the contract details page, hide the Payment Terms section for guest users if the total contract value is greater than $10000, else display it |
Field Criteria |
Field = Total Contract Value Operator = Greater Than Value = 10000 |
Action = Hide Component = Section Section = Payment Terms |
Action = Show Component = Section Section = Payment Terms |
User Criteria |
Field = Permission Groups Operator = Equals Value = GuestPermissionGroup | |||
On the contract details page, show a message saying "Please note that our company policy allows a maximum contract term of 36 months for contracts of type "NDA". |
Field Criteria |
Field = Contract Type Operator = Equals Value = NDA |
Action = Show Message Component = Page Level Field = Error Message = Please note that our company policy allows a maximum contract term of 36 months for contracts of type "NDA | |
On the contract details page, auto-populated the Notice Period field with "60" if the user selects "Fixed - Manual Inactivate" in the Contract Term Type field. |
Field Criteria |
Configure a Rule Condition JSON to check the value of Contract Term Type field Configure a Rule Action JSON to insert "60" in Notice Period field value |
Wizard Layouts
An overview of Wizard Layouts in CX Studio, which allows users to customize contract request form layouts for different record types, enhancing the user experience with a flexible page layout editor.
The Wizard Layouts of a contract request form is divided into multiple steps, with a master layout and individual step layouts for each master layout. You can customize the page layouts of a contract request form for NDA, MSA, and other record types to suit the users' needs using the improved page layout editor. If users create a contract request for a record type other than NDA or MSA, then the default master layout is used.
- Edit each page or step of the contract request form individually.
- Add or delete fields such as text fields, checkboxes, dropdown) on each step.
- Remove existing fields.
- Add rules to hide or show from master config.
- Add rules to hide or show from individual steps based on rules.
- Enable or disable fields based on rules from wizard layout for each step.
Use Case: Configuring Wizard Layouts for Contract Request Form
Imagine a legal department within a company that regularly processes contract requests. The team uses a contract request form that needs to be tailored to different types of contracts, some might require more detailed legal review, while others are straightforward. Using the Contract Request Form Wizard layouts, the team can modify the form by adding additional fields to capture specific contract details, such as special clauses or review checkpoints. They can remove unnecessary steps for simpler requests or even add entirely new pages to handle more complex contracts. If a new contract type requires extra information, the team can simply edit the layout, ensuring that the form is always aligned with their current needs and processes. This not only streamlines the process but also ensures that the form remains valid and user-friendly, avoiding any disruptions in workflow.
Typically, a contract request form contains standard steps such as Basic Information, Terms & Renewals, Key Dates, Miscellaneous, Upload Documents, with a Summary at the end. This use case explains how to create unique wizard layouts by configuring a master layout and individual steps. It showcases how to use Wizard Layouts to establish step rules and demonstrates how to conditionally display or hide elements based on these rules.
To access Wizard Layouts, click the App Launcher ( ) icon from the top-left corner > Apps > CX Studio, and select the
Wizard Layouts icon (
) on the left side. This displays the layouts list view, which includes a master detail page for the record types and detail pages for individual steps such as Basic Information, Terms & Renewals, Key Dates, and others.
Adding or Deleting a Field in a Step or Page
The MSA record is now updated to display the customized information in the step or page. Any added fields is visible, and any deleted fields is no longer be displayed in the Terms & Renewals section.
Hiding or Showing a Step in Master Layout
Example Rule # 1: Hide or Show Cross-Functional Steps
This task outlines the process for configuring a wizard to conditionally hide or show cross-functional steps based on specific rules. You will learn how to select a record, access the rules tab, and define conditions that determine the visibility of wizard steps.
After completing the steps outlined in this task, the wizard is configured to conditionally hide or show steps based on the defined rules. The visibility of the wizard steps now dynamically change according to the criteria set in the Rules tab.
Example Rule # 2: Hide or Show Fields in a Step
This task outlines the process for configuring a wizard to implement conditional logic to display or hide fields in Basic Information of an NDA record based on a specific rule.
After completing the steps outlined in this task, the wizard is configured to conditionally hide or show steps based on the defined rules. In an NDA contract request form, based on the rules set, if the Terminate Date field is greater than 02/03/2025, the system hides the Owner field and displays an error message at the page level stating, "Owner field is hidden using wizard rules." If the Terminate Date is not greater than 02/03/2025, then the Owner field is shown.
Example Rule # 3: Enable or Disable Fields in a Step
This task outlines the process for configuring a wizard to implement conditional logic to enable or disable fields in Basic Information of an NDA record based on a specific rule.
After completing the steps, the wizard is configured to conditionally disable or enable fields in the Basic Information of an NDA record. The fields will respond dynamically based on the specified rule, ensuring that users see only the relevant fields as they complete the NDA form.
Adding a Custom Step in JSON format to the Master Detail Page
In a contract management system, you may need to customize the workflow for handling Master Service Agreements (MSAs) and Non-Disclosure Agreements (NDAs). This involves adding specific steps to the Master Detail page to streamline the process and ensure all necessary actions are taken. For example, you might want to add a step for "Legal Review" to ensure that all contracts are reviewed by the legal team before final approval. This step can be added to the JSON metadata to make it part of the workflow. Ensure that each custom step has a unique ID to ensure proper identification and functioning within the wizard layout.