UA Node Question

 10 Replies
 2 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Srini Rao
Veteran Member Send Private Message
Posts: 149
Veteran Member

 

I created a CER approval process, as part of the set up I created a TASK called ”CerBuyer” and group of buyer assigned to the task.   When new req goes to CerBuyer’s Inbasket flow is sending an email to every buyer defined in task. (I’m using the UA). Instead of every buyer receiving the email, they like me to send it to generic email and buyers will work on the queue.  How do I do it?


 

 

David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
You'd have to send an email to the Buyer group address before hitting the UserAction and turn off 'Notify all users of work' flag within the Inbasket.
David Williams
Srini Rao
Veteran Member Send Private Message
Posts: 149
Veteran Member
If I uncheck "Notify all user of work" it will allow me to send any emails. But I do wanted to send it to common email box not to individual buyers.

Woozy
Veteran Member Send Private Message
Posts: 709
Veteran Member
Hi Srini Rao,

You need to add a separate email node just prior to the UA node, and use that email node to send the notification email. Then you uncheck the "Notify all users of work" checkbox in the UA so it doesn't send email. By doing this, you have complete control over how the initial email notification is built and who it is sent to.

We almost never use the UA to send the initial notification because it introduces limitations we don't like.
Kelly Meade
J. R. Simplot Company
Boise, ID
Woozy
Veteran Member Send Private Message
Posts: 709
Veteran Member
By the way, when I have a "common" email address I use for flows, I generally add a configuration variable in PfiConfiguration to hold the email address and then reference that variable in my email node. That makes it much easier to update that email address if needed. Using this approach you could also just use a comma-delim list of email addresses in the variable rather than using a distribution list - but then someone has to remember to maintain the list.
Kelly Meade
J. R. Simplot Company
Boise, ID
Srini Rao
Veteran Member Send Private Message
Posts: 149
Veteran Member
Woozy - I liked the idea of using the different email node. I will try it.

Can we still use email approval? When we use UA, users gets the option to approve the req's. (Bottom option, Allow actions via email )




Woozy
Veteran Member Send Private Message
Posts: 709
Veteran Member
Unfortunately, you would lose the ability to do email approvals.

We don't use that feature for security reasons, so I didn't even think about that. I suppose maybe you could figure out how they built the link and add it to your own email - I imagine the UA node just adds additional HTML to the email to make the buttons. It probably isn't very complicated - but I haven't played with it so I'm not sure. Sorry!
Kelly Meade
J. R. Simplot Company
Boise, ID
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
You can build the Dispatch Call into your email as an HTML link (see the IPA Admin Guide for the syntax) however you can't duplicate the function of bypassing the login option. To Woozy's point about the security concerns of using Infor's email approval feature, you can set the UserAction to require the user to login to execute the Dispatch Call when they click the Approve or Reject links from the email.
David Williams
Srini Rao
Veteran Member Send Private Message
Posts: 149
Veteran Member
I agree with Kelly , Security and Audit point view it's advised.

I built the email node before the UA and it's working. I'm using UA for first and second remainders.

Other question, Im using the time out function on UA to move the Req to next level. Means if user does not perform any action in 48 hours it does to next level. Is it possible to exclude the weekends? Mean stop the clock the on Friday 8 PM and start it on Monday 8 AM :-)


David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
You can't 'stop the clock' but you can use a variable for your escalation/time out and use a JavaScript expression to determine the day of the week and add 2 days to your escalation variable value so weekends are skipped.
David Williams
Srini Rao
Veteran Member Send Private Message
Posts: 149
Veteran Member
Thanks David