uImplement functionality of original tree with new
requirements without
redeploying the client code after the initial deployment.
ØImplement small set of event listeners and actions.
ØUse a single API as the interface.
uOnly portions of the system residing on the clients’
CPU:
ØTree renderer
ØEvent listeners
ØAction performers
uAll logic and rules moved out of the client code and
into the database.
ØWhen future requests are made, the changes could almost
always be accomplished with a
minor database patch and no end user involvement.
uUpdated tree component success
ØDecided to use same concept to develop dynamic component
to build screens.