Difference in wfmodeler and wfbuilder

What is the fundamental difference in WFmodeler abd WFBuilder.I have seen a bit of WFMODELER.Whats new in it?

Find more posts tagged with

Comments

What is the fundamental difference in WFmodeler abd WFBuilder.I have seen a bit of WFMODELER.Whats new in it?

Workflow Modeler is the new term being used for the WFT builder shipped with TS6.7 and on. Former one was using .wfb as its product extension whereas the latter one is using .ipm

For more information on Workflow Modeler.. read the KB article for Whats new in TS6.7 and ts.670.wf.pdf

Adam Stoller

What is the fundamental difference in WFmodeler abd WFBuilder.I have seen a bit of WFMODELER.Whats new in it?

WFB was (IMO - and MOPO* too) a poor attempt at providing a graphic interface to developing WFTs. It was built almost entirely in-house at IWOV - but not by the same people who developed and maintained the Workflow system.

WFM is largely (I believe) OEM'd using BPMN Business Process Modeling Notation - and represents a different way of designing and using workflows for TeamSite (data stored within TeamSite branch, subscriptions at the branch level from within TeamSite, etc.)

The "old" WFTs allow for embedded Perl code - and with the introduction of TeamSite::WFconstructor allow for an OO-oriented way to code WFTs (though not through WFB).

The "new" IPM files allow for referencing (or embedded?) JavaScript code.

In theory - the new system should be better over the long run - and is likely to see more in terms of feature enhancements - but since (at least for now) the underlying workflow engine used to process the workflows is remaining the same - the "old" WFTs (whether built with WFB or by hand [the "right" way]) should continue to work for a while longer. If IWOV decides to start making significant changes to the underlying workflow engine - then the support for the "old" WFTs may start to go away.

[*MOPO - many other people's opinion]

Ambuj

That’s really a nice piece of information..