Governance & administration Configure and manage global controls and settings.Streamlined business apps Build easy-to-navigate business apps in minutes.Data connections Synchronize data across critical business systems.Secure request management Streamline requests, process ticketing, and more.Process management at scale Deliver consistent projects and processes at scale.Content management Organize, manage, and review content production.Workflow automation Quickly automate repetitive tasks and processes.Team collaboration Connect everyone on one collaborative platform.Smartsheet platform Learn how the Smartsheet platform for dynamic work offers a robust set of capabilities to empower everyone to manage projects, automate workflows, and rapidly build solutions at scale.The icon in the list view represents that the field is hidden due to the dependency rule set.When a trigger field is disabled, the condition will be in a strikeout mode.Trigger field is first outside the block and then moved inside the dependent block, dependency will not work and all the fields will be shown.Dependent field cannot be a trigger field.**Access Control: ** Show (Read + Write) or Show (Read) only, select checkbox to make it as a mandatory field work only on field level Note! Conditional mandatory rules will not adhere if Fields are mandatory in module levels. If List view columns include dependent fields, then it could take more time to load the list.ĭynamic Field allows you to choose picklist field and checkbox field for triggering. Mandatory - Show field or block always and conditionally set as mandatory in record view.įor example, Show Lost Reason Field always but if Sales Stage = Closed Lost, set Lost Reason field as mandatory. Show (Read + Write) & Mandatory - Show field or block and mark mandatory only if the conditions are met. Select Condition: Select Sales Stage equals ‘Closed Lost’.Select Dependent Field (to be visible on selection).Follow these steps to add a Dependent Field Let’s consider adding a dependent field for Opportunity module.
This action is to make a field(s) read-only when conditions are met.Įxample: If an Opportunity stage is Quote approved or closed, make Opportunity amount read-only.įollow these steps to add a Dependent Block This action is to conditionally make a field mandatory.Įxample: If a Case is closed, case resolution field is shown and needs to be filled by the agent closing the case. If all fields are hidden, then the corresponding block also gets hidden.Įxample: If a Lead is a B2C case, show fields relevant to a consumer, else show fields relevant to an Organization. This action is to show or hide a field(s) or a block when conditions are met. Go to Dependent fields/block tab of a module to define dependency rules.Define the picklist or checkbox field that will be used as trigger field in dependency rules.Define the blocks and fields in the layout using Module layout editor.When the customer selects Product A from picklist or a checkbox field, the fields which are related to Product A should be shown and when he selects Product B, the fields related to Product B only should be shown.” Prerequisites for setting up dynamic fields or blocks The customer doesn’t want to see the custom fields which are related to Product A when he is updating the Product B details.
Additionally, rules can be set to mark a field as mandatory or read-only.ĭynamic Fields are supported in List View, Detail View, Edit View and Inline Edit.Įxample: “A Customer sells Insurance (Product A and Product B), he has 120 custom fields which are related to Product A and there will be 120 custom fields for Product B. Dynamic business rules are defined at a module level and impact detail and edit views of a record keeping the clutter out of the views.
0 kommentar(er)
