Discussion posted 3/28/08 by Serenity Thompson, last edited 7/27/09 by Dave Sealey
Details:



steverk

I had opened a case with Serena, wanting to be able to restrict the revert function to only QA , at the QA promotional environments. This would keep the application team from reverting a package when they have already turned it over to QA. Serena said they currently could not do this, but have an enhancement request in to create this functionality. Serena also said that certain companies already do this.
Does anyone out there do this, that would like to help?
Posted 11/29/2007 1:28 PM

chgadm

Access to revert ChgMan pkgs in frozen status is controlled by a security entity. Take a look at your RACF or ACF2 etc. security setup for security entity "CMNREVRT", are there too many users defined to this rule? The security section of the ChgMan install guide can provide further details. CMNREVRT or CMNxREVR Revert packages to DEV status
Good luck.
Posted 11/29/2007 3:23 PM

tmavor

One clarification is needed -- Is QA the only environment where the code gets frozen before it is promoted? If it is not then the above is not that helpful. Otherwise it is the right answer because that is how the product is designed to work. I don't recall an exit for revert but sounds like a good enhancement.
One idea is to restrict revert in the panel so that it cannot be reverted when it is in QA and then create a batch job that the QA team can submit to do a revert if they need to. Ensure that the QA team can submit the job and your problem is solved.
Posted 11/30/2007 8:23 AM












Regarding this topic, we have recently become aware that the security part of revert is only checked once the first level of approval is completed. In other words anyone with security access to the application can revert a package that is Frozen prior to this point. See Solution S100736
"Resolution




Revert is available without special authority to packages that have been frozen but not yet approved. This allows a user to revert their own package before the approval process starts, even if they have not been granted access to the CMNREVER entity. For this reason, REVERT must always be on the menu."
We would like to change the code so that you can only revert if you have Revert access ie. CNMnREVR.
Any ideas?
We thought about changing the CMN@PRIM panel to remove the R Revert line unless the user had security, but are not sure where to make the change,



#ChangeManZMF
#oldforumpost
#post73ad70b948