IZ85159: WORKFLOW FAILS NO ASSIGNEMNTS MADE TO A ROLE

APAR status

• Closed as program error.

Error description

• Workflow fails no Assignemnts made to a Role
  ----------------------------------------------
  
  We created a Role as a dataset realated to the record WOACTIVTY
  The field that will hold the GroupName is the :OWNERGROUP
  The Group is a valid group and exists in the System. Assignments
  made
  via a Role Persongroup and value Helpdesk are working
  If the assignment is made to this role related to Dataset it
  fails.
  This is supposed to be a Workflow tool. If no assignments can be
  made to
  a Group defined as value in a Field I would not call it a
  Workflow
  Engine:
  
  
  A Role defined by  Dataset Option does not allow to place a
  field in
  scope which contains a PERSONGROUP name.
  
  A Role defined by PERSONGROUP does not allow to have a Field
  Value in
  the value field.
  
  When updating the database and setting the Role as Persongroup
  type and
  value as :FIELDNAME the assignments work
  
  Please change the product to not validate the PERSONGROUP type
  role
  values or allow to enter the values for Fields.
  
  A workflow engine that is not able to send assignments
  dynamically to
  Persongroups is not a workflow engine
  
  
  
  The error log shows an issue.
  
  ----------------------------------------------------------------
  
  
  Caused by:
  psdi.util.MXApplicationException: BMXAA4350E - The workflow
  process
  EFACTIFITY cannot be started in the background.
  BMXAA4473E - No assignments created for task NTYOWNER in
  workflow
  process EFACTIFITY.
  at
  psdi.workflow.WorkFlowService.initiateWorkflow(WorkFlowService.j
  ava:285)
  at psdi.common.action.Action.executeWFInitiate(Action.java:569)
  at psdi.common.action.Action.executeAppAction(Action.java:484)
  ... 14 more
  Caused by:
  psdi.util.MXApplicationException: BMXAA4473E - No assignments
  created
  for task NTYOWNER in workflow process EFACTIFITY.
  at psdi.workflow.WFTask.initializeTask(WFTask.java:151)
  at
  psdi.workflow.WFCallStackSet.applyWorkflowAction(WFCallStackSet.
  java:247
  )
  at
  psdi.workflow.WFCallStackSet.initiateWorkflow(WFCallStackSet.jav
  a:136)
  at
  psdi.workflow.WFInstance.initiateWorkflow(WFInstance.java:126)
  at psdi.workflow.WFProcess.initiateWorkflow(WFProcess.java:695)
  at
  psdi.workflow.virtual.InitiateWorkflowMboSet.execute(InitiateWor
  kflowMbo
  Set.java:89)
  at
  psdi.workflow.WorkFlowService.initiateWorkflow(WorkFlowService.j
  ava:270)
  ... 16 more
  [30.08.10 18:25:50:371 CEST] 000001b6 SystemOut O 30 Aug 2010
  18:25:50:371 [FATAL] Did not create assignments in workflow
  process
  EFACTIFITY, task NTYOWNER, on WOACTIVITY Mbo with key of 1'604
  [30.08.10 18:25:50:402 CEST] 000001b6 SystemOut O 30 Aug 2010
  18:25:50:402 [ERROR] Workflow EFACTIFITY started in background
  threw an
  exception, unable to initiate.
  
  ----------------------------------------------------------------
  
  
  IBM WebSphere Application Server 6.1
  Base Services 7.1.1.6-LA20100312-0937 Build 20091208-1415 DB
  Build
  SRM Service Desk 7.2.0.1 Build 20100316D2 DB Build V7201-04
  SRM Service Catalog Content 7.2.0.0 Build 20100226D DB Build
  V7200-07
  Windows Server 2008 6.1 build 7600
  
  ----------------------------------------------------------------
  
  STEP BY STEP instructions used by L1 Support to reproduce the
  problem.
  
  Create a Workflow with
  
  Start Node -> Assignment Node -> Stop Node
  On Object WOACTIVITY
  
  Create a New Role: EFOWNERGRP
  Set as : Related to MBO data
  On WOACTITY
  Value: :OWNERGROUP
  
  Create a Person Group
  Name Helpdesk
  Enter 2 Persons in Helpdesk
  
  
  Use the role created in the assignment Node on the Workflow
  Activate and Enable the Workflow
  
  Crate a WOACTIVTY record and before saving enter set the
  Ownergroup to
  HELPDESK
  
  Save the record.
  Start the Workflow Created above on the WOACTIVTY
  Error will show No Assigments can be created.
  
  
  Second Approach:
  
  Create a Workflow with
  Start Node -> Assignment Node -> Stop Node
  On Object WOACTIVITY
  
  Create a New Role: EFOWNERGRP
  Set as : PersonGroup
  On WOACTITY
  Value: :OWNERGROUP
  
  Try to tab out of the field:
  Error comes up that the Persongroup :OWNERGROUP is not a Person
  group.
  
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>
  How to get it working
  >>>>>>>>>>>>>>>>>>>>>>>>>>>
  
  Create a Workflow with
  Start Node -> Assignment Node -> Stop Node
  On Object WOACTIVITY
  
  Create a New Role: EFOWNERGRP
  Set as : PersonGroup
  On WOACTITY
  Value: Helpdesk
  
  !!! Open SQL Developer and run an update maxrole set value =
  ':OWNERGROUP' where name = EFOWNERGRP
  
  Create a Person Group
  Name Helpdesk
  Enter 2 Persons in Helpdesk
  
  
  Use the role created in the assignment Node on the Workflow
  Activate and Enable the Workflow
  
  Crate a WOACTIVTY record and before saving enter set the
  Ownergroup to
  HELPDESK
  
  Save the record.
  Start the Workflow Created above on the WOACTIVTY
  Assigments can be created !!!
  
  
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: all                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Due to a design omission, it was        *
  *                      impossible to generate an assignment    *
  *                      for a Role related to the Mbo           *
  *                      controlled by workflow. This came about *
  *                      from restrictions inherent in the       *
  *                      design. To fix this, a new              *
  *                      "relationship" attribute has been added *
  *                      to the WFAssignment table.              *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  There was no way to generate an assignment for a Role related
  to the controlled Mbo
  

Problem conclusion

• WFAssignment table expanded to handle this case.
  
  
  
  
  
  The fix for this APAR is contained in the following maintenance
  package:
  
    | release\fix pack | REL 7.1.1.8 - 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