How to Use Rule Editor to make a KUT field mandatory based on checkbox

[Former Member]

Hi Experts

I have an Urgent requirement to set a KUT field mandatory based on checkbox.

requirement is, if checkbox is not checked then KUT field should be mandatory and mandatory sign the * should be seen there.

Please suggest me your valuable suggestion.

Please reply as soon as possible as it is urgent.

[PrasanthArya · Accepted solution]

I have defined a sample scenario based on your requirement as below and could see it is working

You can work on the same for accounts and once understood , you can apply the same logic to your fields.

Scenario : creation of a New account via Quick create

Conditions :

1) If Prospect check box is active , then Phone Number field is Not mandatory
2) If Prospect check box is not active , then Phone Number Field is Mandatory , * indicator is shown and Save Fails with Error message

Actions Taken :

Go to the Field Phone in Adapt
Select Change Properties
Select the hyperlink rule next to Mandatory
Against the Rule Name , select Create New rule and Enter a rule name.
Identify the Field from Field name , my field is Prospect which is a checkbox , I will select the Field Prospect which is Identified as Root.Prospect
Select Functions and define a rule with IF as condition in the format : IF(logical_expression, value_if_true, value_if_false)
So while I define my rule ,it will be IF(Root.Prospect, true, false)
Click on Apply and Save

So the Rule defined here satisfies the conditions above and completes the scenario with conditions.

[Former Member · Accepted solution]

Hi Prasanth,

Thank you for your suggestion and answer of my question this is really a good one. I did exactly you define and it is working well.

Thank you again.

[former_member259099]

Hi Guys,

What if my condition field is a custom field(that i created with KUT) i cannot see my custom fields for opportunity item in Rule Modeler. IS there any way to enhance these item custom fields for rule modeler and code list restriction purposes?

note: header level is working fine.

Orkun.

[juliabeer]

Hi Orkun, have you found a solution for this issue?

[former_member226]

Item level fields are not available as part of model rule validation. You have to either write a validation via PDI script or use some "ListModificationStructure" based field(but it has its own limitations)