IBM Support

IJ10673: WORK FLOW ESCALATION ISSUE WHEN TIME ZONE AND LOCALE IS DIFFERENT.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • When trying to route a work flow from a Europe/Paris time zone
    and fr locale to user in US/Eastern tine zone with a En_US
    locale the work flow record is not being escalated as needed.
    
    STEPS TO REPRODUCE:
    
    1. Create a role that we can use for the escalation, add a
    name, type = person, object left blank and in the value field
    add the name of the person we want to escalate to.
    
    2. Create the escalation that applies to wfassignment, leave the
    condition field blank, in the escalation point in the elapsed
    time attribute add due date, check the repeat field and use an
    interval of minutes. In the actions portion of the screen hyper-
    link over to the actions application. Create a new action,
    object = wfassignment, type = application action, value
    wfescalate, save and return with the value.
    
    3. Create a new work flow process, add 2 task nodes. For first
    task node add your labor that has a Time Zone in Europe/Paris
    and locale is French, add your positive line, make sure to
    change the time limit to 0:02. Add another task node that goes
    to a user that has a Time Zone in US/Eastern and Locale is
    en_US. Now save and activate process.
    
    4. Create a new work order with a location added and add it to
    the process we created. Check and you can see that it is now in
    the users inbox, wait for the time to pass and allow the
    escalation to run. Once the escalation runs notice that the
    record has not been escalated, it stays in the same inbox.
    
    EXPECTED RESULTS:
    
    That the record would have escalated to the needed user.
    
    PRODUCT VERSION:
    
    Maximo 7.6.0.9
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Organizations with users in multiple locales.                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When escalating a workflow to be assigned to a user in a     *
    * locale different than the escalation run-as user's locale,   *
    * if the two locales have represent numeric strings different  *
    * (1,000 vs 1.000), the workflow assignment may fail.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is included in the following package:
                            | Release 7.6.1.1 of Base Services.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ10673

  • Reported component name

    WORK ORDERS

  • Reported component ID

    5724R46WO

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-22

  • Closed date

    2018-11-09

  • Last modified date

    2018-11-09

  • 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

    WORK ORDERS

  • Fixed component ID

    5724R46WO

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management
Work Order Tracking

Software version: 760

Reference #: IJ10673

Modified date: 09 November 2018