Difference: RBSSetupSetConfiguration (3 vs. 4)

Revision 42016-09-12 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="520RoleBasedSecurity"

Setting RBS Configuration

Line: 21 to 21
  Status: Active/Disabled. Controls whether RBS or normal Appx security is active. If 'Active', then RBS rules are enforced. If 'Disabled', then normal Appx security applies. Note that the setting take affect for new logins as soon as you click 'Save'. If you have not completed all the set up steps before clicking 'Save', then users logging on may be denied access, depending on your other settings here.
Added:
>
>
NOTE: Role Based Security is NOT enforced when running processes directly via Option 99 from within Application Design.
 Multi-Role: Disabled/Select/Combine. Disabled means a user cannot belong to more than one Role at at time. This is enforced during 'Security Hierarchy Maintenance'. You may want to set this during initial setup, while still leaving the Status at 'Disabled'. Select means the user can belong to more than one Role at a time, and they will be prompted for which Role they want to use when they log on.
Combine - means the user can belong to more than one Role at a time, and the permissions from all Roles will be combined. In this case, the following rules apply:
- For process/file/field security, if any Role would allow access, then access is granted.
- For Inactivity, if any Role would allow the user to log on, then log on will be allowed.
- For Timeout, the longest Timeout period of any Role will be used.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback