When the user has configured a Chain Approval as per the documentation in converged platform for BWF Defining a chain of approvals they are presented with the below error: "Information. Processing approval. Refresh the case manually to view the latest changes"
Steps to replicate 1.- Login to BWF as Case Agent and open a case for which all the approvals have been completed, for instance "CASE-0000084272" 2.- You will see the message "Information. Processing approval. Refresh the case manually to view the latest changes" 3.- Click on "Show Approvers..." link, same message is displayed and no approvers are shown and Case is stuck in "Pending" status Take Browser Developer (F12) logs, the Case Agent use case shows "approvalID=null" in the GET approvers call. https://service_name-is.onbmc.com/api/com.bmc.arsys.rx.approval/rx/application/approval?application=com.bmc.dsm.case-lib%3ACase&request=CASE-0000084272&approvalID=null |
The issue is that in 20.08 it was recently discovered that the engine did retain the value of the status but this isn't happening in converged platform If one looks at the official documentation for this https://docs.bmc.com/docs/bwf213/en/defining-a-chain-of-approvals-1019260580.html To create a new chain of approval processIf you do not want to use the default approval process, you can create a new process in BMC Helix Innovation Studio.
You can see above that the step hasn't been added ideally there should be a 9.b step where the output map is explained, hence I've left a comment in the master document for BWF Solution: Open the Chain Approval Process in question in IS on this case it was https://servicename-dev-is.onbmc.com/helix/index.html#/com.bmc.arsys.rx.innovationstudio/process/edit/com.bmc.dsm.case-lib:Case%20-%20Chaining%20Approval
It has to look like this USE CASE 2: Customer is using OOTB Approval Flow and the issue is happening 1.- Approval Debug Log showing below INFO TenantId:0:Category -- Approval <THREADID: 0000000809> <OPID: null> <USER: Remedy Application Service > <IMPERSONATEUSER: null > <CATEGORY: ApprovalEngine> <USER-AGENT: Approval Server> /* Mon Mar 11 2024 19:10:12.9390 */ INFO TenantId:0:Command -- New-Details <THREADID: 0000000809> <OPID: null> <USER: Remedy Application Service > <IMPERSONATEUSER: null > <CATEGORY: ApprovalEngine> <USER-AGENT: Approval Server> /* Mon Mar 11 2024 19:10:12.9390 */ INFO TenantId:0:Source Form -- com.bmc.dsm.case-lib:Case <THREADID: 0000000809> <OPID: null> <USER: Remedy Application Service > <IMPERSONATEUSER: null > <CATEGORY: ApprovalEngine> <USER-AGENT: Approval Server> /* Mon Mar 11 2024 19:10:12.9390 */ INFO TenantId:0:Entry ID -- CASE-0000002242 <THREADID: 0000000809> <OPID: null> <USER: Remedy Application Service > <IMPERSONATEUSER: null > <CATEGORY: ApprovalEngine> <USER-AGENT: Approval Server> /* Mon Mar 11 2024 19:10:12.9390 */ INFO TenantId:0:Tag -- Manager Approval Flow The Manager Approval Flow is a sample flow included with BWF/IS and the system is taking this one as precedent move it to the bottom of the list or delete it and move your custom approval to the top from the Approval Flow Section in BWF As below example RCA: The 'Manager Approval Flow' was triggering first before the customer's expected flow. This was causing an error in the approval flow because they did not have the manager approval flow configured, so the approval was returning an error. |