IBM Support

IJ33582: VALIDATION DOES NOT WORK IN GRAPHICAL ASSIGNMENT FOR THE WOCHANGESTATUS.MEMO FIELD THAT WAS CHANGED TO MANDATORY

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

  • STEPS TO REPLICATE:
    - Go to Application Designer and open the Graphical Assignment
    application.
    - Go to 'Add/Modify Signature Options' and create a new
    sigoption MEMOBELOWSTATUS with a Description (Memo field in
    Change Status dialog) and Visible = checked.
    - Go to Security Groups, select the EVERYONE group and then the
    Graphical Assignment application. Grant the 'Memo field in
    Change Status dialog' option in the Options list and save.
    - Logout and close browser and login back into Maximo
    - Now go to Graphical Assignment application, select a record,
    go to Graphical View tab, right-click on a WO and select
    'Change Status': the Memo field is now visible in the 'Change
    Status' dialog.
    - Go to Automation Scripts.
    - Do Create / Script with Attribute Launch Point.
    Name = MEMOFLDSTATUS
    Description = Makes the Memo field required
    Object = WOCHANGESTATUS
    Attribute = STATUS
    Active = checked
    Event = Validate
    Script = New
    ---> Next
    
    Script = WC.WOCHANGESTATUS.MEMOFLDSTATUS.VAL
    Script language = jython
    Variables = add 1st new row:
    Variable = vMEMO, Variable Type = INOUT, Binding Type =
    ATTRIBUTE, Launch Pint Attribute = MEMO, Override = checked
    add 2nd new row:
    Variable = vSTATUS, Variable Type = INOUT, Binding Type =
    ATTRIBUTE, Launch Pint Attribute = STATUS, Override = checked
    ---> Next
    
    - Paste the following script:
    
    from com.ibm.gbs.util.logging import GBSAutomationScriptLogger
    from psdi.mbo import MboConstants
    from psdi.server import MXServer
    if
    MXServer.getMXServer().getMaximoDD().getTranslator().toInternalS
    tring("WOSTATUS",vSTATUS, mbo) == 'CAN':
      vMEMO_required = True
    else :
      vMEMO_required = False
    
    - Click 'Create'.
    - Log out of Maximo and log back in.
    - Go to Work Order Tracking.
    - Select a record in WAPPR status and select 'Change Status'
    option.
    - Change to APPRoved status. No issue.
    - Change to CANcelled status --> the Memo field is now flagged
    as mandatory (*) and if you click OK without populating the
    Memo field, you get this error "BMXAA4195E - A value is
    required for the Memo field on the WOCHANGESTATUS object".
    
    - Go to Graphical Assignment.
    - Select a record, go to Graphical View, select a WO in WAPPR
    status, do right-click and select 'Change Status' option.
    - Change to APPRoved status. No issue.
    - Change to APPR status. No issue.
    - Change to CANcelled status --> the Memo field is now flagged
    as mandatory but if you click OK without populating the Memo
    field, the status change is taken into account and you do NOT
    get the BMXAA4195E error this time.
    - The same Automation Script is NOT taken into account.
    Note: the behaviour is the same if the field validation is set
    directly in the XML file by adding inputmode="required" in
    <textbox dataattribute="Memo" ... > .
    RESULTS:
    The Automation Script is not taken into account and validation
    is not taking place.
    EXPECTED RESULTS:
    The Automation Script set on the MEMO field should be taken
    into account.
    
    REPORTED IN VERSION:
    Maximo TPAE 7.6.1.1
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Scheduler users                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following
    maintenancepackage:
    Release 7.6.1.3 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ33582

  • 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

    2021-07-04

  • Closed date

    2022-10-14

  • Last modified date

    2022-10-14

  • 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":"BU059","label":"IBM Software w\/o TPS"},"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:
15 October 2022