IBM Support

IV41641: CUSTOMER REPORTED THAT THE WFASSIGNMENT.DUEDATE NO LONGER POPULATES DATE AFTER THE UPGRADE TO 7.5.0.3

 

APAR status

  • Closed as program error.

Error description

  • Customer reported that the wfassignment.duedate no longer
    populates date after the upgrade to 7.5.0.3 (from 7.5.0.2).
    
    As per client, in 7.5.0.2 and earlier, when a record is routed
    into
    Workflow and assigned to a Task Node where the task node has a
    time
    limit set; Maximo will populate the wfassignment.duedate with
    its due
    date (startdate + timelimit) for that active record. Since the
    7.5.0.3
    patch it appeared this functionality is no longer working.
    
    Steps in Maximo 7.5.0.2
    1) Create a simple Workorder Workflow with a Task Node and time
    limit
    2) Setup users with supervisors: (wilson > winston > cswilson) .
    Example:  CSWILSON is supervisor of WINSTON, which is supervisor
    of
    WILSON)
    3) Log in with wilson and create a simple Workorder. (wonum =
    1405)
    4) Click the Workflow icon and initiate workflow created in Step
    1
    5) Verify the Workflow is routed to wilson supervisor (winston),
    by
    going to Select Actions-> View Workflow Assignments
    6) On a SQL Tool, run the following SQL statement:
    
    select * from wfassignment where assignstatus = 'ACTIVE' and
    ownerid in
    (select workorderid from workorder where wonum = '1405');
    
    Note the Due date is populated on the wfassignment table.
    
    So, this is working as expected in 7.5.0.2
    
    
    
    (Exact same thing, but in 7.5.0.3)
    
    Steps in Maximo 7.5.0.3
    1) Create a simple Workorder Workflow with a Task Node and time
    limit
    2) Setup users with supervisors: (wilson > winston > cswilson) .
    Example:  CSWILSON is supervisor of WINSTON, which is supervisor
    of
    WILSON)
    3) Log in with wilson and create a simple Workorder. (wonum =
    1279)
    4) Click the Workflow icon and initiate workflow created in Step
    1
    5) Verify the Workflow is routed to wilson supervisor (winston),
    by
    going to Select Actions-> View Workflow Assignments
    6) On a SQL Tool, run the following SQL statement:
    
    select * from wfassignment where assignstatus = 'ACTIVE' and
    ownerid in
    (select workorderid from workorder where wonum = '1279');
    
    Note the Due date is NOT populated.
    
    So, this is NOT working as expected in 7.5.0.3
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo Users using Workflow                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * CUSTOMER REPORTED THAT THE WFASSIGNMENT.DUEDATE NO           *
    * LONGERPOPULATES DATE AFTER THE UPGRADE TO 7.5.0.3            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixpack 7.5.0.5 of Base Services or request interim    *
    * fix                                                          *
    ****************************************************************
    

Problem conclusion

  • Fix has been made to populate due date for workflow assignments.
    
    The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack\interim fix for Release 7.5.0.5 of Base
    Services,
    	 Interim Fix 7.5.0.3 of Base Services and Interim Fix 7.5.0.4
    of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV41641

  • Reported component name

    WORK & MTRL APP

  • Reported component ID

    TIVOWRKMM

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-05-06

  • Closed date

    2013-08-02

  • Last modified date

    2013-08-02

  • 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

    WORK & MTRL APP

  • Fixed component ID

    TIVOWRKMM

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
02 August 2013