Contribute in GitHub:
Open doc issue|Edit online
Simulation script workflow
Each component which simulation state is set to Scripted has a Simulation Script (SS) defined in the Simulate tab.
Here is list of objects exposed to you for direct use from a SS:
- work – the work entry.
- conn – the entry retrieved from the lookup operation or directly from the OutputMap or null.
- resEntry – the entry that is used as a result if the operation being simulated requires a result to be returned; otherwise if the result will not be used, it is null.
- current – the entry found in the target system that will be modified or null.
- search – the SearchCriteria object defined by the user or null.
- method – a String object containing the name of the method that is being override by the SS.
The table below explains the methods being simulated, it shows when the SS will be invoked.
| Mode | Method |
|---|---|
| Connector: AddOnly | putEntry |
| Connector: Update | modEntry, or putEntry if the entry couldn’t be found |
| Connector: Delete | deleteEntry |
| Connector: Delta | modEntry, putEntry or deleteEntry (depends on inner logic) |
| Connector: Iterator | getNextEntry |
| Connector: CallReply | queryReply |
| Connector: Lookup | findEntry |
| Function component | perform |
Table 1. Method invocation according to mode
If a Connector is in Server mode with a Scripted simulation state it would still require to receive a request from a client. The SS will be called when the response is to be sent.
The internal lookup operation that is executed for Connectors in Update, Delete and Delta mode will be done internally and it won’t allow overriding from a SS like it does for the proxy AL.
Connectors in this simulation state will not execute the operation’s override hook if any.