Workflow E-mail Notifications

CM1 Bugs
1

We’re getting ready to set up course catalog workflows in Percussion, and we need e-mail notifications sent to a specific user in each of the three steps.

Ideally, this is how we’d like for it to work:

Contributor -> Approver (specific user gets e-mail) -> Reviewer (specific user gets e-mail) -> Admin (specific user gets e-mail)

If it’s rejected, of course, that user would get an e-mail, and so on and so forth.

The problem is: when we set this structure up in the workflows, e-mails aren’t sent. We know this isn’t an e-mail setup issue, because it does work upon rejecting. They don’t, however, trigger when passing through the steps. We’ve also given the approver and reviewer the required Editor roles to receive e-mails as per the workflow documentation.

Attached are screenshots of our setups. Please let us know how we can get these working correctly.

2

Hi Matt,
That’s strange that the emails are getting sent only when pages are rejected, is this only happening with the “Workflow Test 2” workflow, or the default workflow as well?
-Jon

3

Just Workflow Test 2. That’s the layout we’re going to use. There’s actually going to be dozens of Workflows like it when it’s all said and done.

I’ll try the default workflow, though, and see if e-mails work there.

4

Confirmed that this is also happening with the default workflow, which I’ve set up to match Workflow Test 2. Except with this one, I’m not getting any e-mails.

5

Hi Matt,

Can you confirm that the notification does get triggered when you either Submit a page from Draft into the Review state, or reject a page from Approved back into the Review state? If so, this sounds like you may be experiencing a known bug that affects notifications for the Draft and Approved workflow states. We are tentatively targeting a fix for this issue in our next major release, slated for later this month.

6

Nathaniel,

Sure. Is that something I can see in a log file somewhere?

7

This is an e-mail I got letting me know I had the wrong address in an e-mail field, which nonetheless confirms they are triggering:

Delivery has failed to these recipients or groups:   
 
mr.renfer@gardner-webb.edu   
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.   
 
Diagnostic information for administrators:   
 
Generating server: gardner-webb.edu   
 
mr.renfer@gardner-webb.edu   
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##rfc822;mr.renfer@gardner-webb.edu   
 
Original message headers:   
 
