I have some event action LBs running on an application that will hide/show fields, will it hide/show on layouts of applications that are explicitly specified in the LB action, or does the layout application also need to be specified in the hide/show action?
The logic being applied to the base application should also be applied to the layout application. So if you said hide field A, then it’ll hide field A on both versions. The only time the logic might get messed up is if you move fields into different rows or pages. So to give an example, if the base app has field A on row A and the layout application moves field A to row B, if your logic says to hide row A, it will hide field A in the base app but not in the layout app.
3 Likes
@joeyates23 So I have Application AppTest with Layout AppTestLayout
AppTest - Row A with Field A, B and C
AppTestLayout - Row A has Field E, F, G
I have logic which hides row A defining AppTest in the Hide Action. This would be expected to hide row A on AppTestLayout, Correct?
If that is the case how would I show Row A on AppTestLayout if that is my intention? Do I have to have a differentiator on the table? To know that I am on a layout record vs the base one? If the logic contains conflicting Hide vs Show actions what happens? From the example above, say I add a Show Action to Row A but define AppTestLayout as the Application instead. So now the logic has a Hide for Row A AppTest but a Show for AppTestLayout
Yes, I would expect row A to be hidden in this use case.
That’s definitely an interesting case. There isn’t a built in way to know if you are on the layout or not in logic.
For the conflicting hide/show actions, the last one will win. So no matter what application name you define, the last hide/show for a field is what will be returned and applied.
1 Like