Best Practices for running Legacy .wft workflows in 6.7.1 Teamsite

Can anybody provide information in regards to Best Practices on running legacy .wft workflows in TeamSite 6.7.1. The new Workflow Modeler has changed the way workflows have been done in the past and we need to know what steps, or, best practices to take to allow the legacy workflows, with PERL and Javascripts in them, to be run now in 6.7.1. Any and all help will be greatly appreciated.

Find more posts tagged with

Comments

moonkhanna

your wfts should work as good with 671 as with previous versions however IWOV recommends use of WFM for future purposes..

as far your wfts are concerned, you may like to take care of flex roles in your wfts.. thats the only thing I can think of which has changed for the wfts

nipper

Can anybody provide information in regards to Best Practices on running legacy .wft workflows in TeamSite 6.7.1. The new Workflow Modeler has changed the way workflows have been done in the past and we need to know what steps, or, best practices to take to allow the legacy workflows, with PERL and Javascripts in them, to be run now in 6.7.1. Any and all help will be greatly appreciated.

Yup, it all still works. I even write new WFs in WFT rather than WFM.

That being said, you may want to make some changes to use some of the new 6.7.1 functionality. Since 6.7.1 stores email address, I changed iw_solutions_email to read it instead of email_map.cfg

You can do stuff like that if you want but you do not have to do anything

Adam Stoller

Can anybody provide information in regards to Best Practices on running legacy .wft workflows in TeamSite 6.7.1. The new Workflow Modeler has changed the way workflows have been done in the past and we need to know what steps, or, best practices to take to allow the legacy workflows, with PERL and Javascripts in them, to be run now in 6.7.1. Any and all help will be greatly appreciated.

The only thing you might have issues with is if you're using 6.7.1 SP1 (or later) and are attempting to use "non-OS Users" - then the perl-based WFTs and Perl-based externaltask and/or cgitask scripts might not work the way you expect.

If you're not using "non-OS Users" - then everything should continue to work the way it has in the past.