I don’t think you can do that in Page Designer, the Next Command is based on this logic

As far as I know Assistant Commands for Step Navigation are not visible/editable in Page Designer, so you’d need a customization of the assistant to modify this condition.

Hi ​@KKSloane,

I checked in 25R1, and the application behaviour is as per expectation only. Next button is not enabled until values for the mandatory field are entered. 

Seems like a bug for 24R2 that has been addressed in 25R1. Please raise a support ticket.

Regards

Abdul Rehman

I have just pushed some documentation that highlight this issue: 

Required Attribute

The `required` attribute is used on a field elements to indicate that a field **must be filled out before form submission**. It is a **Boolean Expression attribute**, meaning that if it's present on an input element and evaluates to true, the field is considered mandatory.

Key Behavior

• Applies to `Entity Attribute`, `Field Element`.
• Prevents form submission if the field is empty or has no valid value.
• Triggers the browser’s built-in validation UI (e.g., message saying "Please fill out this field").
• Does not override  `readonly`, those fields are ignored during validation.

Important: If `required` is set on the entity attribute, the layout field cannot override and revoke it. This ensures that data integrity rules at the model level are always enforced, regardless of UI configuration.

Conditional 

Required is of type `Boolean Expression` which means that it can be either static `true` or `false`, or conditional. See nConditional Syntax](../310_conditional_Fields/300_condition_syntax/) for details.

Required Attributes in Assistants

By default, a field marked as required in an assistant will appear as mandatory in the UI, but it will not enforce that a value must be entered unless validation is explicitly enabled.

In the legacy design of Assistants, step validation was manually defined on the Next and Finish commands. Later, a generic framework-based validation mechanism was introduced. When Step Validation is enabled, the framework automatically evaluates required fields and field-level validations, and accordingly controls the Next and Finish buttons.

Due to backward compatibility constraints, this option cannot be enabled by default for all existing assistants. Therefore, developers must explicitly enable Step Validation to activate this behavior.

Step Validation - This is an optional attribute on the Assistant element.

To enable it:

1. In Page Designer on the assistant element, click (...) to toggle optional attributes visible. 
2. Set `Step Validation`to 'Enabled'

Important: For the same reason that Step Validation cannot be enabled by default, you should not assume that enabling it will work seamlessly with existing assistants. In some cases, it may not be possible to add a required custom attribute or mark a standard field as required in an existing assistant. This is a known design limitation.

Hi ​@KKSloane,

Found a KBA which was written on a very similar issue: KB0084662.

But unfortunately, I couldn't find the “Next” command button from the page designer hence, the solution provided on the KBA could not be executed.

Furthermore, I too noted that this has been corrected with IFS Cloud 25R1.

Best Regards,

Uvina Jayamaha.

Thank you. We just got to 24R2 - I don’t know when we’ll move to 25R1. 

Hi ​@KKSloane,

I was able to further check into this issue, and it seems that when a Business Rep is automatically fetched when going into the New Business Opportunity window,

If the user manually removes that Business Rep and fill the rest of the fields, the system will not allow the user to go to the next step.

I believe you are facing the above problem because a default Business Rep is not getting fetched when going into this window. In order to get it fetched, the user you are using should be registered as a Business Representative.

I believe this is the same behavior in IFS Cloud 25R1 as well.

Best Regards,

Uvina Jayamaha.

Hi ​@Uvina Jayamaha,

It's great to know that you are trying to replicate the issue 

I have a suggestion for your test plan. Please remove Stefan Guide (User Id you logged on and created test plan) as a Business Representative, and then recreate a new business opportunity. This time value for Main Representative should come null since system would not find default value. 

Check whether reported issue gets replicate.

Regards

Abdul Rehman 

Hi ​@Abdul,

Thanks for the input and yes, you are correct, when a default value is not fetched for the Business Rep, the “Next” button is not greyed out and users can move forward with it. Hence, the issue is replicated.

However, if a Rep is automatically fetched and if we remove it manually, in that case the “Next” button is greyed out, in that situation the system is working as expected. This is the observed behavior in IFS Cloud 24R2.

Best Regards,

Uvina Jayamaha.

Hi ​@KKSloane,

Your issue has been replicated, and all thanks to ​@Uvina Jayamaha 

You need to define an internal SOP to avoid business opportunity record creation without the Business Representative value entered. Users having full access to the New Business Opportunity wizard and Business Opportunity screen, should be defined as Business Representatives mandatorily.

Though I will still consider this a bug since the system allows creating a business opportunity record without entering mandatory information. Please report this to IFS R&D so that this can be fixed with the future release.

​@IFS RD Product Management 

Regards

Abdul Rehman