IBM Support

IJ37218: IN WORKFLOW THE NOSTATUS ACTION IS IGNORED BY TASK WORK ORDERS

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 a task work order is entered into workflow if the NOSTATUS
    Action is set the task is still allowed to change status. This
    is not true for parent work orders or for child work orders.
    For them the NOSTATUS Action works correctly and stops users
    from changing the status on the record. This message appears
    on screen:
    
    BMXAA4042E - The status cannot be changed for the selected
    records.
    
    Tested on MAS Manage 8.6. Sometimes tasks get the correct
     message and are blocked from changing status. In Manage it
    seems like the first record to go into WF works correctly and is
    blocked from changing status. If the first record is a Task it
    gets blocked and if the second record is a parent workorder it
    is allowed to change status when it, too, should be blocked.
    
    
    STEPS TO REPRODUCE:
    1. Create a simple workorder Object WF process in WF Designer
    with these nodes:
    Start--->TaskNode--->Stop
    
    2. On the Action line between Start and the Task Node put the
    NOSTATUS Action.
    3. For the Task Node create an Assignment row and assign it to
    Originator.
    4. Save, Enable and Activate the WF process.
    If the Add WF to applications dialog appears, click OK to add
    support. When it is done you must log out and log back in
    5. In Work Order Tracking create a new work order.
    6. Start it into the new WF process.
    7. Click on Change Status on the Action menu and it is blocked
    with the message shown above. This is correct as NOSTATUS was
    set when WF was started.
    8. On the Plans tab add a Task.
    9. Scroll down and find the Reference WO:, typically starting
    with T and having 4 or 5 digits.
    10. To launch the Task in WOTrack so that you can start it in WF
    click on All Records in the Available Queries section on the
    left.
    11. Then enter the Reference WO in the Work Order column.
    12. Bring up the Task and start it into the WF process.
    13. Click on Change Status on the Action menu and now the Change
    Status dialog opens. This is the bug, it should have been
    blocked.
    
    
    RESULTS:
    The workorder gets blocked correctly and can't change status.
    The same should happen to the task but it doesn't.
    As it says above, in Manage sometimes the opposite happens: the
    workorder is allowed to change status and the task is blocked.
    
    
    EXPECTED RESULTS:
    All records should be blocked from changing status while the
    NOSTATUS Action is in effect.
    
    REPORTED IN VERSION:
    7.6.1.2
    

Local fix

Problem summary

  • ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When NOSTATUS action is applied in workorder workflow        *
    * process, task work orders bypass this status block due to    *
    * source in the event response reference WORKORDER and not     *
    * WOACTIVITY.                                                  *
    ****************************************************************
    

Problem conclusion

  • Fixed
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ37218

  • 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

    2022-01-18

  • Closed date

    2022-02-09

  • Last modified date

    2022-02-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

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

Applicable component levels

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

Document Information

Modified date:
10 February 2022