Repository navigation
Conversation
KesterJJ
force-pushed
the
fix/place/vip-visitor-driver-packaging
branch
from
November 18, 2026 08:18
1db1433 to
8240249
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The VIP workflow exposed only an all-in-one processing method, making individual stages difficult to test in Backoffice. It also fixed the Planner destination at module level and duplicated email presentation and notification controls in module settings.
This update adds administrator-only booking lookup, read-only preview and workflow status, independent invitation/confirmation/Planner/arrival/departure operations, and
submit_confirmationwith the actual AECB enrolment form fields. Submission merges the fields into the booking with the fixedvip_confirmedmarker, then runs the confirmation workflow.building_nameandlevel_namefrom zone display names. Leave maps, parking and valet wording and recipient overrides to email templates; template presence controls arrival/departure sending.Validation: the driver and expanded spec compiled and passed the PlaceOS harness (1 tested, 0 failures, 0 timeouts), with the old helper absent. Crystal formatting and git diff checks pass. Services were mocked; no live email or Planner resources were created.
External-form integration remains separate: the current frontend sends no acceptance marker, and the restricted guest token needs a scoped booking confirmation endpoint. The new Backoffice method tests the downstream workflow without claiming that external endpoint already exists. Existing deployed driver records are unchanged.