When thinking about such things like this, I tend to think in terms of
'classic' OO strategies like inheritance and polymorphism. T5 is really
big on services and annotations, which may actually provide a more
flexible solution for this problem. At first the obvious two solutions
occurred to me
"The activate event handler may also return a value, which is treated
identically to a return value of an action request event trigger. This
will typically be used in an access validation scenario."
Missed that little gem ;-). Thanks
Nick Westgate (Work) wrote:
Read the docs for onActivate().
Read the docs for onActivate().
Cheers,
Nick.
Chris Lewis-5 wrote:
>
> Hello,
>
> I'm redeveloping an application in T5 that will have several wizard-like
> form sequences. Basically a few forms on a few pages that must be
> followed in order, with the ability to revisit/jump around in ste
Hello,
I'm redeveloping an application in T5 that will have several wizard-like
form sequences. Basically a few forms on a few pages that must be
followed in order, with the ability to revisit/jump around in steps
already completed. A wizard should prevent steps (pages) from being
accessed ou
