Posted: 9 Nov 2016 6:24 EST Last activity: 26 Nov 2016 2:23 EST
Automatic Case Not Updating Work Status
We have a purely automatic case type which runs in the background, fired at a certain time by an agent. It consists of a few stages each with a few processes and what we would like is for a user to be able to view the progress of the case in real time by checking the audit log and current status of the work item. Each process is simply a utiltity calling an activity (to do various bits of processing, calling stored procedures etc), with some error handling. At carious points (e.g. the end of each process) we update the status and audit log.
However, it seems that the status and audit log only get updated in bulk once the whole case either gets to an assignment shape or resolved. So I was wondering if anybody had come across this in a completely automatic case and knew of a way to force the work item to update without using an assignment?
I never worked on automatic cases like that myself but I guess it depends on your Commit operations. Are you supposed to have "Commit" during this process or is it just running from beginning to the end with a final "Commit" operation ?
Thanks LASSM, mentioning Commit has been very helpful. If I add a Commit operation to my activities/flows then the audit trail is indeed getting updated as the case moves along. I think that should suffice for what I need.
Hi Could you please help me to accomplish a purely automatic case type creation. I have similar requirement but need 4 case types to be created on click of a button which invokes 4 services which will give response for each case type (as resolved, pending) and repteadly invoke the services if one of the service failed untill status in the response is resolved.
Posted: 4 years ago
Posted: 26 Nov 2016 2:23 EST
Santanu Bhattacherjee (Santanu)
Senior Manager - Sales Automation
Generally history should be written when an assigned is saved , routed, completed , created etc. So everything is almost with assignment. Thats why you are seeing the history is getting written like that in your log.
As a next step, please review the Decision tree work-FilterHistory and make the modification to capture even utility level operation.