Currently running 3.18.8 without a problem for 6 months, in the process of installing workflow in production. Which we have had in dev system for 3+ months.
Set up users groups etc no issues
Applied workflows to almost every page, again no issues
Set triggers across whole site last night to:
Set status to live once status is “approved to go live” as per dev system
Release all locks when user logs out (as per manual)
This morning
In admin view do not have full access to any asset that had workflow applied (as root, admin, backend user with edit or admin rights)
However, can edit any asset with workflow via simple edit interface once and once and then this nasty error message:
and there is no hippo job being run by root.
Removing workflow from an asset does not fix it.
Tried reapplying triggers to individual assets again no effect.
Any ideas?
I already fire off request to support, but looking for help as this is supposed to go live next Monday
[quote]This morning
In admin view do not have full access to any asset that had workflow applied (as root, admin, backend user with edit or admin rights)[/quote]
Once Workflow has been applied to any asset, the only way you can edit a Live asset is to change its Status to Safe Edit. This is for everyone including the root user.
I did not make myself clear, nobody (root, sysadmin, backend user) has permission to change the status from live to safe edit, except for the one time special offer using simple edit.
[quote]Currently running 3.18.8 without a problem for 6 months, in the process of installing workflow in production. Which we have had in dev system for 3+ months.
Set up users groups etc no issues
Applied workflows to almost every page, again no issues
Set triggers across whole site last night to:
Set status to live once status is "approved to go live" as per dev system
Release all locks when user logs out (as per manual)
This morning
In admin view do not have full access to any asset that had workflow applied (as root, admin, backend user with edit or admin rights)
However, can edit any asset with workflow via simple edit interface once and once and then this nasty error message:
and there is no hippo job being run by root.
Removing workflow from an asset does not fix it.
Tried reapplying triggers to individual assets again no effect.
Any ideas?
I already fire off request to support, but looking for help as this is supposed to go live next Monday[/quote]
Thanks for the information Nickobec for we are going for workflow again shortly. According to my last-time experience the workflow has the higher privilege than sys admin. The system keeps locking the assets until the workflow is finished, even the sys admin cannot help unlock.
So I am going to include myself to every group involved in the workflow just in case someone forgets to let it flow…
Bad trigger design was causing the issue. Do not put trigger to fire both After Asset Approval and Status Change. Just use Status Change.
and compounded by me (and colleague) forgetting how workflow works on admin screen. You can not acquire lock in details screen without going to workflow screen and acquiring lock and changing status.
Bad trigger design was causing the issue. Do not put trigger to fire both After Asset Approval and Status Change. Just use Status Change.
and compounded by me (and colleague) forgetting how workflow works on admin screen. You can not acquire lock in details screen without going to workflow screen and acquiring lock and changing status.[/quote]
You can make the front end edit experience a bit nicer with ignore_frames=1 in your url when you fire the /_edit too. It used to be hide_frames=1 in versions before 3.18 and then changed at 3.18. I just had to change 40 parse files in a system. If you have a lot of users editing it will help to lower the load too.
Robin I think that is overkill and unnecessary. You should:
1. Think about using escalation if you are worried about someone forgetting/ignoring requests
2. Make sure your groups are large enough so if somebody forgets/ignores/is on holidays that somebody else can do it
Otherwise you are likely to drown in email if your site is a decent size.
As a sysadmin and need to make a change and the asset is in workflow and there is a problem, you can always add your self to that group or role on a temporary basis and if the asset is not in workflow, the take workflow off that asset, do the changes and put workflow back on.
As there is interest I will try to keep you informed in our adventures in workflow and probably most importantly how our authors and approvers handle it.
today's episode was a bad trigger stopping an asset from being accessed once a status change was made, workflow was the reason the trigger was added and in workflow just caused major confusion for staff not familar with it in the backend trying to resolve the issue.
Changing status does not require any locks, which is why the drop-down is always available even if you don't have locks. So yes, you can/should be able to change the status of an asset with workflow applied without locking. Once workflow is running, you can't change the status without going to the workflow screen.
[quote]Robin I think that is overkill and unnecessary. You should:
Think about using escalation if you are worried about someone forgetting/ignoring requests
Make sure your groups are large enough so if somebody forgets/ignores/is on holidays that somebody else can do it
Otherwise you are likely to drown in email if your site is a decent size.
As a sysadmin and need to make a change and the asset is in workflow and there is a problem, you can always add your self to that group or role on a temporary basis and if the asset is not in workflow, the take workflow off that asset, do the changes and put workflow back on.
As there is interest I will try to keep you informed in our adventures in workflow and probably most importantly how our authors and approvers handle it.
today's episode was a bad trigger stopping an asset from being accessed once a status change was made, workflow was the reason the trigger was added and in workflow just caused major confusion for staff not familar with it in the backend trying to resolve the issue.[/quote]
Since we started the discussion for workflow I think it'd be better to put my question here.
I notice that in the notification email sent from the workflow, all the links point to the admin interface instead of simple edit interface, is there a way to change that? I cannot find an option to modify the notification email content.
No option for this in 3.18 without editing the local on the server and messing up your SLA, way bad as there are two links that allow immediate approve and reject as well, but from 3.20 on you can edit the emails from within the workflow schema, which is way cool.
Good news, I am using 3.20.2 but cannot find it :(' /> <img src='http://forums.matrix.squiz.net/public/style_emoticons/<#EMO_DIR#>/sad.gif' class='bbc_emoticon' alt=':(
Ahhh, 3.20.3, functionality introduced between dot releases. A trap for young players, start upgrading:)
[quote]Customisable Workflow Emails
Introduced a new "Custom Messages" screen to the Workflow Step asset for entering a custom Workflow message body for a Workflow Step. The following workflow messages can be customised: invitation, approval, rejection, stale workflow, and escalation.[/quote]