RELATED IDEAS
Restricted fields for Portal but not REST
Please, fill in the below fields to enable the processing of your idea.
Who would benefit? |
Customers with Application Templates of Edit Templates where fields to control status, audits, ids etc are required, but must not be edited by the users themselves |
What impact would it make? |
Users with restricted fields can't find and edit fields that are restricted, but the Edit template can still update the fields using the current user context. |
How should it work? |
A setting on Restricted Fields to ignore the restriction in the REST API. |
Why is it needed? |
To allow critical functions not to be tampered by users themselves. |
Additional feedback, background or context:
A new column with "Ignore REST" with a checkbox:
Another method would be to use two new restriction types, but should be carefully implemented not to impact any existing functinality related to restricted fields:
