arputh Contributor.
Contributor.
214 views

KSC Move Request in Workflow

Jump to solution

We have a PMO step to put a Project in ON Hold status from anywhere in the workflow by making use of the ksc_move_request_workflow special command to reactivate the step that should be active / eligible as at the point that the project was put On Hold.

 

The Special command execute correctly but does not actually move the workflow:

Beginning command: KSC Move Request in Workflow Running PL/SQL procedure KCRT_REQUEST_UTIL.MOVE_REQUEST_WORKFLOW

Summary of parameters: REQUEST_ID=58986

FROM_WORKFLOW_STEP_SEQ=35

EVENT_NAME=FORCE_TRANSITION

RESULT_VISIBLE_VALUE=Succeeded

SCHEDULE_DATE=

DELEGATE_TO_USER_ID=

TO_WORKFLOW_STEP_SEQ=2

Special Command successfully run.

 
Does anyone know if there is an issue with this special command in 9.22?
 
Regards,
 
Alfred Puth
PPM Consultant
EOH Application Management
0 Likes
1 Solution

Accepted Solutions
Absent Member.. randull Absent Member..
Absent Member..

Re: KSC Move Request in Workflow

Jump to solution

Hi Alfred,

 

In "HP Demand Management Configuration Guide" (page 68). We can find following message:
"To determine which users or groups are authorized to act on a workflow step, you must set the permissions for the step."
Currently, they only added "PPM Administrator" group to permissions (as you mentioned. “All FROM and TO steps have "PPM Administrator" in the step Security tab").

That's the reason why you can use "Admin" user to run the command as expected.

This has been explained to us to be a security restraint, as users MUST always have permissions before acting on a specific step.
For security reasons when placed in workflow steps, the ksc_move_request_workflow "inherits" the permission of the user that is logged in at the moment of the execution of the command, hence it does not move between the workflow (it appears to be due to the security enabled in the workflow)

The only way to move from the steps it’s to explicitly add a user (admin in this case) that has both access to the workflow steps or a user that has access to both steps of the workflow.

You can try to add users or security groups to act on the workflow step.

Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
9 Replies
Absent Member.. AlexSavencu Absent Member..
Absent Member..

Re: KSC Move Request in Workflow

Jump to solution
Hi,

this is not clear.

Are you using an automated workflow step? A screenshot would be helpful.

Cheers
Alex

--remember to kudos people who helped solve your problem
0 Likes
arputh Contributor.
Contributor.

Re: KSC Move Request in Workflow

Jump to solution

Hi Alex,

 

Yes, Execution step.

 

See attached. Step 35 is still active and the move did not take place to step 2.

 

Let me give context. The workflow will start at step 30 which will activate step 1, 43 and 29.

 

Step 29 is a PMO function. When PMO put the project On Hold the process will run through 34 which will store the active steps by looking at which step is active less than 29 which will ensure that we store the correct step number in a hidden request field. PMO Resume project which will activate step 29 and run execution step 35 which is using the ksc_move_request_workflow special command to reactivate the step stored in the Hidden request field.

 

Thanks,

 

 

Alfred Puth
PPM Consultant
EOH Application Management
0 Likes
Absent Member.. randull Absent Member..
Absent Member..

Re: KSC Move Request in Workflow

Jump to solution

Hi Alfred,

 

In "HP Demand Management Configuration Guide" (page 68). We can find following message:
"To determine which users or groups are authorized to act on a workflow step, you must set the permissions for the step."
Currently, they only added "PPM Administrator" group to permissions (as you mentioned. “All FROM and TO steps have "PPM Administrator" in the step Security tab").

That's the reason why you can use "Admin" user to run the command as expected.

This has been explained to us to be a security restraint, as users MUST always have permissions before acting on a specific step.
For security reasons when placed in workflow steps, the ksc_move_request_workflow "inherits" the permission of the user that is logged in at the moment of the execution of the command, hence it does not move between the workflow (it appears to be due to the security enabled in the workflow)

The only way to move from the steps it’s to explicitly add a user (admin in this case) that has both access to the workflow steps or a user that has access to both steps of the workflow.

You can try to add users or security groups to act on the workflow step.

Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
Absent Member.. AlexSavencu Absent Member..
Absent Member..

Re: KSC Move Request in Workflow

Jump to solution
Hi,

From the graphical view looks like step 35 is still active. This is either because the step did not execute or it failed. Did you check the logs of the request?

On another note, I have a better implementation solution for the on hold functionality which will not create the crazy transition maze in the graphical view and you would be able to use it multiple times in same request. My solution is not 100% supported by HP, but it works.

Cheers
Alex

--remember to kudos people who helped solve your problem
arputh Contributor.
Contributor.

Re: KSC Move Request in Workflow

Jump to solution

Hi Randall,

 

That is how we normally configured the step, only "PPM Administrator" has access. (version 9.14 had no problems with this configuration)

 

I will add the PMO Security Group to resolve.

 

Is this new to version 9.2?

 

Regards,

Alfred Puth
PPM Consultant
EOH Application Management
0 Likes
arputh Contributor.
Contributor.

Re: KSC Move Request in Workflow

Jump to solution
Hi Alex,

Please can you mail me the solution.

Can always use a better solution.

alfred.puth@eoh.co.za

Thanks
Alfred Puth
PPM Consultant
EOH Application Management
0 Likes
Absent Member.. randull Absent Member..
Absent Member..

Re: KSC Move Request in Workflow

Jump to solution

Hi Alfred,

 

I don't think this is new. My question is this was working on previous versions?

Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
arputh Contributor.
Contributor.

Re: KSC Move Request in Workflow

Jump to solution

Hi Randall,

 

I found that it worked in 9.14 with only PPM Administrator security group.

 

Thanks for your assistance.

 

I tested after adding the specific PMO security group and signed in as one of the PMO's. Works 100%

 

Regards,

Alfred Puth
PPM Consultant
EOH Application Management
0 Likes
Absent Member.. randull Absent Member..
Absent Member..

Re: KSC Move Request in Workflow

Jump to solution

Excellent Alfred! I am glad to help you!

Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.