We are currently using Pega Deployment Manager Service and have implemented a custom task to capture a Change Request (CR) number as part of our deployment pipeline. The user is expected to provide the CR number, after which the task should complete and the pipeline should proceed to the next step.
However, as shown in the attached screenshot, after entering the CR number and submitting it, the system repeatedly prompts for the CR number instead of completing the task and advancing the pipeline.
We have implemented the solution according to the guidance provided in the Could anyone suggest what might be causing this behavior or recommend troubleshooting steps to resolve the issue? Implementation has been done following the document: Implement-custom-task-behavior. Also one additional thing we observed, the overridden and customized activity runtask is run on the result of a OOTB Data Page: D_WorkItemList which is returning response code 200 for us but no content.The resource path invoked for this api looks like this: https://{baseurl}/prweb/api/DeploymentManager/v1/workitem?deploymentID=&pipelineID=Pipeline-BEUAV&taskStatus=“Open-Inprogress”,“Open-Ready”&stageIdInPipeline=&latest=&taskType=&environmentUniqueId=Env-XXXX&fetchOnlyTaskSummary=true&pyStatusWork=“Pending-Claim”&GetLongRuningTasks=true and the response string returned by this url is {“data”:[]}
