wft's future

With 6.7.1 we are all encouraged by IW to use the new workflow modeler.

Reading the following article: http://devnet.interwoven.com/site.fcgi/techlib/56780

I got a little worried with the following wording:
[indent]Interwoven will continue supporting previously designed workflows with TeamSite, but customers should begin planning the migration of their workflows to the new Workflow Model with their upgrade to TeamSite 6.7.1.
[/indent]Does that mean that wft's will be dumped in the near future?

Find more posts tagged with

Comments

jed

With 6.7.1 we are all encouraged by IW to use the new workflow modeler.

Reading the following article: http://devnet.interwoven.com/site.fcgi/techlib/56780

I got a little worried with the following wording:
[indent]Interwoven will continue supporting previously designed workflows with TeamSite, but customers should begin planning the migration of their workflows to the new Workflow Model with their upgrade to TeamSite 6.7.1.
[/indent]Does that mean that wft's will be dumped in the near future?

Heh--If it is anything like the OpenAPI --> CSSDK swtich, they will forget to formally announce the EOL plan.

"Fortunately, it should be faster with the new graphical drag and drop interface"

Yeah. The original "workflow builder" and the "DCT builder" (forget the product name) were also supposed to be faster. Riiiight.

gzevin

Heh--If it is anything like the OpenAPI --> CSSDK swtich, they will forget to formally announce the EOL plan.

"Fortunately, it should be faster with the new graphical drag and drop interface"

Yeah. The original "workflow builder" and the "DCT builder" (forget the product name) were also supposed to be faster. Riiiight.

during the pre-launch of TS 6.0 I heard that it would be *very soon* that IWOV will cease perl-based WFTs and will introduce Java everywhere.
Probably with Kevin Cochrane's departure, the ideas departed with him Smiley Happy

IwovHeather

Hi Valentine,

We aren't planning to dump support for your existing WF's in the near future. Interwoven will continue supporting existing WF's through TeamSite 7.0.

We are trying to encourage planning now so that customers can migrate all their code to java slowly and start using the workflow modeler to manage their workflows. This is a proactive measure to try to alleviate workflow code changes in conjunction with an upgrade once the product no longer supports your old code. Once we have a definitive platform where the older scripts are no longer supported, we will update the KB and provide a new customer notification.

I hope this helps,

Heather

I got a little worried with the following wording:[indent]Interwoven will continue supporting previously designed workflows with TeamSite, but customers should begin planning the migration of their workflows to the new Workflow Model with their upgrade to TeamSite 6.7.1.
[/indent]Does that mean that wft's will be dumped in the near future?

abhi2005

Hi Valentine,

We aren't planning to dump support for your existing WF's in the near future. Interwoven will continue supporting existing WF's through TeamSite 7.0.

We are trying to encourage planning now so that customers can migrate all their code to java slowly and start using the workflow modeler to manage their workflows. This is a proactive measure to try to alleviate workflow code changes in conjunction with an upgrade once the product no longer supports your old code. Once we have a definitive platform where the older scripts are no longer supported, we will update the KB and provide a new customer notification.

I hope this helps,

Heather

sounds great. java can be universal for all dev activities to make things secure.
-->A

gzevin

sounds great. java can be universal for all dev activities to make things secure.
-->A

secure? in what sense?

ISCBorisB

secure? in what sense?

In none at all. Phrase semantics is as rich as my parrot chirping

gzevin

In none at all. Phrase semantics is as rich as my parrot chirping

well said