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 | |
| 80 | Rollback strategy: Single point of failure: reverse check-in at BSDX APPOINTMENT. |
| 81 | |
| 82 | M Error Handling: none. If the error occurs inside BSDXAPI, the same rollback activates and rolls back check-in in BSDX APPOINTMENT. |
| 83 | |
| 84 | Limitations of Rollback: If an M error occurs in BSDX25 after BSDX APPOINTMENT filing, it is not rolled back. |
| 85 | |
| 86 | Workflow 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 | |
| 94 | Rollback strategy: Single point of failure: reverse check-in at BSDX APPOINTMENT. |
| 95 | |
| 96 | M Error Handling: none. If the error occurs inside BSDXAPI, the same rollback activates and puts back the check-in in BSDX APPOINTMENT. |