Details
-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
Description
User story
When receiving script errors, I want explicit error messages so that I can identify the root cause easily.
Background
For execution errors in scripts of input-output mappings and delegates, the current error message does not specify the root cause of the error.
This makes it harder to identify which script is causing the error.
Current error message:
unable to evaluate script:ReferenceError: "code" is not defined in <eval> at line number 1
Desired error message:
unable to evaluate script for activity "mytaskid" output mapping for variable "myname":ReferenceError: "code" is not defined in <eval> at line number 1
Acceptance criteria
- Scripting errors specify where the error occured
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- mentioned in
-
Page Loading...