Received: from mail82-co9-R.bigfish.com (207.46.163.23) by   
CH1PRD0102HT021.prod.exchangelabs.com (10.42.118.205) with Microsoft SMTP   
Server (TLS) id 14.15.129.3; Mon, 4 Mar 2013 15:28:45 +0000   
Received: from mail82-co9 (localhost [127.0.0.1]) by mail82-co9-R.bigfish.com   
(Postfix) with ESMTP id 2FFA31400A0 for <mr.renfer>; Mon,
4 <br>
Mar 2013 15:28:45 +0000 (UTC) <br> X-Forefront-Antispam-Report: CIP:152.44.159.162;KIP:152.44.159.162;UIP:(null);(null);H:pm.gardner-webb.edu;R:internal;EFV:INT <br> X-Safelisted-IP: 152.44.159.162 <br> X-FOPE-CONNECTOR: Id$4217%Dn$GARDNER-WEBB.EDU%PF$0%SF$0%RO$0% <br> Received: from mail82-co9 (localhost.localdomain [127.0.0.1]) by mail82-co9 <br>
(MessageSwitch) id 1362410923706280_13674; Mon,
4 Mar 2013 15:28:43 +0000 <br>
(UTC) <br> Received: from CO9EHSMHS007.bigfish.com (unknown [10.236.132.236]) by <br>
mail82-co9.bigfish.com (Postfix) with ESMTP id AA4C34A00CF for <br>
<mr.renfer>; Mon,
4 Mar 2013 15:28:43 +0000 (UTC) <br> Received: from pm.gardner-webb.edu (152.44.159.162) by <br>
CO9EHSMHS007.bigfish.com (10.236.130.17) with Microsoft SMTP Server id <br>
14.1.225.23; Mon, 4 Mar 2013 15:28:41 +0000 <br> Received: from pm.gardner-webb.edu (localhost [127.0.0.1]) by localhost <br>
(Postfix) with SMTP id 93BF15C8076 for <mr.renfer>; Mon,
4 <br>
Mar 2013 10:28:39 -0500 (EST) <br> Received: from u16312282 (u16312282.onlinehome-server.com [74.208.109.200]) by <br>
pm.gardner-webb.edu (Postfix) with ESMTP id 1DC345C80D4 for <br>
<mr.renfer>; Mon,
4 Mar 2013 10:20:32 -0500 (EST) <br> Date: Mon, 4 Mar 2013 10:22:48 -0500 <br> From: <mrenfer> <br> To: <mr.renfer> <br> Message-ID: &lt;22981003.191362410568921.JavaMail.webmaster@u16312282&gt; <br> Subject: Content is awaiting your approval <br> MIME-Version: 1.0 <br> Content-Type: text/plain; charset="us-ascii" <br> Content-Transfer-Encoding: 7bit <br> X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.3.4.151215 <br> X-PMX-SPAM: Gauge=IIIIIIII, Probability=8%, Report=' <br>
HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_300_399 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, FROM_EDU_TLD 0, INVALID_MSGID_NO_FQDN 0, NO_REAL_NAME 0, __ANY_URI 0,__ CP_URI_IN_BODY 0, __CT 0,__ CTE 0, __CT_TEXT_PLAIN 0,__ HAS_FROM 0, __HAS_MSGID 0,__ MIME_TEXT_ONLY 0, __MIME_VERSION 0,__ PHISH_SPEAR_STRUCTURE_1 0, __SANE_MSGID 0,__ SUBJ_ALPHA_END 0, __TO_MALFORMED_2 0,__ TO_NO_NAME 0, __URI_NO_MAILTO 0,__ URI_NS ' <br> Return-Path: mrenfer@gardner-webb.edu <br> Reporting-MTA: dns;gardner-webb.edu <br> Received-From-MTA: dns;mail82-co9-R.bigfish.com <br> Arrival-Date: Mon, 4 Mar 2013 15:28:45 +0000 <br><br> Original-Recipient: rfc822;mr.renfer@gardner-webb.edu <br> Final-Recipient: rfc822;mr.renfer@gardner-webb.edu <br> Action: failed <br> Status: 5.1.1 <br> Diagnostic-Code: smtp;550 5.1.1 RESOLVER.ADR.RecipNotFound; not found <br><br> From: <mrenfer> <br> Date: March 4, 2013 10:22:48 AM EST <br> To: <mr.renfer> <br> Subject: Content is awaiting your approval <br><br> Please click the following link to view content that is awaiting your approval: <br><br> http://webwork.gardner-webb.edu:9992/cm/app/?id=1-101-19633&amp;site=www.gardner-webb.edu&amp;name=index&amp;path=/Sites/www.gardner-webb.edu/academics/academic-publications/2013-2014-undergraduate-catalog/catalog-index/index&amp;view=editor&amp;pathType=page&amp;mode=readonly <br>

</mr.renfer></mr.renfer></mr.renfer></mr.renfer></mr.renfer></mr.renfer>

8

To confirm, this is only triggering for items put into the Review state, correct?

9

I think so. Then again, it seems most do come through, though I can’t pinpoint why some and not others. I did get 100+ e-mails today when we tested the workflows, so that is definitely a good sign.

Let’s hold off on this for now, though. We have a Catalog Training for users tomorrow, but won’t necessarily need e-mails for it. After the training, we’ll continue narrowing down why some aren’t being sent.

10

Sounds good, Matt. Keep me posted.

11

I want to confirm that reject workflow e-mails are working properly.

My main concern is submit and approve e-mails. Let me clarify what we’re looking to accomplish.

We have multiple steps for our workflows. For example, most workflows are structure in this way:

Contributor -> Approver -> Reviewer

What we’re looking for is an e-mail sent to the Approver once the Contributor submits their changes. Is this possible?

Likewise, once the Approver approves their step, we’d like for the Reviewer to receive an e-mail. Is this possible?

Both the Approver and Reviewer roles are specifically set to a single person. By doing it this way, will we be narrowing down the e-mail to that person only?

The reason I ask this is because these particular steps seem to be hit or miss when it comes to e-mails. Sometimes they work, sometimes they don’t. Not really sure why.

12

Matthew,

Your first objective here, of having an email notification triggered when a content contributor Submits a page from Draft to Review, is fully functional and very common. Have you had any trouble with this particular workflow transition not triggering an email? If so, we can take a closer look into your workflow setup.

Beyond that, however, we are currently working on a bug where transition notifications are not being created in the system for any other type of transition besides this one and – as far as we can tell – Resubmitting a page from Archive to Draft. We are targeting a fix to address this issue in our next major release.