How to Retrieve axes screen field value to the VLF widget

This Q&A forum allows users to post and respond to "How Do I Do ....." questions. Please do not use to report (suspected) errors - you must use your regional help desk for this. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
Post Reply
JABIVULLAS
Posts: 2
Joined: Tue Sep 19, 2017 6:07 pm

How to Retrieve axes screen field value to the VLF widget

Post by JABIVULLAS » Fri Oct 13, 2017 3:44 am

Is there Anyway to get the field value of axes screen to the VLF widget,We are unable to get the field value of axes screen to the VLF widget to delete the cookie, can u suggest please.

MarkD
Posts: 321
Joined: Wed Dec 02, 2015 9:56 am

Re: How to Retrieve axes screen field value to the VLF widget

Post by MarkD » Fri Oct 13, 2017 9:35 am

You should be able to do this – and there would be several ways to do it.

Probably the simplest way to do this is to use the VLF's virtual clipboard - http://docs.lansa.com/14/en/lansa048/in ... 8_0840.htm

This gives you a place to store persistent or non-persistent information that is accessible to:

VL/VLF RDMLX coding
RDMLX logic can then then pass that information into VL-widgets are via the normal widget properties or as parameters passed into widget methods. Access to the virtual clipboard is via the #AvFrameworkManager.avSaveValue and #AvFrameworkManager.avRestoreValue methods.


RAMP scripts created in the VLF to navigate RAMP screens
RAMP scripts can access the virtual clipboard by using http://docs.lansa.com/14/en/lansa050/in ... 0_2425.htm and http://docs.lansa.com/14/en/lansa050/in ... 0_2420.htm
You need to remember that AVRESTOREVALUE in VLF-ONE is asynchronous - http://docs.lansa.com/14/en/lansa050/in ... f436222333

aXes scripts created just within aXes
aXes scripts can use the RAMP scripting functions. Put RAMP. In front of the name. eg:RAMP.AVSAVEVALUE
I don't think that an aXes script could viably use RAMP.AVRESTOEVALUE, so if you need to do that do it a RAMP script and make it available to the aXes script. That would probably involve involve using the SHARED object that is accessible to (and shared by) both aXes and RAMP scripting - http://docs.lansa.com/14/en/lansa050/in ... f224971316


RAMP scripting and aXes scripting can get and set field values from 5250 screens.
If that information is placed onto (or sourced from) the virtual clipboard it becomes accessible everywhere and can be passed into VL-Widgets.

Post Reply