how to restrict workflow base on dct type?

I want to restrict workflow base on the dct type? There are some templates can access the workflow but not all.

Can i configure in available template.cfg?

thanks

Find more posts tagged with

Comments

Migrateduser

I'll have to assume you're referring about TS 6.5, since you left that part out and no, there is no OOTB support for limiting access to a workflow based on the template type. This seems to be a fairly straight-forward thing to check for in the wft, itself.

Dave

nipper

I want to restrict workflow base on the dct type? There are some templates can access the workflow but not all.

Can i configure in available template.cfg?

thanks

Not supported.

You *used* to be able to, in the branch specification, have the path down to a specific directory and it would run or not run the workflow.

I do stuff similar to this by using the perl preprocessor and erroring out if it is not to be run for some reason.

This is not nearly as nice as using available templates, since the user will need to choose the correct WF.

Or you can make a more complex WF that will understand what steps are needed for that circumstance.

Andy

Migrateduser

Or you can make a more complex WF that will understand what steps are needed for that circumstance.

This is what I was referring to. You could have the wft write a two step workflow (something as the starttask and an endtask) so doesn't really DO anything but if the DCR is of a certain type, have it write out the complete spec.

Adam Stoller

Not supported.

You *used* to be able to, in the branch specification, have the path down to a specific directory and it would run or not run the workflow.

I do stuff similar to this by using the perl preprocessor and erroring out if it is not to be run for some reason.

This is not nearly as nice as using available templates, since the user will need to choose the correct WF.

Or you can make a more complex WF that will understand what steps are needed for that circumstance.

Andy

Actually - for Templating-invoked workflows (tt_data) you were always limited to the branch path (new_job and submit workflows allowed processing down to the directory level).

As has been suggested, a workflow "shell" or "facade" could be created that is responsible for determining what workflow should be called for the associated DCR and then calling it and ending - or if there is no appropriate workflow for the DCR - just end (with or without a submit?)