Posted: 20 Feb 2019 16:08 EST Last activity: 12 Mar 2019 13:18 EDT
Processing case with wait shape not saving values to exposed col
We have a scenario where a s child case gets created, parent case waits for certain period of time and creates second child case based on certain decision logic.
To achieve this, we have used 'Wait Shape' with 'user can choose to continue process' checked. The wait process itself is working great. However, when the wait process resumes and creates second child case, an exposed column in the db is not populating values but the value do exist on Clipboard.
Instead, if user chooses to continue the process, everything works. Values exist in the exposed column and the clipboard.
Tried explicit mapping on the class rule but doesn't work.
Any help is highly appreciated.
***Moderator Edit-Vidyaranjan: Updated SR details***
Thanks for responding. I did thought of this. I believe it would be the same SLA agent that process wait shapes too. Either way, if it is access issue, I should see some thing in the logs and access should be for the whole table instead of one single exposed column.
Thanks for responding. The column is exposed using Optimization (Datamodel>Property>Actions>Optimize). There are separate nodes for WebUser and Background Processing. Since Wait shape uses same agent as SLA's, ServiceLevelEvents is configured as part of background processing (pega-procom). I believe this is OOTB. I am not sure what impact this would cause if this is changed to WebUser.
I am not suggesting changing the background processing node to a web node. I think it might be possible the background processing node is not aware of the property optimization. Is this occurring in a lower environment where you can restart the nodes to see if that addresses the issue?