Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Johan Lauwens on Sep 19 at 1:08 PM You have to ensure that you maintain the org level values via the org level button on the menu bar (pop-up screen). Never maintain the org level values directly in the auth objects as this will indeed overwrite the derived role with same values.
1) Maintain your org levels via org level button (pop-up screen) in the master role
2) Push the derivation into the derived role
3) Maintain the derived org level values via the org level button (pop-up screen) in the derived role. Save and generate the derived role.
4) You can now test by changing the org level value in master role and push again into derived. The derived role should still have the derived org level values.
You can use * or any other set of values in the org levels from the master role. This would allow to have a master role that covers e.g. all plants.
| | | ---------------Original Message---------------
From: Alex Ayers
Sent: Monday, September 19, 2016 6:00 AM
Subject: Derived Role Issue - When We Update Master Role Values for Derived Role Change
When you push changes from a master role (adjust derived) then i. all
object level values and ii/. all org level values (e.g. plant 1002) in the
master will be pushed to the derived role.
Only blank org levels in the master will not overwrite org level values in
the derived role. This is why we typically do not maintain org levels in a
master role. If you are going to maintain any values then you should only
maintain those org level values that are consistent for all roles derived
from that master. |
| Reply to this email to post your response. __.____._ |    _.____.__ |
