we Browsing the pending cases from workbasket and close the cases using pxForceCaseClose . but the status not updated as what we given(Resolved) . they still remain as pending .
below steps are used to change the status .
obj-browse –
Loop over tempPage.pxResults
2.1. open-by-handle
2.2. Call pxForceCaseClose .
is there anything we need to do . ?
please suggest .
@KRISHKY Looks like pxForceCaseClose checks if the Status starts with “Resolved” and it is not ignoring case. Try with Resolved instead of resolved.
@KRISHKY Check if you are setting all the parameters correctly. Also, while looping through a pagelist, you can specify a step page to call pxForeCaseClose and set commit (parameter) to true.
@KRISHKY Hi krishky while looping instead of opening the case just set the pyId value to a parameter on temp page and pass that pyID param to pxForceCaseClose activity along with your status and also provide that temp page on step page for calling pxForceCaseClose activity it will work.
@satish kumar
Hi satish ,
after passing the Param.CaseID in pxForceCaseClose, still getting the same pyStatusWork in the Case instances . It is updated as resolved in Audit Logs , but remains as pending in case instances ..
please help me with the resolution .
@KRISHKY Resolved By Own .
if you face this kind of issue like pystatus work not updated after resolving the case using activity .
First check if you have dupliicate case for the same pzinskey . / same pyID .
if yes , then check the constraint on db table .& check if pzinskey is added as primary key in DB .
if not added pls add that .
in my scenario what happen is , the case status not updated when i use pxforcecaseclose method in activity .
it is inserting the new duplicate record instead of updating the existing record . this is due to unavailable of primarykey in the db table .
hope it helps .
Thanks
@KRISHKY
Can you add an obj-save after the pxforcecaseclose call and see if that helps or not.
