Learn how to increase the operational efficiency of the assets you manage, and improve overall equipment effectiveness by using IoT data and AI.



Reduce the operational costs of the facilities you manage, and create more engaging occupant experiences through the application of IoT data and AI.



Learn how IoT data and AI are being applied to transform the end-to-end engineering lifecycle.

Expand all | Collapse all

Prevent tasks from being converted to WOs

  • 1.  Prevent tasks from being converted to WOs

    Posted Sun October 18, 2020 09:05 PM

    In a related question, we determined that tasks can be converted to WOs by applying a Job Plan to a task or by adding a task to a task.  

    However, if 
    we don't want users to be able to convert tasks to WOs, is there a way to disable that functionality?


  • 2.  RE: Prevent tasks from being converted to WOs

    Posted Mon October 19, 2020 10:29 AM
    Taking away the ability to apply job plans to tasks and the ability to add tasks to tasks sounds like a good starting point. That should be pretty elementary App Designer work, making fields read-only and taking away buttons. If your concerned about code or integration sneaking by your App Designer changes, you could have an autoscript that just throws an error, e.g. service.error("mycompanywo","taskpromotionprohibited"), on object update before save where :$old_istask = :yes and :istask = :no.

    Jason Uppenborn
    Sr. Technical Maximo Consultant
    Ontracks Consulting

  • 3.  RE: Prevent tasks from being converted to WOs

    Posted Mon October 19, 2020 02:13 PM
    An AutoScript validation as suggested by Jason is a good fail safe.  Regarding the Application Designer changes:

    In the "Work Order Tracking" application, a Task cannot be promoted to a WO unless you allow a Task WO to appear as the "header" WO.  By default, the "Is Task?" field is set to "N" on the "More Search Fields" dialog.  But a user can change it to "Y" or clear it to include Tasks on the List tab.  A user can also type the Task's "Reference WO" in the "Find Work Order" field at the top.  To prevent this, you can add an Application Restriction to the <presentation> tag in the WOTrack.xml.  This can be done on the "Presentation Properties" dialog in Application Designer or by editing the XML.  The change in the WOTrack.xml would look something like this:

    <presentation apphelp=",wotrack/c_wo_tracking_application.html" apprestrictions="( WOClass IN ('WORKORDER') )" beanclass="...


    <presentation apphelp=",wotrack/c_wo_tracking_application.html" apprestrictions="( WOClass IN (SELECT Value FROM SynonymDomain WHERE DomainID = 'WOCLASS' and MaxValue = 'WORKORDER') )" beanclass="...

    For performance reasons, I recommend the first syntax and including any synonyms of "WORKORDER" in the "IN" list since that list should rarely change.  Do the same for the "Quick Reporting" application (QuickRep.xml).

    In the "Activities and Tasks" application (Activity.xml), hide the "Job Plan" and "Job Plan Revision Number" field on the "Resources", "Plans", and "Actuals" tabs and hide the "Tasks for Activity {0}" table on the "Plans" and "Actuals" tab.

    You should also not allow "ACTIVITY" to be selected on the "job Plan Class" table on the "Select Value" dialog for the "Default WO Class" field in the "Job Plan" application (JobPlan.xml).  This can be done by created a custom Table Domain that reads the WOCLASS Synonym Domain to select only Values with a MaxValue of "WORKORDER" and then changing the Domain for the JobPlanClass.WOClass attribute to the custom Domain in the Database Configuration application.

    Julio Hernandez