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

Submit conflict

Dmitry

We are running into a problem with our workflow:

We have a workaround the place where an "editor" level workarea-owner is the owner of the submit task so that authors can submit content using the workflow.

However this causes a conflict with imported files, since they are locked by the original author, so when the submit task (owned by someone else) tries to take control, it causes a problem.

Is this a bad workaround for authors not being able to submit? Can anyone think of a different way?

Or if we do keep this workaround, I was thinking of unlocking all the files using an external task, or using override option with our submit, but I am not sure if there are any downsides to this.. please advise.

Thanks!
Dmitry

Find more posts tagged with

Comments

nipper

relock the files in the workflow. I usually lock them to Admin or root so that no user can unlock them

Dmitry

Awesome I think that worked - thank you!

nipper

Awesome I think that worked - thank you!

Don't act so surprised. Even a blind archer hits the target once in a while. Smiley Wink

gzevin

relock the files in the workflow. I usually lock them to Admin or root so that no user can unlock them

so, what if an approver wants to edit files?

we usually run external unlock tasks....but I think that 'targeted' locking will work better...however if you have a group approval task .. what do you do?....

nipper

so, what if an approver wants to edit files?

They should learn to be disappointed. Smiley Wink

I dislike the approver making changes. But you can do locking at the task level. I am trying to make certain that the author does not back changes during the workflow. Esp when I had a delay since we did not want the content out until a certain date, people were trying to sneak changes in.

me

gzevin

Esp when I had a delay since we did not want the content out until a certain date, people were trying to sneak changes in.

me

well, this could be tackled on different levels.

with one of my clients I reccomended that they cease area compairison deployments, and do filelists only. Thus we could use delayed deployments from staging, without the fear of getting some assets too early.