Question

Hide a custom tab based on condition in IFS Cloud?

  • 1 September 2022
  • 4 replies
  • 228 views

Userlevel 2
Badge +7

I have added a tab with a group and a custom field on a (standard) form in Aurena. The standard tabs are visible based on conditions, but it does not seem to be possible for tabs added with page designer.  Only true or false. Is that right or am I missing something (version 22R1)?

/ Kenneth


4 replies

Userlevel 2
Badge +4

Correct, for custom tabs it’s currently only possible to have true/false, not a condition. So to achieve this you would have to go with a Marble level coded customization. There are other things for which you can control the visibility by a condition, even if the lack of a condition editor (already in the backlog) doesn’t make it thing for the faint-hearted , but tabs isn’t one of those things.

I’m sure @LakmaliRD, @ChanakaAlahakoon or @tofuse can provide more context background if needed.

Userlevel 4
Badge +8

Just to second Martins answer. Current released versions of the Page Designer will only support boolean values for all FndExpression types. This means that it is not only tabs but any attribute that could hold an expression according to the metadata schema. E.g. visible, editable, readonly, required. 

We do have in the backlog to provide a condition editor and when that is in place. All those attributes will automatically also support conditions in the page editor. 

The exception to this rule is where there are expressions set by core. In these situations the expression is visible and editable as is. However this is only because the expression can not be shown as a boolean value. To edit the expression like this is however not supported and thus not recommended. 

 

/Tobias 

 

Userlevel 7
Badge +21

R&D is providing expressions set by core. Nice as they are all json coding. Why not only include a json validator on these type of fields. It doesn't have to be a nice editor. Just leave it out for the next release/update better to have a proper condition set via json, than waiting for a nice editor. Those persons opening page designer have already learned that they should not have a faint heart to get the nitty gritty details working in the page designer.

Userlevel 4
Badge +8

With the release of 23R1 conditions are now enabled (not editor) in the Page Designer. In the places where you have attributes of type BooleanExpression it is now possible to input conditions, e.g., visible, required, editable.

See https://docs.ifs.com/techdocs/23r1/040_tailoring/225_configuration/200_client_configurations/310_conditional_fields/#conditional_value

 

Reply