Is it very necessary to map BOPF Authorization field for BOPF Authorization

[al]

1.
Is it very necessary to map authorization filed? 

I did not map authorization field for the BO which implement BOPF authorization check.

It is successfully activated.  But got error message when doing check on the BO. 

If there is error why the BO activation  is success ? 

May I left blank under authorization field mapping?

2.
I define one authorization object “/XX/number” and assign 3 authorization fields “actvt; bo_serivce; /XX/number” . 

if adding  /XX/number  to authorization field mapping. 

Does It  mean I change other files would not trigger the authorization checking ? 

I want to  trigger the authorization check when user change any fields on root ,

how should I do?

[former_member190794]

Hi Alex,

using the authority concept in BOPF is optional but of course recommended. If you use the authority concept, you have to define the mapping between fields of the authority objects corresponding to attributes of your nodes.

At runtime, BOPF automatically evaluates that mapping and executes the authority check on that objects in order to hide instances that did not match the authority check. It is also not possible
to modify instances that did not match the maintained authority condition.

Even if authorization objects and fields are assigned to a concrete node, at runtime the static and instance-based checks will be propagated along the composition tree. E.g. authorization checks configured to ROOT node will be propagated to ITEM node.

Best regards
Tilmann