Anybody who has worked with traditional HTML forms/PDF Forms know how cumbersome its making is in livelink. That is because the form template is rigorously tied to livelink code .The WF /Form developer sits in front of livelink many time not knowing it is submitting to a livelink RH(all those hiddens you should not touch).The submitted POST data is parsed by livelink code to do all the crazy things you want or your manager wants you to deliver to a customer requirement. There is a frantic look for help in this and after perusing the KB for a lot of stuff one finds something and basically in about a week’s time one is able to write something that works. Then comes the big questions like it all looks very kind of unaesthetic. So lo and behold some kind of WYSIWYG editor is employed and lots of colors aesthetics applies and then TONS of java script errors on views….The smart cookies will figure out the JS errors and proceed but all done it is a good effort to do anything with it. In fact most of the Best Practices you will find about editing form templates/forms/views were even taken verbatim from old discussions are findings I posted when I was developing forms etc for my wf /form project years and years ago and they still hold good. The world has gone to WYSIWYG and nobody hires programmers for doing html/JS etc .While OT has their own version of WYSIWYG editor kind of forms (eForms) or something like that it is also not very that easy or intuitive .At least for me when I tried it several years ago so take that with a pinch of salt.
Now compare that to Patrick Vitali’s Product. It is an amazing, jaw dropping revelation to how one uses livelink and its forms capability .I do not work for him nor do I get remunerated for this but a good friend. I also make it a point to reward good things without expecting anything in return. Mind Blowing that is the real word that comes.
I hope upcoming livelink wf /forms projects get a taste of this product soonJ