IZ89926: WORKFLOW NOTIFICATIONS BEING SENT WHEN CONDITION IS NOT MET

APAR status

• Closed as program error.

Error description

• Workflow Notifications being sent when condition is not met
  
  Maximo 7
  
  1)  Sign into Maximo - Go to - System Configuration - Platform
  Configuration - Workflow Designer - Click on New - Process =
  WOTEST - Object = WORKORDER.  Add a Condition Node to the Canvas
  - right click on the condition node - select properties.  Title
  = CHECKSTAT - Expression = :status in ('CLOSE,'COMP') click OK.
  Click on the Positive Node pencil - Add a connection from Start
  to CHECKSTAT.  Add another positive connection between CHECKSTAT
  to STOP.
  
  Add a Task Node to the Canvas - click on the new task node -
  select Properties - Title = ASSIGN - Application = WOTRACK.  In
  the Assignments pane - click on New Row - RoleID = WOLEAD -
  Application = WOTRACK - Communication Template = WFASSIGN - Send
  Email? = Checked.
  
  Click on the Negative Node pencil and add a negative connection
  between CHECKSTAT and ASSIGN.
  
  Add another Task Node to the Canvas.  click on the new task node
  - select Properties - Title = INPRG - Application = WOTRACK.  In
  the Assignments Pane - click on New Row - RoleID = WOLEAD,
  Application = WOTRACK, Communication Template = WFASSIGN.  In
  the Notifications pane - click on New Row - In the Communication
  Template field - hyperlink to the Communication Templates
  application - click on New Row - Template - WOTEST - Applies to
  = WORKORDER - Send from = maxadmin@maximodemo.com, Subject =
  Workorder :wonum is in a status of INPRG.  Click on the
  Recipients tab - in the Role(s) for Communication Template click
  on New Row - in the Role field - hyperlink to the Roles
  application - click on new Role - Role = WOSUPERV - Type = A Set
  of data related to the record - Object = WORKORDER - value =
  :supervisor - click on Save - Return with Value.  Now from the
  Communication Templates - click on Save - Click on Change Status
  - Make the Communication Template Active -  Click on Return with
  Value to go back to the Task Node Properties.  Click on OK.
  
  Add a positive connection between the ASSIGN Task Node and the
  INPRG task node.  Right click on the postive connection between
  ASSIGN and INPRG - Add the Action = WO INPRG - click on Ok.
  Then create a positive connection between the INPRG task node
  and the Stop.
  
  Click on Save - Validate the Workflow - Enable the Workflow -
  Activate the workflow from the Select Action.
  
  Go to - Administration - Conditional Expression Manager - Create
  a new condition called WOTEST.  Expression = :status <> 'WSCH'.
  Check Always Evaluate.  Go to Security - Security Group - click
  on Select Action - Global Data Restrictions - Click on the
  Attribute Restrictions - click on New Row - Object = WORKORDER -
  Attribute = SCHEDFINISH - Application = WOTRACK - Type =
  REQUIRED - Condition = WOTEST.  Click on New Row - Object =
  WORKORDER - Attribute = SCHEDSTART - Application = WOTRACK -
  Type = REQUIRED - Condition = WOTEST.  Click on OK.
  
  Sign out - Sign in as MAXADMIN.  Go to PM application - create a
  new PM - Asset = 1004 - Save - Change the status to Active -
  Click on Select Action - Generate Work Orders - Uncheck - Use
  Frequency Criteria? - Click on OK.  Note the Workorder.  (In
  this example Workorder = 1166)
  
  Go to Workorder Tracking - Access workorder 1166.  Within the
  Supervisor fields enter MAXADMIN.  For the Lead field enter
  MAXADMIN.  Click on Save.  Click on the Route Work Flow button.
  Process = WOTEST.  Click OK.  As Maxadmin  - Go to Start Center
  - Within the Inbox/Assignments - click on the Route Workflow
  button for the Workorder just put through the workflow process.
  Click OK for the Action of Workorder in progress.  An error
  message will appear:  BMXAA4195E - Required field Scheduled
  Start is Blank.
  
  But if you access the mail account for MAXADMIN - The email from
  the INPRG node is sent.  Workorder 1166 is in progress.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: all                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: This problem occurs when attributes are *
  *                      made required by the presentation UI or *
  *                      data rules. Workflow completes and      *
  *                      tries to save the record, but there are *
  *                      missing required attributes, and the    *
  *                      result is that the UI and Workflow are  *
  *                      left in an unstable state.              *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  Validation errors mess up workflow.
  

Problem conclusion

• Perform a validation before attempting to save.
  
  
  
  
  
  The fix for this APAR is contained in the following maintenance
  package:
  
    | release\fix pack | REL 7.1.1.9 - BS
  

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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  MAXIMO SYS CONF

• Fixed component ID

  5724R46S1

Applicable component levels

• R711 PSY

     UP