IBM Support

IJ45535: SIGOPTION'S CONDITION IS NOT INITIALLY TAKEN INTO ACCOUNT

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

  • PROBLEM DESCRIPTION:
    The Condition set via a Sigoption is not initially taken into
    account in the subtabs on the Plans tab in Work Order Tracking.
    For example, set a Condition to have the Plans/Services subtab
    in WO to be read-only for a specific Security Group. But when
    you first access this Services subtab, the read-only Condition
    is not working straight away and you can actually modify values
    and save them before the read-only Condition takes effect.
     
    STEPS TO REPRODUCE: 
    * Log in as User maxadmin.
    * Go to Conditional Expression Manager.
    * Create a new record: Condition = WO-ACT, Description = [WO
    Class = ACTIVITY], Type = Expression, Expression (on Object
    WORKORDER) = [ :woclass = 'ACTIVITY], Always Evaluate? =
    checked
    * Save the record.
    * Go to Application Designer and select WOTRACK.
    * Do Add/Modify Signature Options
    * Create new option SIGOPTION-1 SigOption-1 with Visible? =
    checked and OK.
    * Go to Security Groups and select MAXADMIN.
    * Go to Applications tab and select WOTRACK.
    * In Options table, search for SigOption-1 and grant access to
    it and save.
    * Go to Application Designer and select WOTRACK.
    * Select the Plans tab and then Services sub-tab
    * Right-click on Services (entire tab should be highlighted in
    green) and select Properties
    * For Control ID : plans_plans_services_services_table, go to
    Advanced tab
    * Set Signature Option = SIGOPTION-1 and Sig Option Data Source
    ID = MAINRECORD
    * Select Configure Conditional Properties 
    * Select MAXADMIN Group, then select Condition WO-ACT
    * On Condition is true tab, enter Property = inputmode and
    Value = readonly
    * Do not enter anything in Condition is false tab.
    * Click OK, close dialog and save.
    * Log back into Maximo as same User maxadmin.
    * Go to Work Order Tracking and open a record which has Class =
    ACTIVITY, Status = WAPPR and a value in Plans/Services
    * Go to Plans/Services subtab: it has one row.
    * Do not expand the row but change the Quantity value directly
    on the row.
    * Save the record.
    * The change was saved even though the fields are supposed to be
    read-only.
    * Try to change the value of Quantity or Unit Cost fields: this
    time, the fields are read-only as expected.
    * Reopen the Work Order Tracking application from the Go To menu
    and repeat the test with the same record.
    * Once again, a value can be changed on the minimized row.
     
    RESULTS: 
    The Condition (read-only in this example) is not applied right
    away when you first access the Services subtab. It only works
    after a small UI change:  for example if you expand the row or
    move to another subtab and then back to the original subtab
    where the Condition was set.
    
    EXPECTED RESULTS:
    
    The Condition should be applied straight away as soon as you
    access the subtab.
     
    REPORTED IN VERSION: 
    Maximo TPAE 7.6.1.2
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * SIGOPTION'S CONDITION IS NOT INITIALLY TAKEN INTO ACCOUNT    *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 8.x Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ45535

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-02-21

  • Closed date

    2023-03-10

  • Last modified date

    2023-03-10

  • 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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

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:
10 March 2023