Template Order on Submit, changed after 6.7.1

Hello,

We just upgraded from TS 6.7.0 to 6.7.1. Everything went fine except for the following.

If a user has more that one available Workflow when clicking 'Submit', the order of the selections has changed.

Is there anyway to change the order of these selection values? I've also opened a case with Interwoven and they're researching.

Thanks for the help!

Sincerely,
~Chris

Find more posts tagged with

Comments

nipper

I wish I knew. I have noticed the same thing. It *appears* that pre 6.7.1 (mine is 6.5) that it is in the order int he available templates.cfg. I think in 6.7.1, my test server it is alphabetic order.

Bhargav Coca

I guess it alphabetic oredr no matter how you mention in your AT.cfg

ccprofessional

Hello,

We just upgraded from TS 6.7.0 to 6.7.1. Everything went fine except for the following.

If a user has more that one available Workflow when clicking 'Submit', the order of the selections has changed.

Is there anyway to change the order of these selection values? I've also opened a case with Interwoven and they're researching.

Thanks for the help!

Sincerely,
~Chris

I'm curious, why is the order important in your environment?

Adam Stoller

I'm curious, why is the order important in your environment?

As a guess - because I can see where this would make a difference - the first one listed tends to be pre-selected - so if you had a "default" workflow to use in most cases, you'd want that pre-selected and the other ones to come below it -- and not have them forced into alphabetical order.

Alphabetical order is a great thing if you can force default-selection or ensure no-default-selection so that users need to explicitly choose which one they want to use -- at which point it becomes a question of either user-training or reducing the number of workflows available to avoid confusion.

Adam Stoller

As a guess - because I can see where this would make a difference - the first one listed tends to be pre-selected - so if you had a "default" workflow to use in most cases, you'd want that pre-selected and the other ones to come below it -- and not have them forced into alphabetical order.

Alphabetical order is a great thing if you can force default-selection or ensure no-default-selection so that users need to explicitly choose which one they want to use -- at which point it becomes a question of either user-training or reducing the number of workflows available to avoid confusion.

Also, now that I think about it - this kind of change is one of those things that should be documented clearly in the release notes and - should allow for some means of backwards-compatibility if possible (just because the vendor *thinks* this is a better interface, doesn't necessarily make it so)