As explained on JavaScript Type Mapping, JavaScript objects and properties will vanish when the script finishes. You can, however, use the global session object to store JavaScript objects between operation calls. This object exists for the duration of the current session, and can be accessed from any script during that session.
One session during service execution in Designer context is one request to the running service, e.g. one BPMN task, or one API call.
JavaScript_Session_Example
Click here to download a simple example model that shows how you can use transfer data between JavaScript operation calls using the session object.
Example
|
Script 1 |
|
|---|---|
|
Script 2 |
|
Related Content
Related Pages:
-
this Context
The contents of a target object in JavaScript are available via the this context. -
JavaScript Type Mapping
A comprehensive overview how JavaScript types and xUML Base Types are mapped. -
Unprovided Input Parameters
Explains how the xUML Runtime handles unprovided JavaScript input parameters. -
Using Maps in JavaScript
Explains how to handle maps in JavaScript. -
Calling xUML Operations from JavaScript
Explains how to call Designer operations from JavaScript. -
Working with the JavaScript Editor
This page describes the basics of the integrated JavaScript editor.