how to make it that we select one attribute on page2 as per some criteria some page3 attribute will get displayed
how to make it that we select one attribute on page2 as per some criteria some page3 attribute will get displayed
One thing to note is that the Agile GUI is not the most robust… say something like SFDC but we can do this. You would need to only allow the READ once the Page2 value is filled in. So the user would fill in the Page2 value, click Save and then the Page3 value would show. Not quite as sexy as one might like but it is possible.
I did just get this to work with two Page 2 fields:
– first, add the applicable role in an active “Enforce Field Level Read” privilege. This will hide any field that users do not have specific read access to read. Your default settings will probably hide any newly created flex field as users probably have read access right now to everything else. Make sure you test this as any field this role had read access to to ensure Agile didn’t hide any needed fields.
– go through your read accesses and strip read access on your Page 3 field. Make sure you do this on all Class levels (like Items, Documents, subclass, etc.)
– create a criteria where Page Two field = “yes” or not null or whatever you need it to be
– create a new Read access with the new Criteria. In the Applied To field, add your Page 3 field.
– enable this new Read access to the specific User Role (add the role from step 1 to the Privilege’s where-used tab)
And done – I got this to work so that as soon as I updated a Page 2 field to Yes and hit ‘Save’, Agile revealed the fields. Once I edited for “No”, Agile hid those fields and saved any data stored. Pretty cool. Biggest thing was how powerful “Enforce Field Level Read” privilege can be – make sure you do lots of testing to ensure Agile didn’t hide any necessary fields.
