Hi Team,
We are in the process of migrating our applications from lansa version 13 vlf to lansa version 14 (VLF-ONE). Observed that 'NAVIGATE_TO_SCREEN()' function in ramp script is not working in VLF-ONE. But we are using the same function which works fine in lansa vlf 13.
Immediately after the execution of ''NAVIGATE_TO_SCREEN()' function ramp script breaks/crashes and gives a message saying 'No Valid navigation path from 'Screen1' to 'Menu Screen'. Please see to the attached screen shot for your reference.
NAVIGATE_TO_SCREEN function doesn't seem to work in VLF-ONE
NAVIGATE_TO_SCREEN function doesn't seem to work in VLF-ONE
- Attachments
-
- Loan_Filter_Issue.PNG (58.93 KiB) Viewed 6965 times
Re: NAVIGATE_TO_SCREEN function doesn't seem to work in VLF-ONE
Please suggest is something that I miss here. Or suggest me any other alternative of achieving the navigation of screens.
Re: NAVIGATE_TO_SCREEN function doesn't seem to work in VLF-ONE
Run with trace mode on and examine what happens.
Re: NAVIGATE_TO_SCREEN function doesn't seem to work in VLF-ONE
From trace I understood one point that there is no proper navigation plan prepared from LoanScn1 to LoanScn2 screen.
But im more concerned about the function 'NAVIGATE_TO_SCREEN()'. Why this function doesn't navigates to the intended screen whereas it works fine in Version 13. Please let me know if anything substitute is there in place.
But im more concerned about the function 'NAVIGATE_TO_SCREEN()'. Why this function doesn't navigates to the intended screen whereas it works fine in Version 13. Please let me know if anything substitute is there in place.
Re: NAVIGATE_TO_SCREEN function doesn't seem to work in VLF-ONE
It should work in VLF-ONE.
Could you elaborate on your comment “whereas it works fine in Version 13”?
Do you mean:
(a) that the actual problem script and RAMP session you are using used to work in LANSA V13.
(b) a general comment that you have used NAVIGATE_TO_SCREEN in LANSA V13 with no issue.
If it’s (a) are you seem to be saying that the actual problematic script you are using works fine in VLF-WEB in LANSA V13 (since VLF-ONE has never worked in LANSA V13).
If you are using VLF-ONE RAMP with a former VLF-WEB RAMP script then there might be some complex reason for this problem, because VLF-WEB and VLF-ONE are architecturally very different products.
If it’s (a) or (b) then I would first double check that your RAMP definitions do correctly define a navigation path from the first screen to the second. If you are sure they do then you should report the issue to your local support organization.
Could you elaborate on your comment “whereas it works fine in Version 13”?
Do you mean:
(a) that the actual problem script and RAMP session you are using used to work in LANSA V13.
(b) a general comment that you have used NAVIGATE_TO_SCREEN in LANSA V13 with no issue.
If it’s (a) are you seem to be saying that the actual problematic script you are using works fine in VLF-WEB in LANSA V13 (since VLF-ONE has never worked in LANSA V13).
If you are using VLF-ONE RAMP with a former VLF-WEB RAMP script then there might be some complex reason for this problem, because VLF-WEB and VLF-ONE are architecturally very different products.
If it’s (a) or (b) then I would first double check that your RAMP definitions do correctly define a navigation path from the first screen to the second. If you are sure they do then you should report the issue to your local support organization.