PM13383: EMAIL ACTION FAILS WITH IWKPW1015X ERROR CODE WHILE ADDING [OWNER] AS APPROVER AT WORKFLOW STAGE.

APAR status

• Closed as program error.

Error description

• Email action fails with following exceptions while adding
  [owner] as approvers in workflow stage.
  
  Error in WCM authoring portlet.
  
  IWKPW1015X: E-mail action was unable to add recipients
  
  Steps to recreate the issue.
  
  (1) Configure SMTP server in WCMConfigServices.properties to in
  workflow
  
  (2) Add valid email id of the admin user.
  
  (3) Create a email action , select "E-mail Stage Approvers" and
  save it.
  
  (4) Add this action in publish stage , in approver add [owners]
  and save publish stage.
  
  (5) Create a content with above workflow and publish the
  content. It should send email to the [owners] , i.e. to admin
  user, however it fails with following error on screen,
  
  Email_Action: FAILED - IWKPW1015X: E-mail action was unable to
  add recipients
  
  No exceptions in logs.
  
  (6) If we add owner direcly i.e. Direcly "wpsadmin" instead of
  [owners] , email action works well.
  

Local fix

• Add Owner direcly instead of [owner] in workflow stage.
  

Problem summary

• Problem Summary:
  EMAIL ACTION FAILS TO SEND MAY SEE IWKPW1015X ERROR CODE
  [OWNER, author or creator] AS APPROVER AT WORKFLOW STAGE.
  

Problem conclusion

• Detailed Problem Description:
  When owners, authors or creator are selected as Approver and an
  email action is set to E-mail stage approvers these virtual
  groups are not resolved.  Under Workflow > ACTIONS section users
  may see:
  
  Email_Action: FAILED - IWKPW1015X: E-mail action was unable to
  add recipients
  
  Traces ( com.aptrix.pluto.workflow.actions.*=all ) will show
  lines like:
  EmailAction   2   Sending 3 emails to: [
     PrincipalInformation: {dn: author_user, memberId:
  author_user_id, displayName: null, name: null, locale: null,
  isValidUser: true, isUser: Type: User, isUserLazyLoaded: false},
     PrincipalInformation: {dn: creator_user, memberId:
  creator_user_id, displayName: null, name: null, locale: null,
  isValidUser: true, isUser: Type: User, isUserLazyLoaded: false},
     PrincipalInformation: {dn: owner_user, memberId:
  owner_user_id, displayName: null, name: null, locale: null,
  isValidUser: true, isUser: Type: User, isUserLazyLoaded: false}]
  
  
  There wont necessarily be 3 emails sent the dn is the important
  part of the message. Where either or any of the following are
  listed:
  
     author_user, owner_user, creator_user
  
  Problem Analysis:
  The virtual groups author_user, owner_user, creator_user are not
  being resolved as expected and therefore no email address is
  available for these virtual groups.
  
  Problem Solution:
  The code has been updated to resolve the virtual groups
  author_user, owner_user, creator_user
  
  Affected Users:
  All Users
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R61A PSY

     UP

• R61B PSY

     UP

• R61C PSY

     UP

• R610 PSY

     UP

• R615 PSY

     UP