Page 1 of 1

VLF-Win vs. VLF-One Default Instance Command Behavior Differences

Posted: Mon Jan 16, 2017 1:30 pm
by PatrickF
In VLF-Win, I can select an entry from an instance list and it will show the Default Instance Command Handler. As a user, I can then click a 2nd instance list command handler for the same business object command and show it. If I select another entry from the instance list, VLF-Win keeps me on the 2nd command handler, rather than reverting to the default command handler for the new instance list entry.
In VLF-One, it appears that when I select a different instance list entry, it resets the command back to the Business Object default command.
For an example, I am using the Examples Application in the VLF-One Home
Screen shots attached show when I changed the Command to view on instance list line 1 and what happened when I clicked on line 2. How can I get VLF-One to adapt the same behavior as VLF-Win in this respect ?
instance list entry 1.png
instance list entry 1.png (78.96 KiB) Viewed 8369 times

Re: VLF-Win vs. VLF-One Default Instance Command Behavior Differences

Posted: Sat Jun 24, 2017 12:42 am
by gerryc
Hi Patrick, did you find a solution to this?
I'm in the UAT phase of a VLF-Win conversion to VLF-One and the users have asked for the same behaviour....

Re: VLF-Win vs. VLF-One Default Instance Command Behavior Differences

Posted: Mon Jun 26, 2017 8:52 am
by MarkD
There is a new VLF version EPC141034 due out soon.

The (incomplete) What's New section is here : http://docs.lansa.com/14/en/lansa048/in ... 8_6925.htm

The item "VLF-ONE Applications Now Support Default Command Overrides" is the one you are referring to think?

Re: VLF-Win vs. VLF-One Default Instance Command Behavior Differences

Posted: Mon Jun 26, 2017 8:38 pm
by gerryc
Thanks Mark!