nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Trouble with workflows after upgrading to 6.5

ttriemst

I was hoping that someone would be able to help me with something. I am currently in the process of upgrading TeamSite from 5.5.2 to 6.5.0, and I am not able to get my Workflows working. I basically copied the available_templates.cfg and templating.cfg to the newer version. When I make a change to a DCR (or create a new one), I doesn't prompt me for a new job or anything. It just returns back to the TeamSite GUI. I have checked my log files, read the manuals, and can't get it to work. Would anyone have suggestions or if there is anything else that I have to do?

Thanks much.

Find more posts tagged with

Comments

Adam Stoller

Please post (as an attachment) your available_templates.cfg
Which UI are you using - CCPro or CCStd?
Is the only issue you have (right now) with regard to initiating workflows after Edit DCR sessions?
Are you sure that the DCR in question is not already associated with an existing job?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

nipper

Do any WFs work ?

How about a new DCR ?

Is the DCR you are editing part of a WF already ?

TS Trivia - if you edit a DCR that is already in a WF and save it will not ask you to submit it.

It makes sense, however there is no indication of why.

Andy

ttriemst

Attached is my available_templates.cfg. I am using CCPro, and currently it is the only problem that I am aware of. I have verfied that the DCR I am trying to modify is not associated with an existing job. I try to create a new DCR, and it does not bring up the "New Job" window.

Edited by ttriemst on 04/18/05 09:41 AM (server time).

ttriemst

sorry, forgot to attach file

ttriemst

I have not been able to get any WF's working. I have tried creating a new DCR, and it does not bring up the option for a new job. I have tried to modify both a new DCR and an existing DCR. I have also confirmed that the file is not currently in an existing job.

Adam Stoller

It should only prompt you to start a new job after you've saved *and* closed the Edit DCR window (which is probably now "saved & finished")
You still didn't manage to attach your available_templates.cfg file.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

ttriemst

sorry, lets try this again.

nipper

Can you simplify it, remove the user list to test ? Also remove the branch list ? Since we do not know your
logins or your branch, we cannot tell if they are accurate.

Which one are you trying to run anyway ?

Adam Stoller

What platform is your TS server? I assume Unix - because if it's Windows - all the userid entries in the availbale_templates.cfg file are wrong (they don't having DOMAIN\ preceding them).

I second Nipper's comments - simplify the config file while you're trying to debug the problem - by removing the constraints around the one workflow you want to see get kicked off.

Also - when you do have constraints - simpify your xml - i.e. instead of:

...
<command_list>
  <command value="tt_data">
  </command>
  <command include="yes" value="all">
  </command>
</command_list>
<branch_list>
  <branch include="yes" value="gfs_extranet">
  </branch>
</branch_list>
<user_list>
  <user include="yes" value="tjacobs">
  </user>
  <user include="yes" value="ttriemst">
  </user>
</user_list>
...

Try

...
<command_list>
  <command value="tt_data"/>
  <command include="yes" value="all"/>
</command_list>
<branch_list>
  <branch include="yes" value="gfs_extranet"/>
</branch_list>
<user_list>
  <user include="yes" value="tjacobs"/>
  <user include="yes" value="ttriemst"/>
</user_list>
...

It's much easier to read and simpler to maintain that way.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

ttriemst

Ahhhh....that was the problem. I removed the branch and everything works great. I am working on getting 6.5.0 setup in a test environment and didn't realize that I had created a different branch name. Thanks for your help.