com.ibm.tivoli.maximo.appt.app

Class ApptBook

    • Constructor Detail

      • ApptBook

        public ApptBook(MboSet ms)
                 throws java.rmi.RemoteException
        Throws:
        java.rmi.RemoteException
    • Method Detail

      • init

        public void init()
                  throws MXException
        Description copied from class: Mbo
        Called by the framework when the Mbo has been constructed and the MboValues have been initialized. This can be overridden by the programmer to provide any custom initialization they would like to do.
        Overrides:
        init in class Mbo
        Throws:
        MXException
      • add

        public void add()
                 throws MXException,
                        java.rmi.RemoteException
        Description copied from class: Mbo
        This is called when a new Mbo is added to the Mboset collection. It is called AFTER user defaults have been set from the data dictionary. Programmer should usually override this to set some defaults. Default behavior is to do nothing.
        Specified by:
        add in interface MboRemote
        Overrides:
        add in class Mbo
        Throws:
        MXException
        java.rmi.RemoteException
      • save

        protected void save()
                     throws MXException,
                            java.rmi.RemoteException
        Description copied from class: StatefulMbo
        Overrides the save of Mbo so that a row is added to the status history table when a new object is saved.
        Overrides:
        save in class StatefulMbo
        Throws:
        MXException
        java.rmi.RemoteException
      • appValidate

        public void appValidate()
                         throws MXException,
                                java.rmi.RemoteException
        Description copied from class: Mbo
        Pre-save validation method. Programmer can override with specific rules.
        Overrides:
        appValidate in class Mbo
        Throws:
        MXException
        java.rmi.RemoteException
      • validateApptBookName

        protected void validateApptBookName()
                                     throws java.rmi.RemoteException,
                                            MXException
        Check if there's an existing ApptBook record with the same name.
        Throws:
        java.rmi.RemoteException
        MXException
      • canAapplyApptWindows

        public boolean canAapplyApptWindows()
                                     throws MXException,
                                            java.rmi.RemoteException
        canApplyApptWindow() is called before apply the window. So, the user doesn't need to explicitly call canApplyApptWindow().
        Specified by:
        canAapplyApptWindows in interface ApptBookRemote
        Throws:
        MXException
        java.rmi.RemoteException
      • checkShiftsDateLimits

        public void checkShiftsDateLimits()
                                   throws MXException,
                                          java.rmi.RemoteException
        Description copied from interface: ApptBookRemote
        Checks if at least one work period from the selected calendar is inside the start and end dates limits. This method is called before apply the window. So, the user doesn't need to explicitly call it.
        Specified by:
        checkShiftsDateLimits in interface ApptBookRemote
        Throws:
        MXException
        java.rmi.RemoteException
      • applyApptWindows

        public void applyApptWindows()
                              throws MXException,
                                     java.rmi.RemoteException
        Propagates APPTBKWINDOWAVAIL records from start date to end date of the apptbook for the input appt windows definition. canApplyApptWindow() is called before apply the window. So, the user doesn't need to explicitly call canApplyApptWindow().
        Specified by:
        applyApptWindows in interface ApptBookRemote
        Throws:
        MXException
        java.rmi.RemoteException
      • applyApptWindow

        public void applyApptWindow(MboRemote apptWindow)
                             throws MXException,
                                    java.rmi.RemoteException
        Propagates APPTBKWINDOWAVAIL records from start date to end date of the apptbook for the input appt windows definition. canApplyApptWindow() is called before apply the window. So, the user doesn't need to explicitly call canApplyApptWindow().
        Specified by:
        applyApptWindow in interface ApptBookRemote
        Throws:
        MXException
        java.rmi.RemoteException
      • applyApptWindows

        public void applyApptWindows(java.util.Date startdate,
                                     java.util.Date enddate)
                              throws MXException,
                                     java.rmi.RemoteException
        Propagates APPTBKWINDOWAVAIL records from specified start date to end date for for the input appt windows definition. canApplyApptWindow() is called before apply the window. So, the user doesn't need to explicitly call canApplyApptWindow().
        Specified by:
        applyApptWindows in interface ApptBookRemote
        Throws:
        MXException
        java.rmi.RemoteException
      • applyApptWindow

        public void applyApptWindow(MboRemote apptwindow,
                                    java.util.Date startdate,
                                    java.util.Date enddate)
                             throws MXException,
                                    java.rmi.RemoteException
        Propagates APPTBKWINDOWAVAIL records from specified start date to end date for for the input appt windows definition. canApplyApptWindow() is called before apply the window. So, the user doesn't need to explicitly call canApplyApptWindow().
        Specified by:
        applyApptWindow in interface ApptBookRemote
        Throws:
        MXException
        java.rmi.RemoteException
      • getStatusHandler

        protected StatusHandler getStatusHandler()
        Description copied from class: StatefulMbo
        Return the status handler object to be used for the actual changing of the status. This is only called once by the framework. This method must be provided by the Mbo programmer.
        Specified by:
        getStatusHandler in class StatefulMbo
      • getStatusHistory

        protected MboSetRemote getStatusHistory()
                                         throws MXException,
                                                java.rmi.RemoteException
        Description copied from class: StatefulMbo
        Return the MboSet object used for storing the status change history. This method must be provided by the Mbo programmer.
        Specified by:
        getStatusHistory in class StatefulMbo
        Throws:
        MXException
        java.rmi.RemoteException
      • skipCopyField

        protected boolean skipCopyField(MboValueInfo mvi)
                                 throws java.rmi.RemoteException,
                                        MXException
        Overrides the skipCopyField() in the Mbo. Since this method takes the MboValueInfo as its parameter just check to see if this field needs to be copied or skipped by using the data from the static HashTable. If this field does not need to be copied return true. The following fields will be skipped without being copied to the newly duplicated object.
        1. WORKZONE
        Overrides:
        skipCopyField in class Mbo
        Parameters:
        - - The MboValueInfo object of the MboValue that needs to be copied.
        Returns:
        - True,if the field does not need to be copied.In all other cases return false.
        Throws:
        MXException
        java.rmi.RemoteException
      • canDelete

        public void canDelete()
                       throws MXException,
                              java.rmi.RemoteException
        Description copied from class: Mbo
        Can the object be deleted ? This is object specific and should be overridden.
        Overrides:
        canDelete in class Mbo
        Throws:
        MXException
        java.rmi.RemoteException
      • delete

        public void delete(long accessModifier)
                    throws MXException,
                           java.rmi.RemoteException
        Description copied from class: Mbo
        Mark the object to be deleted depending on the access modifier. This will usually be overridden in the subclass of Mbo as there may be application specific rules as to if and when an object can be deleted. Object is not actually deleted in the database until save() is called. This method will also mark all associated Long Description and Translation Mbos for deletion.
        Specified by:
        delete in interface MboRemote
        Overrides:
        delete in class Mbo
        Parameters:
        accessModifier - The bitwise flag specified to determine if certain normal security checks are to be bypassed for this delete request. For example: if the accessModifer is NOACCESSCHECK, then the check for the object's NODELETE flag and the call to the object's canDelete() method will not be performed. If the accessModifer is NONE, then all the access checks are performed before this object is marked delete.
        Throws:
        MXException
        java.rmi.RemoteException
        See Also:
        Mbo.delete(long)