| In VLF-ONE RAMP Applications
|
Details
|
|
Some scripting functions will be inactive
|
There are a number of RAMP scripting functions that are inactive when the application is running in VLF-ONE mode:
|
|
Some scripting functions have to be coded differently
|
There are some RAMP scripting functions that have to be coded differently:
These functions are asynchronous in the RAMP-ONE environment, so you invoke them and then you have to have a separate event handling function that will get the resulting data when the operation finishes.
See AVRESTOREAVALUE and AVRESTORENVALUE in VLF-ONE.
|
|
There are no screen wrappers
|
Chums (screen wrappers) are not available.
|
|
Special field handlers are different
|
Special field handlers (RAMP Popup prompters) have a different ancestor and are coded slightly differently (see DF_PRM*O examples for more details).
|
|
RAMP-NL is not supported
|
Only TS2 runtime mode is supported in RAMP-ONE.
|
|
There is no cross-domain limitation
|
The cross-domain limitation of RAMP-WEB is removed (for RAMP-ONE). The aXes URL can be in a different domain to the VLF URL.
|
|
BeginListUpdate / EndListUpdate are not required
|
It is not necessary to use BeginListUpdate / EndListUpdate when adding to the instance list.
|
|
Ancestors are different
|
Filters, command handlers and the instance list have different ancestors:
- Filters: VF_AC007 --> VF_AC007O
- Command handlers: VF_AC010 --> VF_AC010O
- Instance List: VF_AC012 --> VF_AC012O
|
|
HTMLAPI is not supported
|
The HTMLAPI scripting object is not supported.
|
|
V2 find path algorithm is always used
|
The V2 find path algorithm is always and exclusively used.
|
|
Private and unpublished RAMP APIs need to be tested
|
If you have used private or unpublished RAMP APIs or features in your scripting then they may not function and may need to be modified to work in VLF-ONE.
|
|
Multiple VLF-ONE RAMP session panes can be open
|
Multiple VLF-ONE RAMP session panes can be open simultaneously. This means 5250 sessions are managed differently.
|
|
There is no RAMP signon
|
VLF-ONE does not have secondary RAMP session signon capability. The RAMP 5250 session signon details used are those provided at initial VLF-ONE signon to or as returned by any custom user profile validator.
|
|
Closing the browser may not end the aXes session
|
In VLF-ONE RAMP, aXes sessions may not get closed if the user closes the browser window. (Currently this problem is restricted to the Firefox browser). So the designers of VLF-ONE RAMP applications should always ensure that the VLF tool bar contains an Exit button, and that the users are encouraged to end their RAMP sessions by pressing the Exit button, rather than by closing the window.
|