iw_user and iw_areaowner

TS671, win 2003
[php]
owner="__TAG__('iw_areaowner');"
creator="__TAG__('iw_areaowner');"
description="__TAG__('iw_submit_comment');">

owner="__TAG__('iw_areaowner');"
description="Author Content Approval"
start="t"
readonly="t">

.....[/php]In this workflow, job is initiated by user, by submitting modified files. Then how come creator is iw_areaowner ? Is not the creator iw_user ?

Regards

Find more posts tagged with

Comments

Rick Poulin

In this workflow, job is initiated by user, by submitting modified files. Then how come creator is iw_areaowner ? Is not the creator iw_user ?

You'll have to ask whoever created this workflow. If you're looking at a sample, there's nothing preventing you from setting it to iw_user if that's what you want.

Adam Stoller

In this workflow, job is initiated by user, by submitting modified files. Then how come creator is iw_areaowner ? Is not the creator iw_user ?

Regards

The rationale for this is usually that Authors were unable to own the submittask and the jobowner was usually selected as the owner of that task; an areaowner should never be an Author - and therefore the workflow would work.

The other option would be to just make the owner of the submittask the areaowner and then you can have the owner of the job be the iw_user. Although you'd have to test the workflow out with someone who is [just] and Author to make sure there isn't some other task in the process that uses the job owner because it needed to be a non-Author....