Hi There,
Is it possible to have a default value for the future status options for an asset. The idea is that someone can create a new asset using the Simple Edit Interface, however by default the asset they create shall be placed up for review in 6 months…
Thanks,A
[quote]Is it possible to have a default value for the future status options for an asset. The idea is that someone can create a new asset using the Simple Edit Interface, however by default the asset they create shall be placed up for review in 6 months…
[right][post=“16212”]<{POST_SNAPBACK}>[/post][/right][/quote]
Yes, using Triggers. If you use the “Status Changed” event (with a Criteria of “Live”, so it looks for changes to the Live status), you can then use the Set Future Status to add an “Up for review” change in X months/weeks/days. You should also use the Delete Future Status action to remove any other Up for Review changes first.
This requires v3.12 of Matrix or higher.
I've been playing with the 'Up For Review' state. I thought when the 'Up For Review' state was entered a workflow email notification was sent to users in the first workflow step?
I have an asset with a two step workflow applied. As the root user I manually placed the page up for review but the user in the first workflow step didn't receive an email? Does this email notification have to be setup separately with a trigger?
And also regarding workflow email notifications - is there any way to customise them to include workflow coments? Or again would this have to be done with a trigger?
Thanks 
Sarah
That is correct. Workflow starts like normal and all users in the first step are notified. Do you get notifications when you go from Under Construction to Apply For Approval?
[quote]And also regarding workflow email notifications - is there any way to customise them to include workflow coments? Or again would this have to be done with a trigger?[/quote]
There is no way to email the workflow comments at the moment.
[quote]That is correct. Workflow starts like normal and all users in the first step are notified. Do you get notifications when you go from Under Construction to Apply For Approval?
[right][post=“16275”]<{POST_SNAPBACK}>[/post][/right][/quote]
Yes the user in the first step does receive notification for Under Construction > Apply For Aproval
but not for Live > Up for Review
I invoked both theses status changes as a sys admin user completely independent of the workflow.
Any ideas why I wouldn’t be getting the email when entering up for review?
The only thing I can think of is that your internal message settings are too specific.
Go to System Configuration > Messaging Service Configuration (from the drop-down)
In the Log To Email White List, add asset.workflow.*
This will probably send a lot more emails than normal, but at least you can see if you are getting the messages that you should be. We can then try and make that setting more specific for you.
[quote]The only thing I can think of is that your internal message settings are too specific.
Go to System Configuration > Messaging Service Configuration (from the drop-down)
In the Log To Email White List, add asset.workflow.
This will probably send a lot more emails than normal, but at least you can see if you are getting the messages that you should be. We can then try and make that setting more specific for you.[/quote]
Is there a list of keywords that can be used in the Messaging Service COngif lists, ie: asset.workflow. etc…
Thanks,
A
The defaults you see there are all of them. You can just get more or less specific, but those more specific settings are not documented as far as I know.
The message types are visible in the sq_internal_msg or in the system.log file.
Sorry took a while to get back to this… I've added asset.workflow.* and I am getting notification that the up for review process has started (yay!) but I am getting more emails than I would like. My message types are:
asset.locking.forced
config.
hipo.
inbox.
asset.status.notify
asset.workflow.invitation
asset.workflow.announce
asset.workflow.invitation.
asset.workflow.announce.
asset.workflow.stale
cron.deadlock
asset.workflow.
My workflow has 2 steps - Author and Approve - both of which have 'Notify When Live' selected.
Invoking up for review BOTH the author and approver get an email 'Asset Up for Review' - is it possible to customise my email messages so that only the author (first step of the approval process) receives this?
My author then approves the review and 4 emails are received:
Author - Asset Changes Approved (don't need)
Approver - Workflow User Log (don't need), Workflow Approval Required (want to keep), Asset Changes Approved (don't need).
Approver approves and makes the page live and then receives 2 emails - Review Complete (OK) and Asset Changes Approved (don't need).
Neither the author or the approver get an Asset Made Live email - with the Up for Review proccess or when workflow is manually invoked - any idea why?
Thanks,
Sarah
A list of all the codes that are available for the Messaging Service screen can be found in the MySource Matrix System Administrator manual.
Great thanks I now have the following message types for workflow which has gotten rid of the unwanted emails:
asset.status.notify
asset.workflow.invitation
asset.workflow.stale
asset.workflow.review
asset.workflow.announce.reject
Still not getting any email notification when the page is made live to either the author or approver - that should be covered by asset.status.notify shouldn't it?
Also I've set this trigger up but it sends 2 emails when the asset changes to 'Up For Review' - one for the page and one for the div. Any ideas on how to get it to only send the one email for the page?
Interesting. The messaging system is supposed to try and batch those together. Can you log this as a bug so the developers can investigate?
Will do thanks
Also when a page is rejected the 'Asset Changes Rejected' email is sent to the user that actioned the 'Reject Changes'. Shouldn't it be sent to the user who applied for approval?
The system only batches those mails if it does them in one big request. That means you either need to not see a HIPO at all, or be running the Squiz Server. To not see a HIPO, increase the thresholds on the HIPO Configuration screen (in System Configuration) so that Matrix can do, for example, 10 assets at a time.
That is just the way it works.
How does this work with the Cron Manager? I assume it wouldn't trigger a HIPO job (i.e. it would always freestyle), so it would need to be under the freestyle threshold, yes?
Yep.