Page 1 of 1

aXes 4.2 - choreographer

Posted: 06 Aug 2019, 23:47
by Joerg Hamacher

axes 4.2 has the new feature "Choreographer". I tried this functionality and have two questions:

1. How can I prevent that all the screens that are on the way to the final destinations will be shown? I suppose this feature is very helpful but daiplaying all those screens is a little bit annoying for the end user.
2. When I leave the final destination screen (e.g. by pushing F3) I want to return into the calling screen. How can this be reached?

Many thanks in advance and best regards,

Re: aXes 4.2 - choreographer

Posted: 10 Aug 2019, 01:42
by Dino

If the user press F3 in the screen, the onLeave event is activated for the Screen, in extensions.

You could record the steps to get out in a choreographer sequence, save it like LeaveOrder
choreo01.jpg (45.21 KiB) Viewed 325 times
then put an EXECUTECHOREONAME("LeaveOrder"); on the onLeave event.
choreo02.jpg (477.65 KiB) Viewed 325 times

Re: aXes 4.2 - choreographer

Posted: 20 Aug 2019, 18:05
by Joerg Hamacher
Hi Dino,
thank you for this information. This is really a good possibility and I did not think about this before.

But I see the problem that one destination screen can be linked with different starting points.
Let's say we have 3 screens (A, B, C) and from every of those 3 screens we make a choreographer sequence to screen D.
Now I need to know from which starting point screen D was activated - and I have to create a sophisticated java script to travel back to A, B or C.

I suppose something like that can only be realized by using lots of USERENV variables, but I would prefer that aXes does this itself in an automatic process - considering the hundreds (if not thousands) of screens and possible links we have in our own ERP system.