Implicit registration: how to keep bookings in sync?
Does anybody know why, when trying to delete a sessional registration in Student File with implicit registration turned on, the underlying bookings for that session are not cleared? No warning, no nothing?
It doesn't look like desired behavior as it fails to keep related data in sync. Also, it's most likely confusing for the end users. Otherwise the registration tab would provide a neat overview when the student was registered, when had a leave of absence, etc.
And, if the sessional registration is deleted while the bookings are left, does this mismatch create conflicts somewhere else in the system?
Joachim Plumbaum replied
there are multiple reasons for this behaviour, e. g.
a) Cancellation of sessional registrations are a kind of "undo" for the explicit registration - institutions using the function in the implicit registrtion case do that mainly for maintenance purposes only. There is a function in module booking to "withdrawal from module" to cancel all current module bookings. Also deregistration allows you to cancel automatically the module bookings.
b) The required behaviour for cancellation of sessional registrations with module bookings was different for different types of institutions. Thus it is possible to use VSR to configure the system behaviour: Issue a warning, prevent cancellation if module bookings exist, ...
Technically there shouldn't be an issue - however the students would still be booked to the modules (and use their capacity). The question is rather if you would want to allow that from a business process point of view. If not, you should prevent (via VSR) the cancellation if module bookings exist.
I hope that helps to understand the system behaviour. We know that it is important to keep some related information in synch in the way the institutional rules demand it. That is why we are thinking about a "post-process-framework" in SLCM to allow automation of particular "follow-up" activities.