Page History
A VLF-ONE system IIP (eg: e.g., DF_OSYSTM) may now contain redefinable methods that permit advanced control of RAMP sessions:
avRAMP_StartSession | Executes just before a session starts. It allows the aXes URL, user, and password that will be used to start the session to be changed. |
avRAMP_ProcessAVSIGNALEVENT | Is It is a new faster, and simpler way to intercept AVSIGNALEVENT signals fired by your RAMP scripts. This is the recommended way to communicate state information from your RAMP scripts into your RDMLX code. |
avRAMP_QueryCanClose | Allows a RAMP session to respond to a uQueryCanClose request just like any normal VLF-ONE command handler can. |
avRAMP_QueryCanExecute | Allows a RAMP session to control whether a RAMP session request to execute will be allowed. |
avRAMP_EndSession | Executes just after a session ends. The primary roles role is to clean up any custom object reference in the session instance manager. |
avRAMP_SHOW_CURRENT_FORM | Executes when a RAMP script executes the SHOW_CURRENT_FORM function. |
...
Example 1 – Locking and 'off the path' tracking
Imagine that you create an a Visual LANSA object named #MySessionInfo that contains the properties:
- Locked (Boolean),
- LockMessage (String)
- OnUnknownScreen (boolean).
...
In avRAMP_ProcessAVSIGNALEVENT you watch for signals LOCK (with an accompanying lock message in the payload), UNLOCK, and UNKNOWNSCREEN that are signalled signaled from various places in your RAMP scripts.
...
Using the screen name supplied in the event payload, you update the screen usage collection.
Additionally, your IIP contains a private method named DumpScreenStats. It attempts to send the screen usage collection details to your server for storage in a database table that you will later use to produce some screen usage heatmaps. After the details are sent, the screen usage collection is emptied.
...