Prev
Next
Forums Integration / Customization IPA/ProcessFlow

IPA User Actions - Sending emails from Main Config

 4 Replies
 2 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Preston Burdwell
Advanced Member
Posts: 33
Advanced Member
9/15/2016 3:53 PM

    I have been struggling with a problem that exists when I use the IPA User Action to send emails. I can send emails correctly if I use our system configuration name, but then my display exec: recsum.htm displays an error 404 (File not found) in the users Inbasket.

    If I use the main/default configuration name with User Action Node, the display exec works, but the emails fail with the following error: Notification failed with javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client. It must have something to do with the Main vs. System configuration and something we are missing. Anyone seen this before?? Thanks!

    Preston Burdwell Systems Analyst CHRISTUS St. Vincent Med CTR
    Tim Cochrane
    Veteran Member
    Posts: 154
    Veteran Member
    9/15/2016 6:24 PM
      Never seen that behavior...but I don't send emails from User Actions either...very few of us use the email feature within the UA.

      I would suggest moving your emails outside of the UA and into an actual email node...makes your life a little easier AND the email node offers more options (html, formatting, etc)
      Tim Cochrane - Principal LM/IPA Consultant
      Preston Burdwell
      Advanced Member
      Posts: 33
      Advanced Member
      9/15/2016 7:07 PM
        Thanks Tim. That is the way I designed it before. But, I was trying to use Lawson's new Buttons for Approval to be included within the email. Have you gotten those to work?
        Preston Burdwell Systems Analyst CHRISTUS St. Vincent Med CTR
        Thibaud Lopez Schneider
        Advanced Member
        Posts: 30
        Advanced Member
        9/16/2016 6:49 PM
          @Tim, the User Action email DOES allow HTML, and hence formatting too.

          @Preston, yes the buttons to take action in the email work correctly, provided you set the email address in the Actor. But the user/password is hard-coded in the URL (in encrypted form for privacy) so if you forward the email to someone else, and that someone else takes action, they would do so on your behalf, and the logs would show that you took action, which is incorrect and non-informed, that's accidental impersonation. Also, it's not possible to set a reason code / message (that's why I'm on LawsonGuru today, to ask that question). There are a few other drawbacks which I don't remember.
          Thibaud Lopez Schneider
          Advanced Member
          Posts: 30
          Advanced Member
          9/28/2016 9:51 PM
            @Tim, you are correct in that the UserAction activity node, email notification, is limited, for instance it does not allow adding attachments, whereas the email activity node does. But conversely, the email activity node does not allow adding buttons to take action via email (unless we create the buttons ourselves and deal with authentication).

            @Preston, regarding the accidental impersonation I mentioned, Jena Block responded by email to a question I asked at http://blogs.infor.com/te...ts-new/#comment-3012 . She said "from 10.1.1.43 and on, the accidental impersonation is fixed. You will, however, need to add a new configuration property in order for this to be allowed. The default behavior is that user authentication will be required when taking action from an email. If the authenticating user is not the same as the user that has been assigned the work, they will not be allowed to take action. If you want to allow users to take action on a forwarded email, you will need to add a system configuration property called “emailActionAllowEmailForwarding” and set it to true."