skeener
Member
Security Workbench bug: Applying processing option security through security workbench unlocks version line level security
We’ve had ongoing issues with users running batch jobs with data selection parameters that negatively impact our E1 production environment. In some cases, the result has been reduced system performance. In other cases, the result has been large volumes of incorrect data. One root cause factor is the lack of a valid option for completely locking down the interactive use of data selection parameters. We have broadly applied line level locking of data selection parameters, but creating enough versions to cover every possible combination of parameters is unmanageable and unrealistic. This means that we continue to require versions that have a combination of locked lines and unlocked lines that allow users to set their own data selection parameters, particularly the right operand. We’ve also considered implementing processing option security through the security workbench now available in Tools. The functionality available does provide some benefits, but has a major bug in that it will unlock the right operand in versions where line level security has been used to fully lock out a line.
We’ve requested a bug fix from Oracle that would ensure version line level security is not unlocked when processing option security is applied using security workbench. The response from Development stated that Data Selection security was intended to replace the old locking feature, therefore, they do not recommend combining them. Also, Development stated that this is the only request they have ever seen on the issue.
So, a few questions: 1) Has anyone else experienced this issue?; 2) Does anyone have recommendations on how to overcome the issue?; 3) Does anyone have interest in joining us if we continue to pursue a fix?
E1 8.12 (upgrading to 9.0)
Tools Release 8.98.2.4 (updgrading to whatever the latest and greatest is roughly six months from now)
We’ve had ongoing issues with users running batch jobs with data selection parameters that negatively impact our E1 production environment. In some cases, the result has been reduced system performance. In other cases, the result has been large volumes of incorrect data. One root cause factor is the lack of a valid option for completely locking down the interactive use of data selection parameters. We have broadly applied line level locking of data selection parameters, but creating enough versions to cover every possible combination of parameters is unmanageable and unrealistic. This means that we continue to require versions that have a combination of locked lines and unlocked lines that allow users to set their own data selection parameters, particularly the right operand. We’ve also considered implementing processing option security through the security workbench now available in Tools. The functionality available does provide some benefits, but has a major bug in that it will unlock the right operand in versions where line level security has been used to fully lock out a line.
We’ve requested a bug fix from Oracle that would ensure version line level security is not unlocked when processing option security is applied using security workbench. The response from Development stated that Data Selection security was intended to replace the old locking feature, therefore, they do not recommend combining them. Also, Development stated that this is the only request they have ever seen on the issue.
So, a few questions: 1) Has anyone else experienced this issue?; 2) Does anyone have recommendations on how to overcome the issue?; 3) Does anyone have interest in joining us if we continue to pursue a fix?
E1 8.12 (upgrading to 9.0)
Tools Release 8.98.2.4 (updgrading to whatever the latest and greatest is roughly six months from now)