Getting error "Make Decision method is disabled or cannot be run" when approver is trying to approve the request

Hi,

Take a look at the request approval history (in Manager) for this request.  From the sound of it, the request is considered complete after the first step is approved.

HTH, Barry.

When I approve the request and submit it, it does not do anything and I still see the same approval page. When I try to approve the again and submit it, it throws this error. Also, it is not even assigning system role to the user for which I approved the request. In user overview, it shows this role in Active product request but system role is not assigned

Is this a custom approval workflow?  Sounds like there is something wrong in your workflow.

Yes, this is custom approval workflow but we are using OOTB approval procedure and I understood from my colleague that wherever we are using OR approval procedure, we are facing this issue

Which CU do you have applied?

What is CU?

If you are asking about customer, we have created custom ITShop, shelves and customers. Requester, recipient, approvers have access to this shop as I can see these users in Customers

We tried OOTB ITshop structure, created one level approval workflow with CM as the approval procedure still we are facing same issue. When approver tries to approve the request, in first attempt page only loads and does not do anything, however in the backend it seems that request gets closed with Assigned status. But, because approver still sees the same page, he tries to re approve the request and this is when we see the above mentioned error. So, even if the request is approved in the backend, system role does not get assigned. What can be the issue

https://support.oneidentity.com/download-install-detail/6132511

Cumulative Update package

A cumulative update includes one or more transport packages with resolved issues for an LTS release. The individual transport packages are combined into a cumulative transport package. The cumulative transport package settings specify the conditions under which the individual transport packages are installed and the order of installation.

This cumulative update 3 contains the fixes provided with cumulative update 1 & 2. There is no need to install CU1 or 2 before installing CU3.

The list of the resolved issues included can be found in the release notes.

Determining if this cumulative update is needed:

The version required to install this cumulative update is 9.0 LTS.

https://support.oneidentity.com/download-install-detail/6132511

Cumulative Update package

A cumulative update includes one or more transport packages with resolved issues for an LTS release. The individual transport packages are combined into a cumulative transport package. The cumulative transport package settings specify the conditions under which the individual transport packages are installed and the order of installation.

This cumulative update 3 contains the fixes provided with cumulative update 1 & 2. There is no need to install CU1 or 2 before installing CU3.

The list of the resolved issues included can be found in the release notes.

Determining if this cumulative update is needed:

The version required to install this cumulative update is 9.0 LTS.

CU3 is already installed still we see the same error

Maybe this is related to your other thread  RE: Operation "Procedures for creating approval methods" stuck in DBQueue, shown as IsReset=1

maybe. Can you let me know how shold I check these custom approval procedures and what should I look into these?

I could resolve cusotm approval procedure issue which I had posted in other thread still this issue persists

DId you try contacting support?

I have raised SR but there is no response from them

Are you still seeing errors in the database journal?

In regards to support, I am unable to provide support instead of support. :-)

There are no errors in database journal now. I checked below link as well since I am also facing same issue but do not see the resolution here

 Approved ITShop requests does not result in assignment  

Hello Markus,

I could resolve this issue. The problem was with the custom process written on pwo table on "ORDERGRANTED" event. The generating condition was not right in this process which was causing the issue. The problem is web portal did not throw this error these many days and so we were not able to figure it out. Thank you for your support.