mattbbpl
Member
We are using Qsoft to manage JDE 9.1. We're currently using a very rudimentary security setup in a proof of concept system, but we're looking at setting up a more robust "finalized" security structure in Dev and, later, production.
Researching, I found the following two blog posts from QSoft:
http://www.qsoftware.com/blog/trends-and-best-practise-on-enterpriseone-roles/
http://www.qsoftware.com/blog/row-security-in-jd-edwards-enterpriseone-part-2/
Pertinent portions:
1) "As of the 9 releases, the character limit means that a User can have around 30 Roles – which is a lot."
2) "The research is proving this; we are witnessing a move to 2 Roles per User to try and solve these two issues. Why 2 Roles? The first Role is the functional Role, defining what a bunch of Users can do, for example AP Manager. The second Role consists of the User’s Row Security, which restricts what data a User can see, for example Company A."
3) Well, unless you are suffering from performance issues due to high numbers of Row Security records
The trouble arises from the fact that the powers that be don't view QSoft as a reputable resource (and number 3, even from Qsoft, is vague). I've found Oracle documentation which validates Qsoft's claims regarding sequencing issues, but I'm coming up empty when attempting to find Oracle-sourced documentation confirming the three claims above.
1) What character limit is being referred to here? Is there Oracle documentation I can point the powers that be towards that confirms such a limit?
2) I'm familiar with this setup from 3 other systems I worked on in a past life, and it makes sense to me. I'm just having trouble selling the idea without an Oracle recommended best practice stating that it's actually a good thing to implement. Is there any Oracle documentation stating any portion of this concept, in whole or in part, is a best practice?
3) Is there any Oracle documentation specifying what levels/numbers we should watch out for to avoid performance pitfalls? I'd like to be able to point to numbers to avoid regarding total number of security records, security records per user, etc.
Researching, I found the following two blog posts from QSoft:
http://www.qsoftware.com/blog/trends-and-best-practise-on-enterpriseone-roles/
http://www.qsoftware.com/blog/row-security-in-jd-edwards-enterpriseone-part-2/
Pertinent portions:
1) "As of the 9 releases, the character limit means that a User can have around 30 Roles – which is a lot."
2) "The research is proving this; we are witnessing a move to 2 Roles per User to try and solve these two issues. Why 2 Roles? The first Role is the functional Role, defining what a bunch of Users can do, for example AP Manager. The second Role consists of the User’s Row Security, which restricts what data a User can see, for example Company A."
3) Well, unless you are suffering from performance issues due to high numbers of Row Security records
The trouble arises from the fact that the powers that be don't view QSoft as a reputable resource (and number 3, even from Qsoft, is vague). I've found Oracle documentation which validates Qsoft's claims regarding sequencing issues, but I'm coming up empty when attempting to find Oracle-sourced documentation confirming the three claims above.
1) What character limit is being referred to here? Is there Oracle documentation I can point the powers that be towards that confirms such a limit?
2) I'm familiar with this setup from 3 other systems I worked on in a past life, and it makes sense to me. I'm just having trouble selling the idea without an Oracle recommended best practice stating that it's actually a good thing to implement. Is there any Oracle documentation stating any portion of this concept, in whole or in part, is a best practice?
3) Is there any Oracle documentation specifying what levels/numbers we should watch out for to avoid performance pitfalls? I'd like to be able to point to numbers to avoid regarding total number of security records, security records per user, etc.