Changes between Version 5 and Version 6 of SchedTechManual/ServerChanges1_7


Ignore:
Timestamp:
Jul 10, 2012, 3:32:00 PM (12 years ago)
Author:
Sam Habiel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SchedTechManual/ServerChanges1_7

    v5 v6  
    5858 * Lock appointment
    5959 * Check if appointment can be cancelled in PIMS
    60  * Add cancellation data in ^BSDXAPPT (rollback: none needed on failure)
     60 * Add cancellation data in BSDX APPOINTMENT (rollback: none needed on failure)
    6161 * Cancel appointment in 2 (rollback: remove cancellation data)
    6262 * Delete appointment in 44 (no error detection as Fileman is not expected to fail)
     
    7070Limitations of Rollback: If an M error occurs in the event driver, I do not uncancel in file 2 and restore the entry in file 44.
    7171
    72 === BSDX25 (Check-in and Remove Check-in)
     72=== BSDX25 (Check-in and Remove Check-in) ===
    7373Workflow for Check-in:
    7474 * Lock appointment
    7575 * Check if we can check-in the appointment in PIMS
    76  * Check-in the appointment
     76 * Check-in the appointment in BSDX APPOINTMENT (rollback: none needed on failure)
     77 * Add check-in in file 44 (rollback: remove check-in in BSDX APPOINTMENT)
     78 * Call event driver (point of no return)
     79
     80Rollback strategy: Single point of failure: reverse check-in at BSDX APPOINTMENT.
     81
     82M Error Handling: none. If the error occurs inside BSDXAPI, the same rollback activates and rolls back check-in in BSDX APPOINTMENT.
     83
     84Limitations of Rollback: If an M error occurs in BSDX25 after BSDX APPOINTMENT filing, it is not rolled back.
     85
     86Workflow for Remove Check-in:
     87 * Lock appointment
     88 * Check if check-in can be removed in PIMS
     89 * Get old check-in date and save off in case of rollback.
     90 * Remove check-in from BSDX APPOINTMENT (rollback: none needed on failure)
     91 * Remove check-in from 44 (rollback: put check-in back into BSDX APPOINTMENT)
     92 * Call event driver (point of no return)
     93
     94Rollback strategy: Single point of failure: reverse check-in at BSDX APPOINTMENT.
     95
     96M Error Handling: none. If the error occurs inside BSDXAPI, the same rollback activates and puts back the check-in in BSDX APPOINTMENT.
    7797== Unit Test Routines ==
    7898