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

Not able to submit files through workflow

shr

Hi,

whenever i'm instantiating a workflow , it gives me the following error: (Role is author)
Invalild workflow: Job 278049 does not exist
ERROR: 02439: Operation not permitted
ERROR: User ead557 cannot subit files in workarea /defaut/main/du.com/v3/Corporate/US/Dark_Site/en_US/WORKAREA/Dark_Site in task "Submit changes".

we're using out of the box workflow - there is no log file
-------------------
In the available_templates.cfg -
<!-- role value="author" include="no" allusers="yes"/>
<role value="all" include="yes" allusers="yes"/>
--------------------------------------------
Can someone tell me why that's happening?

Thanks

Edited by shr on 08/01/05 10:43 AM (server time).

Find more posts tagged with

Comments

Adam Stoller

This sounds like a classic mistake where you've managed to make an Author-only user the owner of a workarea and are attempting to use a workflow the assumes the workarea-owner has the ability to login with the role Editor or higher (and thus able to submit to the staging area).

Your potential fixes are:
- change the owner of the workarea to a "power user" and share the workarea with a group that contains the intended Author
- "promote" the Author to be able to login as Editor (may violate licensing though)
- modify the workflow to hard-code the owner of the submittask to someone who (a) has the ability to submit to staging, and (b) the ability to write within that workarea.

There may be a couple of other alternatives - but those are the ones that come to mind first.

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

shr

ok..understood what you're trying to say. Thanks for the prompt reply.

prem_pratick

Hi All,

We are facing a similar issue, When a user submits the DCR he gets the below error

[Wed Jul 09 11:06:54 2008] User bp1\callagkc cannot modify files in workarea \default\main\intranet\bpworld\admin\WORKAREA\WorkInProgress in task 899.
[Wed Jul 09 11:06:54 2008] Invalid workflow.

But,
The user is login using -adm-pratp2 and not by callagkc.

The user is having master role. We have recently installed TS6.7.1 on our old CMS Box and use AD for user/group validation. We are using the old store only.

In our Production Box, the same User is able to submit the files using the same WF and there is no difference between our STG and Prod .wft files/roles and all.

TS 6.7.1 SP1, Windows 2003.

Thanks
Prem Pratick.

Adam Stoller

Hi All,

We are facing a similar issue, When a user submits the DCR he gets the below error

[Wed Jul 09 11:06:54 2008] User bp1\callagkc cannot modify files in workarea \default\main\intranet\bpworld\admin\WORKAREA\WorkInProgress in task 899.
[Wed Jul 09 11:06:54 2008] Invalid workflow.

But,
The user is login using -adm-pratp2 and not by callagkc.

The user is having master role. We have recently installed TS6.7.1 on our old CMS Box and use AD for user/group validation. We are using the old store only.

In our Production Box, the same User is able to submit the files using the same WF and there is no difference between our STG and Prod .wft files/roles and all.

TS 6.7.1 SP1, Windows 2003.

Thanks
Prem Pratick.

There probably is a difference - you just haven't uncovered it yet.

If you examine the specification that the instantiated WFT creates - you should be able to find the reference to the user which is causing issues - if you cannot find it in that output, verify membership of any groups used in group task sharedby elements.

dynamic_table1.rptdesign

prem_pratick

Hi Ghoti,

Pls find the attached file.

Our STG(TS 6.7.1) and Prod 6.1 uses the same AD. So roles and permission should be the same.

Thanks
Prem Pratick.

Adam Stoller

Hi Ghoti,

Pls find the attached file.

Our STG(TS 6.7.1) and Prod 6.1 uses the same AD. So roles and permission should be the same.

Thanks
Prem Pratick.

You have three grouptasks shared by[html] [/html]is bp1\callagkc a member of that group?
If so - you either need to ensure that user has access to the branch / workarea - remove that user from the group - or create a new group without that user and change the workflow to use that new group.

nipper

You have three grouptasks shared by[html] [/html]is bp1\callagkc a member of that group?
If so - you either need to ensure that user has access to the branch / workarea - remove that user from the group - or create a new group without that user and change the workflow to use that new group.

You can also try making the task readonly. If it is an approval task only, that may not be a big issue.

before.jpg

Adam Stoller

You can also try making the task readonly. If it is an approval task only, that may not be a big issue.

As long as the user has read-access to the branch / workarea - that would probably work, otherwise I think you would run into the same problem.

prem_pratick

Hi,

I have found out the issue, WF was fine, it was basically related to the user access.

We did a fresh Install on TS6.7.1 SP1 on out old/STG CMS BOX. We did usermigrate and access migrate as recommended by IW.

But we noticed that if a user say USER-A had access to a particular branch before Upgrade, now he does not have any access to that branch. He cannot edit/save/submit the files in that branch.

We removed all the users{Except the master role from}
tsusers.xml
Then we tried to use the workflow, and the same was working fine now.

But the question is still there, how does the access gets lost after upgrade/fresh install of TS6.7.1 as we are using the same AD/Same Box/Same Store.

I have attached a screen shot the shows that now the user does not have access to any branch.

Any help on this would be great.

Thanks
Prem Pratick.