You could use 2 separate configurations and for the admin types who need more search functionality, give them an additional separate transaction (as a workaround)? Though that implies identifying these admin types up front with a unique role that would provide this additional transaction.
Or taking a different approach, why would the read-only field appear at all if they can't do anything with that field. If it's not, you could just remove the search field from the definition method couldn't you?
I just read about Context Based Adaptations, and was thinking in the role of the administrator an additional application parameter could be added, then at run time adapt either use - 2 configurations or hide select option for no admin types.
Cool. Still think it would be easier just to have 2 configurations, and even doing the switch between the two using code in the application code like SRM does but always like the idea of trying new things too 😉
That Context Based Adaptations sounds interesting. Is that only avail from 7.03? I can't find any FPM_ADAPTABLE* components in my 7.02 system...
If I understand it correctly, the configuration is chosen based on a application parameter - is that correct? The only downside I see is that if savvy users work this out then they could bypass your read-only restriction by adding/changing the URL parameters (assuming they can see the URL in the first place, that is). At least with the AppCC you can make the choice of the configuration based on an actual role and protect it it from external influences. But then your requirement might be a usability thing not a strict, security requirement...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.