What are the consequences or risks if we hide certain field views from the global context via visible checkbox? Is that recommended way or do you have a better suggestion?
We would like to hide certain fields from view so that page visitors do not see all the content on the page.
Question
Consequences is if I hide certain field views from the global context via visible checkbox?
Hi,
(I think it would be better to raise this question in another area, like in Framework and Experience, to get more answers.)
IFS treats changes to the Global Context as a customisation. You can find more details in the IFS documentation here:
In my opinion, just because it is possible to amend the Global Context, it does not mean it should be done.
My reasons are,
1. In the future, it can be very difficult to debug or track down issues related to Global Context changes. I am not sure what type of information you are trying to hide, but it may be information that is used by other pages or configurations (such as workflows or events). So, you may lose visibility into why the system behaves a certain way for you.
2. You may not be able to clearly identify what standard functionality or behaviour is available to you if, in the future, you want to revisit your business processes or start using capabilities that were not previously used. Changes applied to the Global Context are passed on to other contexts as well, so losing visibility of the full solution is not a good long‑term choice.
3. If IFS changes application behaviour during an upgrade—even slightly (for example, a dependent field or logic), your upgrade could become more complex due to the Global Context changes you have.
Instead, you can create another context and make it behave globally by ensuring it is applicable to all relevant scenarios.
There are also other Community discussions on this topic that may be useful, for example:
Community- Aurena Context
Hope this helps,
Asanka
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.