Change Details

Once T317705 is done, we want to write the code for actually calling the P&E dashboard API, although this won't be available to users just yet. ==== Acceptance criteria ==== - Add code that syncs an event with the P&E dashboard on event creation. - Add code that updates the event participants on the dashboard when a participant is added/removed. - Add translations of the possible error messages listed in T302584#7751395. ==== Out of scope ==== - User interface and API endpoints should not expose anything about tracking tools yet

Once T317705 is done, we want to write the code for actually calling the P&E dashboard API, although this won't be available to users just yet. ==== Acceptance criteria ==== - Add code that syncs an event with the P&E dashboard on event creation. - Add code that updates the event participants on the dashboard when a participant is added/removed. - Add translations of the possible error messages listed in T302584#7751395. ==== Out of scope ==== - User interface and API endpoints should not expose anything about tracking tools yet ==== Key points from meeting with Sage ==== - We can use either a batched job or "live" updates (via DeferredUpdate), whatever works best for us. - Watch out for race conditions when sending updates - The full list of participants may be potentially very long; make sure this is not a problem. - Private registrants should NOT be synced with the dashboard; we will create another task about making sure that this is explained transparently in the interface.

Once T317705 is done, we want to write the code for actually calling the P&E dashboard API, although this won't be available to users just yet. ==== Acceptance criteria ==== - Add code that syncs an event with the P&E dashboard on event creation. - Add code that updates the event participants on the dashboard when a participant is added/removed. - Add translations of the possible error messages listed in T302584#7751395. ==== Out of scope ==== - User interface and API endpoints should not expose anything about tracking tools yet ==== Key points from meeting with Sage ==== - We can use either a batched job or "live" updates (via DeferredUpdate), whatever works best for us. - Watch out for race conditions when sending updates - The full list of participants may be potentially very long; make sure this is not a problem. - Private registrants should NOT be synced with the dashboard; we will create another task about making sure that this is explained transparently in the interface.