Maximo Open Forum

 View Only
Expand all | Collapse all

Cloned SR application with custom table needs to be edited even when ticket is in History

  • 1.  Cloned SR application with custom table needs to be edited even when ticket is in History

    Posted yesterday

    I have created a custom table, RAMSPECIFICS, that is related to the TICKET table by TICKETID and SITEID.  I have cloned the SR application so that this custom table can have its values edited and all works well until the Ticket has the HISTORYFLAG set.  I don't need or want the TICKET table to be edited but the new custom table, RAMSPECIFICS, needs to be edited even if the Ticket has a HISTORYFLAG=1.  How can I accomplish this?

    I am comfortable with automation scripting, but have never worked with modifying Java classes and would like to avoid it if possible, but if this is the course that needs to be taken I would like to be pointed to step by step directions in making changes to the Java.

    Thank you very much for your consideration.

    Rick


    #Administration
    #Analytics
    #Architecture
    #Assets
    #CivilInfrastructure
    #Customizations
    #EndUser
    #EverythingMaximo
    #HSE/OilandGas
    #Infrastructure
    #Integrations
    #Inventory
    #IoT
    #LifeScience/Calibration
    #Linear
    #MaximoApplicationSuite
    #MaximoForAviation
    #MaximoUserGroups
    #Mobility
    #Nuclear
    #Procurement
    #Reporting
    #Scheduling
    #Security
    #ServiceProvider
    #Spatial
    #Transportation
    #Utilities
    #WorkCenters
    #WorkManagement
    #MaximoVisualInspection
    #Predict
    #Monitor
    #Health
    #Assist
    #Safety

    ------------------------------
    Rick Viera
    General Dynamics Mission Systems
    ------------------------------


  • 2.  RE: Cloned SR application with custom table needs to be edited even when ticket is in History

    Posted 17 hours ago

    You can't have it as a child object and editable on a history ticket without going through the edit history feature of tickets. When the parent MBO is read-only the Maximo framework automatically cascades down to the child objects and won't let the record be saved. It'd be sort of an ugly hack but as long as you don't depend on the parent object being the ticket, you can create a dialog where the main object is your custom object with the fields editable. Then you could add an action for a user to open the dialog. 



    ------------------------------
    Steven Shull
    Naviam
    ------------------------------