Logging Client-Side recordWatch Events to the System Log

[ebarrette]

Hello,

We are trying to debug an issue with a client-side recordWatch that appears to affect some users but not others. It is very difficult to reproduce. While we have put remediation in place to improve the user experience, we would like to capture the event when this condition is triggered and send it to the system log for later review.

Is there a function available to do this, similar to console.log, but that writes to the system log instead?

Thanks,

Eric

[Ankur Bawiskar]

@ebarrette 

what's the issue faced?

[ebarrette]

We built a form using the CSM playbook and cloned a copy of the CSM intake redirect widget, updating only the default draft value to "17" to match our configuration. It should trigger only when users reach the end of the playbook and the request is no longer in draft, and for the most part it works as expected.

However, for some users, the redirect appears to trigger before they reach the end of the playbook. When this happens, they have to navigate back to the request and they lose everything they were filling out in that step.

I'm looking to send some data to the system log to gain insight into why the error occurs in certain obscure scenarios.