Restricting DCT TYPEs in a Workflow

[Sorry to repeat this message but I typed the original subject line incorrectly.]

Is it possible to restrict which types of templates can be associated with a task in a workflow? I would like to have a workflow that is specific to a particular type of document and not other.

Thanks

Find more posts tagged with

Comments

Migrateduser

If your templating.cfg restricts a particular data-type (or even category) to a given branch (via a locations element,) and if your wft is restricted to that same branch in available_templates.cfg, then yes, only that data-type would be available while that workflow was running.

Another approach is to not put your data-type into templating.cfg at all, and instead use CGI tasks to envoke the data capture form and to do the generation. There's examples of this on the support site KB database.

bw

Bob Walden [bob.walden@interwoven.com]
Interwoven Education Group
IM: Yahoo, MSN bob_walden

SexyBeast

So are you saying then that there's no way to bind a particular workflow to a particular DCT except by restricting them to a specific branch? or else do custom scripting...

So for example, suppose I had a Workflow that was to be used *only* for, say, Press Releases; would need to create a "PressRelease" branch and limit the workflow and DCT to that particular branch.

james1

You could take the approach you describe.

You could also put code in your .wft that checks the files that are being added to the workflow at instantiation time. If they are not DCR's and are not of the correct type, you could put up an error message.

And/or, you could put an externaltask in your workflow that verifies the types of the DCR's attached to the workflow, and if something is awry, the workflow could abort or transition to a please-take-corrective-action usertask assigned to whomever you want.

I'm sure there are many other ideas employed by many other folks out there.

Hope this helps.
-- James

--
James H Koh
Interwoven Engineering