psdi.app.workorder

Class WOActivity

    • Constructor Detail

    • Method Detail

      • add

        public void add()
                 throws MXException,
                        java.rmi.RemoteException
        Description copied from class: WO
        Adds a new Work Order. Field defaults are set as well as field flags.
        Specified by:
        add in interface WOActivityRemote
        Specified by:
        add in interface MboRemote
        Overrides:
        add in class WO
        Throws:
        MXException
        java.rmi.RemoteException
      • propagateKeyValue

        public void propagateKeyValue(java.lang.String keyName,
                                      java.lang.String keyValue)
                               throws MXException,
                                      java.rmi.RemoteException
        Set value for Wonum.
        Specified by:
        propagateKeyValue in interface MboRemote
        Overrides:
        propagateKeyValue in class WO
        Parameters:
        keyName - Should equal "wonum" or else nothing will be propagated.
        keyValue - The new value of wonum.
        Throws:
        MXException
        java.rmi.RemoteException
      • addmultiassetlocci

        public void addmultiassetlocci()
                                throws MXException,
                                       java.rmi.RemoteException
        add primary record inmultiassetrecord
        Throws:
        MXException
        java.rmi.RemoteException
      • appValidate

        public void appValidate()
                         throws MXException,
                                java.rmi.RemoteException
        10-20167: in Work Order Tracking - cannot add duplicated TASK ID that already exists, but it only checks the current MboSet. This will slip if two users enter the same task for the same wo from two browser. the system accepted it because the wonum for the duplicated task is different. Per proudct designer, this is a bug.
        Overrides:
        appValidate in class WO
        Throws:
        MXException - the mX exception
        java.rmi.RemoteException - the remote exception
      • copy

        public MboRemote copy(MboSetRemote mboset,
                              long mboAddFlags)
                       throws MXException,
                              java.rmi.RemoteException
        IV97553: in Ticket.duplicate(), it uses normal mboSet.copy(MboSetRemote) to copy existing WOACTIVITY set to a new WOACTIVITY. It does not have the skipCopyField logic, so everything is copied. WO.duplicate() handles the copy differently; this override is only for ticket duplicate with tasks. Override copy method on the mbo(the existing WOActivity) to call WO.loadSkipFieldCopyHashSet() to tell the mbo.copy(mbo, mboset, mboAddFlags) to skip the fields in the hashSet. Before 7503, Ticket.duplicate() used to call newActivity = activity.duplicate(); which will call WO.duplicate() and loadSkipFieldCopyHashSet is called if it has not been. Calling the activity.duplicate(), however, will not show the records on UI until saved which is not desirable either.
        Specified by:
        copy in interface MboRemote
        Overrides:
        copy in class Mbo
        Parameters:
        mboset - The set into which the new mbo will be added.
        mboAddFlags - Flags to use when adding the new Mbo. Values on the attribute are always set with NOACCESSCHECK|NOVALIDATION_AND_NOACTION.
        Returns:
        The new mbo, with values copied from this mbo.
        Throws:
        MXException
        java.rmi.RemoteException