Workflow not working properly for Editors Role

I am using "author submit workflow" that comes with Teamsite 6 and I am having problem with the review process when I log in as an editor. It works absolutely fine when I login as a master and I can do everything (approve, reject and submit). On the othe hand as an editor it does not allow me to approve or reject job in the workflow and it shows me at the top that I only have read access to this page.
This is what I have done so far:
I have added Editors Role as well as Master role in the available_templates.cfg file as you can see below:

<template_file active="yes" name='Author Submit' path='web/iwauthorsubmit.wft'>
<command_list>
<command value='submit' />
<command value='all' include='no' />
</command_list>
<role_list>
<role value="master" include="yes" allusers="yes"/>
<role value="editor" include="yes" allusers="yes"/>
</role_list>
</template_file>

I have also removed the file locks but it still doesn't work.
Is there anything else I need to add apart from this. It's urgent please let me know

Find more posts tagged with

Comments

Adam Stoller

The available_templates.cfg file controls only in what circumstances which users can *initiate* an instance of a particular job - not who has access to any of the tasks within the job.

The access controls for the task are handled via the wft itself and via the OS and TeamSite in terms of whether or not the user who has managed to be assigned (or take ownership) of a given task has access to the areavpath associated with that task.

In your case - if you log in as an editor and it does not allow you to approve or reject a task in a workflow - check to see if the user you are logged in as has the appropriate access rights for the areavpath associated with the task.

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

Migrateduser

I have verified that I do have access rights for that areavpath associated with the task as suggested by you but it still it doesn't work. Then I have also tried adding a role file and specifying its location in a string like for example
my $wfuserfile=" "$iwhome\\config\\roles\\editors.uid";

Strange thing is when I tried to run one of the TeamSite configurable workflow and log in as an editor the review process works fine. And everything is visible to me (Reject and Approve). So I am assuming may me I am missing something in the workflow. I have attached my workflow with this email.

Any help will be appreciated.
Thanks in advance
Surnu

Edited by surnu55 on 01/03/05 04:49 PM (server time).

Adam Stoller

Which task are you referring to - where, as an Editor, you only have read-only access to the task? "Approver" or "EditorWork"?
Is the Editor the person who initiated the workflow, or is the Editor the owner of the workarea in which the job was initiated?

Also, the line that reads: __INSERT__(" <file path='"/HR/html/index.htm ' " . "comment='testing'/>");looks wrong (for the highlighted reason and because you have an extra space at the end of the path [after the .htm] before the end-single-quote)

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

Migrateduser

To answer your Questions:
First, I am referencing to the "Approver" task which has read-only access for Editors. Although I have tried putting
readonly="f" for this task but didn't help.?
Second, Editor is the person who has initiated the workflow but also has rights to make changes in that workarea.

Thanks forthe quick catch, I have corrected that already...

Adam Stoller

The Approver task is defined as: <usertask name="Approver"
owner="__TAG__('iw_areaowner');"
description="Content Approval"
readonly="f">
<areavpath v="__TAG__('iw_workarea');"/>
...
</usertask>which means that only the user who is defined as the owner of the workarea (iw_workarea) should be able to manipulate the task and the files attached to this task. Masters tend to be provided administrative access to such tasks and so are not restricted. I'm guessing that the Editor you logged in with and initiated the job with is not the owner of the workarea (though they may be in the group-for-sharing).

Can you verify whether this is (or is not) the case?

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