Highlighted
Established Member..
Established Member..
424 views

Request Type Buttons not working

Greetings,

HP PPM version 9.22 running on Linux

We create a Custom Request using a pl/sql procedure which updates the kcrt_request_details_int and kcrt_requests_int tables and then runs the kcrt_request_int.run_interface.

While the request gets created without any issues with all the data that we pass, the buttons fail to work. Clicking on the action buttons + Cancel button does nothing. I can see a grey rectangular border around the buttons which I think is due to this issue. (attaching the screenshot).

Also, note that the issue is only with the requests that are getting created using the custom procedure from the background. Rest of the request types have no issues whatsoever!

What are we missing here? Any inputs are greatly appreciated.

Thanks,

Arjun

 

0 Likes
4 Replies
Highlighted
Absent Member.
Absent Member.

Hi,

The step in which the workflow has failed, is an executable step? Have any error in link "Trasition Details"?

I ask you these questions because to see your screen shot, seems to be an error after it is performed an executed step.

Regards.

0 Likes
Highlighted
Established Member..
Established Member..

Hello,

 

That is correct. We ahve an execution step in the very buginnning of the Request Workflow that creates a child package.

If I remove this execution step and create a request, the buttons work just fine. 

How are we creating the child package:

We are creating the child package using a custom pl/sql procedure which feeds the KDLV_PACKAGE_INT & KDLV_PACKAGE_LINES_INT tables and then runs the interface report thus creating the package.

What is that we are missing here?

 

Thanks,

Arjun

0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

You are seeing the override buttons because the user you are logged in as is on the step security for the Bi-Weekly Package Workflow step.  Can you post your workflow and the contents of the Execution step?

-- Remember to give Kudos to answers! (click the KUDOS star)
0 Likes
Highlighted
Absent Member.
Absent Member.

Hi, 

For The solution, i Understood that the execution step is the first step in your Workflow. 

Try Adding Or step before the execution Step, i.e. The Or step as first step of workflow. 

Let me know if this works for you. 

-- Remember to give Kudos to answers! (click the KUDOS star)

Thanks

Neha

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.