Re: Chapter two: Rules to dynamize screen

Hello James, No worry i wasn't active due to the situation we are aware of... I plan to get back into the subject in the coming weeks. Regards, Gil On Fri, May 15, 2020 at 04:08:07PM -, James Yong wrote: > Hi Gil, > > Sorry for the late reply. > I agree that button actions should be

Re: Chapter two: Rules to dynamize screen

Hi, After gil remarks and test with the POC-Vue.js We are now working with two new "action" usable by link - hyperlink * set-area * set-watcher and in container, we have added attribute watcher-name, and using auto-update-target as target set-area is used to update a containerId, and, most

Re: Chapter two: Rules to dynamize screen

HI Gil, In your posting your mentioned: In previous thread Can you provide a link to that thread? Met vriendelijke groet, Pierre Smits *Proud* *contributor** of* Apache OFBiz since 2008 (without privileges) *Apache Trafodion , Vice

Re: Chapter two: Rules to dynamize screen

Hi Gil, Sorry for the late reply. I agree that button actions should be decoupled from forms. Shall we continue with Part 3? Regards, James On 2020/01/10 17:58:59, Gil Portenseigne wrote: > Hello ! > > In previous thread we focused on the process of how to define a dynamic > workflow that

Chapter two: Rules to dynamize screen

Hello ! In previous thread we focused on the process of how to define a dynamic workflow that raises some questions. Let's go back to our principles: we have to find simple things, limit the possibilities (do little but good) and remember that on the backoffice it's end-users who are focused on