IBM Support

IJ17226: WORKFLOW TASK DESCRIPTION ASSIGNMENT BINDING PROBLEM FOR ASSIGNEE RELATIONSHIP, DISPLAYS ":PERSONID" INSTEAD OF ACTUAL ID

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Summary:
    Maximo 7.6.1.0 and Control Desk 7.6.1 Workflow Task Description
    assignment binding problem for Assignee Relationship, eg.
    Displays ":personid" instead of actual person id.
    
    Problem Description:
    Maximo 7.6.1.0 and Control Desk 7.6.1 Workflow Task Description
    assignment binding problem for Assignee Relationship, eg.
    Displays ":personid" instead of actual person id.
    The error is occurring specifically because of Maximo APAR
    IJ02952. The substitution of bind variables in DESCRIPTION only
    occurs if there is a roleid. However, if task node doesn't have
    a roleid, and instead it has an assignee relationship, it never
    substitutes the workflow variables.
    
    STEPS TO REPRODUCE:
    Failed on an out-of-box Control Desk workflow with a task that
    has an Assignee Relationship.
    a) Duplicate workflow 'PMCHGFIXD1' to 'PMTSTFIXD1'
    b) For Task "@AUTH", edit task properties. (Note: This task has
    an Assignee Relationship, instead of a roleid.)
    c) Add ":personid" to Task Description (eg. Assignee
    Relationship = PMCHGOTHERAPPROVERS.PMCHGOTHERAPPROVERSAPPROVER)
    - Replace: "Approve or Reject Change :wonum
    (:&owner&.description)"
    - With: "Approve or Reject Change :wonum - (:personid)
    (:&owner&.description)"
    d) Enable & Activate new test workflow.
    e) Create new Change. Do not start workflow yet.
    f) Goto Authorization tab. Add new row:
    - Approver: MAXADMIN (Also, add description "test other
    approver")
    g) Save
    h) Route Workflow = PMTSTFIXD1 (the duplicate test workflow with
    ':personid')
    i) Complete assignment(s) until you reach the '@AUTH' task.
    j) Observe workflow inbox assignment.
    k) PROBLEM: Assignment result: "Approve or Reject Change 1028 -
    (:personid) (:&owner&.description)"
    - Note: Fails for added ':personid', but also failed for
    original '(:&owner&.description)'.
    l) EXPECTED: Assignment result: "Approve or Reject Change 1028 -
    (MAXADMIN) (test other approver)"
    
    RESULTS:
    Assignment result: "Approve or Reject Change 1028 - (:personid)
    (:&owner&.description)"
    
    EXPECTED RESULTS:
    Assignment result: "Approve or Reject Change 1028 - (MAXADMIN)
    (test other approver)"
    
    REPORTED IN VERSION:
    Maximo Asset Management 7.6.1.0 (and Control Desk 7.6.1 )
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo users on 7.6.1 and 7.6.1.1 who use Assignee           *
    * Relationships and Task Description bind variables needing to *
    * be resolved from related MBOs on task nodes.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Maximo 7.6.1.0 and Control Desk 7.6.1 Workflow Task          *
    * Description assignment binding problem for Assignee          *
    * Relationship: ":personid" appears in assignment's            *
    * description in the Start Center instead of the actual person *
    * id.                                                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Maximo 7.6.1 and 7.6.1.1 Workflow Task Description assignment
    binding problem for Assignee Relationship, eg. Displays
    ":personid" instead of actual person id.
    The error is occurring specifically because of Maximo APAR
    IJ02952. The substitution of bind variables in DESCRIPTION only
    occurs if there is a roleid. However, if task node doesn't have
    a roleid, and instead it has an assignee relationship, it never
    substitutes the workflow variables.
    
    STEPS TO REPRODUCE:
    Failed on an out-of-box Control Desk workflow with a task that
    has an Assignee Relationship, but also occurs in core without
    Control Desk.
    a) Duplicate workflow 'PMCHGFIXD1' to 'PMTSTFIXD1'
    b) For Task "@AUTH", edit task properties. (Note: This task has
    an Assignee Relationship, instead of a roleid.)
    c) Add ":personid" to Task Description (eg. Assignee
    Relationship = PMCHGOTHERAPPROVERS.PMCHGOTHERAPPROVERSAPPROVER)
    - Replace: "Approve or Reject Change :wonum
    (:&owner&.description)"
    - With: "Approve or Reject Change :wonum - (:personid)
    (:&owner&.description)"
    d) Enable & Activate new test workflow.
    e) Create new Change. Do not start workflow yet.
    f) Goto Authorization tab. Add new row:
    - Approver: MAXADMIN (Also, add description "test other
    approver")
    g) Save
    h) Route Workflow = PMTSTFIXD1 (the duplicate test workflow with
    ':personid')
    i) Complete assignment(s) until you reach the '@AUTH' task.
    j) Observe workflow inbox assignment.
    k) PROBLEM: Assignment result: "Approve or Reject Change 1028 -
    (:personid) (:&owner&.description)"
    - Note: Fails for added ':personid', but also failed for
    original '(:&owner&.description)'.
    l) EXPECTED: Assignment result: "Approve or Reject Change 1028 -
    (MAXADMIN) (test other approver)"
    
    RESULTS:
    Assignment result: "Approve or Reject Change 1028 - (:personid)
    (:&owner&.description)"
    
    EXPECTED RESULTS:
    Assignment result: "Approve or Reject Change 1028 - (MAXADMIN)
    (test other approver)"
    
    REPORTED IN VERSION:
    Maximo Asset Management 7.6.1 and 7.6.1.1
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Interim Fix for Release 7.6.1.2
    
    The fix for this APAR backs out the fix for IJ02952. The problem
    described by APAR IJ02952 ultimately is not a bug and does not
    require a code change. Refer to the following Tech Note re: the
    workflow configuration modification necessary to address the
    behavior described in IJ02952.
    
    https://www.ibm.com/support/pages/node/5694243
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ17226

  • Reported component name

    SYSTEM CONFIG

  • Reported component ID

    5724R46S1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-25

  • Closed date

    2020-03-09

  • Last modified date

    2024-10-29

  • 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

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
29 October 2024