2 Replies Latest reply on Apr 20, 2017 2:11 PM by Jeo123

    Location Specific Security Roles


      In FDM Standard edition, there was functionality in place to allow assigning Intermediate Security Levels to a suer for a sepecific location.  As an example, our I8 users could make map changes, while I9 users could not.  Using this functionality, we could allow them to make map changes on certain locations, while blocking map changes for centrally managed maps.


      In FDMEE PSE's as of this post have been applied) it seems this functionality does not exist.  Can anyone else confirm this, or is there something special that needs to be done to grant I8 for one location and I9 to another?


      Currently using the Location Security groups results in the user having Intermediate 8 level permission for both locations which lets them change the maps managed by corporate.

        • 1. Re: Location Specific Security Roles
          Francisco Amores



          currently you can't have different security at location level.


          FDMEE does role security where you can say what can be done for each role and then location security where you can say to which locations users have access.


          You would need two users...


          I suggest you create a SR with Oracle to double check with them if they have a workaround for this. Otherwise please raise an Enhancement Request



          • 2. Re: Location Specific Security Roles

            Yeah, I was afraid of that.  I opened an SR last night aroudn the time I posted this and got their response this morning.  They've basically confirmed what you said:


            5. If yes, this issue was raised in Bug 24790133 : (ENHANCE LOCATION SECURITY TO PROVIDE ACCESS BY LOC WHEN USER HAS MULTIPLE LOC). However, Development has determined that this is NOT a bug and is the designed current functionality of FDMEE (which IS different that the way it functioned in FDM). FDM and FDMEE are two separate applications. Even though FDMEE does retain some functionality from FDM, there is no guarantee that all the same functionality from FDM is carried over in FDMEE.

            6. That having been said, Development created an Enhancement Request (ER) for this issue (25719955). However, to date, there has been no release date for this functionality or acknowledgement that it will be added to a future version of FDMEE.

            7. Because this is the current functionality as designed for FDMEE, there is no workaround published for this issue. Development has suggested that the restriction to add/modify mappings should be handled by corporate policy.


            So that's unfortunate, but thanks.