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; } } }

A Very Strange Problem

blairm

I have a very strange problem and being a WF newbie, I hope someone can help me. I am running TS 5.5.2 on Solaris and have generated some very simple 3 step workflows to allow users (as authors) to submit files to the STAGING area. Then an external task is called to use OpenDeploy to move the files to our webserver docs directory. For 2 of the users, this works fine. For our 3rd user, the WF is never even kicked off (although available_templates.cfg looks fine). I have checked perms, the workflow files themselves, etc. and everything looks OK. I have even installed the whole thing on our QA machine, where it worked perfectly. Here is the available_templates file. The user is aau66r, the branch is SafetyForms, and the template file name is "Deploy Safety Forms".

Thanks in advance,

Blair Morton

Find more posts tagged with

Comments

Migrateduser

Perhaps you could also attach your wft file. Also, define "never kicked off". Does this imply you get some sort of feedback when you try to run the job, or does it allow you to run the job and you get no feedback? If it allows you to run the job and you get no feedback, check the ToDo list for All Users. It's possible that you have your workflow set up so that tasks are owned by someone other than the person running the workflow. If that's the case, the person who runs the job will not see any tasks in their ToDo list. Just a SWAG based on no other data to look at.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Edited by Smitty77 on 09/09/02 11:35 AM (server time).

blairm

Here is the .wft file. As for "never kicking", the workflow is going through the normal approval process and ending up in the user's "To Do" box rather than executing my workflow, which is self-approving.

Thanks,

Blair

Adam Stoller

Have you looked at the iwtrace.log and/or iwjoberrors.log?

Are all these users trying to initiate the workflow in the same workarea - or different workareas?

Is the owner of the workarea in which the job is being fired off an Editor or higher - or did you create a workarea owned by an Author (which would then cause the submittask to fail - which should be logged in one of the two above mentioned logs)?

--fish
(Interwoven, Curriculum Development)

Migrateduser

If the workflow is going through the normal approval process, then the user probably isn't executing the workflow that you think (SafetyForms.wft).
How is the user aau66r starting the workflow? With the Submit button? Is a menu of workflows being presented? If so, which one was selected?
What is the name of the task being displayed in the ToDo list?
Login to WebDesk Pro and locate the task. (Select View -> All Jobs if necessary.) Then select Job Options -> Job Admin. From the presented results, does this look like the correct workflow?

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

This is weird, because you claim that 2 different people have executed this same workflow successfully. I'm perplexed about this because you appear to have at least attempted to set up this workflow to be executed by one person and one person only. So how did the other users successfully execute this workflow? One thing I wonder about is your branch_list value is not fully defined, meaning you do not prefix the branch with "/default/...". Perhaps this is not necessary, but the example shown in the documentation fully defines the branch path, but the documentation doesn't say whether you need to or not. The documentation for available_templates.cfg stinks.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Adam Stoller

The value of the branch specified is used in a regular expression (/value/) so if you don't specify an anchor (^ or $) in the string it will match if the value appears *anywhere* within the actual branch-path.

Also - in case you were wondering - you can use '\', '\\', or '/' as path separators in the branch path specified in the available_templates.cfg file - they will all be translated to '/' (on both the pattern and the actual branch path being matched against) before the match is attempted.

--fish
(Interwoven, Curriculum Development)

Migrateduser

Geez, I would think that the value of the branch path being treated as a regular expression would be significant enough for the documentation to tell us that. It's irritating that a change this significant (old available_templates.cfg vs. new available_templates.cfg) is documented so poorly. There's no way anyone would think that this value was anything but a standard string based on the way it's documented.

This forum is really quite useful in learning things that are undocumented. The trick is asking the right questions that uncover the things you need to know. Thanks for letting us know about the regex for branch path.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Adam Stoller

I'll admit it doesn't seem well documented - but it is there - at least in the 5.5.2 Workflow Developers Guide at the bottom of p. 149.

I'll file a bug on the documentation for this.

--fish
(Interwoven, Curriculum Development)

Migrateduser

I stand corrected. I guess I expected it to be on page 105, where the branch_list element for available_templates.cfg is defined. Thanks for the reference.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

blairm

I tried fully qualifying the branch names, but the workflow still does not work. I even pulled the available_templates.cfg file over from our QA machine, where the workflow does work, but still no success. Are there WF config files that I don't know about? I have checked available_templates.cfg and SafetyForms.wfb.

Thanks,

Blair Morton

Migrateduser

It appears as if the template_file section isn't returning a "true" value for all of the qualifiers you're defined. One thing you might try is to start with the simplest form of a template_file section. Make it identical to how the Author Submit Workflow is defined, but use your wft and name it Deploy Safety Forms. Make sure at this point that you get an option of choosing the Author Submit or Deploy Safety Forms workflow when you click the Submit button. Now cancel out of this and start to modify the sections inside the template_file one at a time. In other words, first change the command_list section to your original command_list section, next time change to your original role_list section, and so on. After each modification, click the Submit button to see if the Deploy Safety Forms option still appears. If not, the section you just added isn't returning a "true" for the user you are logged in as. Once you discover which section is not working the way you expected, you can start to really debug why it's failing. This is kind of painstaking, but it will at least narrow your problem down a bit. Just an idea...

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Edited by Smitty77 on 09/10/02 01:45 PM (server time).

sajiddc

Have you applied the SP#2 by any chance?

sajiddc

Just asking. I am not asking you to apply SP#2.

blairm

I am on Solaris, so the only SP available is SP1. I have not applied it yet.

blairm

I think I've made some progress. I noticed that when you go to File -> New Job and try to assign an author to a workflow, our user (aau66r) does not show up in the workflow list of authors. I copied the author.uid file over from QA (where that
user does show up) and restarted TS. However, the user aau66r still doesn't show up in the list of authors.

I then did some searching and found the user definition in
$iw_home/local/entities/Data. I saw that our user had an iw_filesys_filter value of "myLocked", while all the other users had a iw_filesys_filter value of "all". I changed the value to "all" and restarted TS, but no luck. I'm now
thinking of removing aau66r from the /etc/passwd file and
$iw_home/local/entities/Data, restarting TS, adding the account again, and restarting TS. Has anyone ever done somethink like that, I'm kind of afraid of totally messing up TS?

Migrateduser

Be afraid. Be very afraid.

You should NOT edit any of the files in the entities directory unless you know exactly what you are doing. Even then, you shouldn't do it.

Try using the command iwckrole to see if a user is permitted to use a role, such as author. Then see if you can login as that user.

The iw_filesys_filter deals with the task filtering in WebDesk. If you are looking at task in WebDesk Pro it should have no effect.

Brinko Kobrin
Interwoven Staff Engineer

Migrateduser

Why did you copy the author.uid file over from another server instead of using the TeamSite Admin tool to set the role for aau66r? Set up the user through the Admin tool, reset TS and see if that works.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

blairm

I only copied the author.uid file over after resetting the role through the TS admin GUI failed.

Migrateduser

What do you mean it failed? Did you run iwckrole on the user after setting it up with the admin tool? Did you make sure you ran iwreset after changing the role?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com