Outdated workflow's config

We have couple custom configuration, however once we update the workflow, it will become Outdated. it is really annoying.

is that any way to make it back to custom, I dont want to delete and make a change.

how Teamsite determine the configure is outdated ?

Find more posts tagged with

Comments

Adam Stoller

We have couple custom configuration, however once we update the workflow, it will become Outdated. it is really annoying.

is that any way to make it back to custom, I dont want to delete and make a change.

how Teamsite determine the configure is outdated ?

You have two different versions of TS listed in your signature - which version are you talking about?

I assume it is 671 and you are talking about WFM - though it would be nice if you would make that clear one way or the other.

Beyond that - please provide more detail about what exactly you are trying to do and how you are trying to do it.

cc96ai

TS 6.7.1 WFM

we have couple configurable variable in workflow, and do custom configure on different branch, everything look fine.

if we go WFM, make a slightly change and publish to Teamsite, the configured branch will become "outdated" which is normal, beacuse we did update the change.

if we want to get rid of the "outdated", we have to delete the "outdated" and reconfigure for each branch.

rather than that way, do we have other method ? like command line to tell TS that is updated version/ run script/ edit RAW config file/ etc...?

Faizi

Each time whenever you re-publish the workflow the custom config becomes outdated.
If there is no change occurred in configurable variable or no new configurable variable added then no need to change custom config.

In this case you can use this option "Use Outdated Configuration" from Action. Now old custom config is activated. So, you do not need to change values.