A fix is available
APAR status
Closed as program error.
Error description
If a asset owner who is not a RAM admin, lifecycle admin, and a member of the review group, when he/she moves an assets to a state which is configured as 'Private Review', the asset does not exit the state event though the asset can by pass all the state's policies. So either the policies are not triggered or RAM does allow the asset to move to the next state (or exit condition).
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** If a asset owner who is not a RAM admin, lifecycle admin, and a member of the review group, when he/she moves an assets to a state which is configured as "Private Review", the asset does not exit the state event though the asset can by pass all the state's policies. So either the policies are not triggered or RAM does allow the asset to move to the next state (or exit condition). ? Rich's explanation: Looking at the code I think that kind of makes sense, but it shouldn't. It looks like the lifecycle during asset update is being accessed via the submitting user's permissions. What happens is that lifecycles have the policy results wiped when a non-reviewer accesses the lifecycle. So it doesn't see them during the submit (action) processing. But during lifecycle submit (other than verifying that the user has the authority to do a submit) the lifecycle access should have no restriction by users. --- Here is the testcase. 1. Go to Master Lifecycles ? Create a lifecycle ? Select Standard 2. Uncheck "Include asset owners as lifecycle managers" ? ?Draft State's permission - Override All ? ?Review State's permissoin - Override All ? ? 3. Create an Asset Type: BD1 ? ?Create a Community: Ben Defects ? ?Create a Lifecycle - Standard 4. Use the following settings to configure the lifecycle ? ?????Conditions - Asset type is BD1 ????Review -? Review (Manual action is Review) ????Review State's Policy -? Add Unique Asset Name Policy (Asset Save and Entrance to state) ????When the Unique Asset Name Policy is Approve go to Approved state ????Set the Review State as a Private Review state. ? ???? 3. Submit an asset as a BD1 type 4. Move from Draft to Review Expected Result: RAM will automatically move the asset from Review State to Approve State since the asset name is unique. Actual Result The asset stays in the review state.
Problem conclusion
Added an option to internally override the private review setting if the date such as the policy results is needed.
Temporary fix
Comments
APAR Information
APAR number
PM73072
Reported component name
RATL ASSET MGR
Reported component ID
5724R4200
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-09-17
Closed date
2013-04-02
Last modified date
2013-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
RATL ASSET MGR
Fixed component ID
5724R4200
Applicable component levels
R751 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSUS84","label":"Rational Asset Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 October 2021