Javascript API onsave() function (14 Comments)

Topic by Marv Ferrer

Content

We utilize the Javascript API within the incident workspace to run certain tasks on onsave() events only. However, when I hit save from another ticket/contact tab, the onsave() function is triggered in the other incident. Shouldn't the onsave() function accessible only within it's own incident tab?

Steps to replicate:

1. Open or create an incident. Leave it open.
2. Open or create another contact or incident record. Then, save it.
3. The onsave() event within the incident in #1 also executes.

We are currently in Nov 14 release. There's no mention of this behavior in the documentation. Is this a bug?

Version

Code Block