...
Event/Action ordering
Events/Actions are now ordered with provider rules at the top and participant rules below throughout the system. The order shown in Admin will reflect the order in enrollment and in the clinician dashboard.
Provider events/actions
Messaging pool recipient (EHR pool message)
Provider email distribution list (if enabled for account)
Direct provider recipient (EHR message)
System alert (if enabled for account)
Participant events/actions
Within these types, required actions are shown first and are then ordered newest to oldest
System monitoring improvements
Resolved Defects
N/A
tele-curator
IC-2342: BE | Program level flag for cellular
IC-2358: BE | Program Events and Actions are ordered by recipient type, required, newest to oldest
IC-2359: BE | User Program Events and Actions are ordered by recipient type, required, newest to oldest
tele-actions
AIS-1041: tele-actions | Include "from_address" in write to Redis
impact-ui
AIS-1035: impact-am | New property "customer_integrations.epic.custom_headers"
AIS-552: Keycloak | Spike Quarkus | Hyperspace launch
IC-2360: FE | Clinician enrollment and dashboard events and actions are ordered by the BE
fulfillment-api
AIS-1040: fulfillment-api | refactor findExistingPatient
impact-api
AIS-1038: Impact-api | Conversations template GET with special keycloak role
AIS-950: impact-api | Grafana monitoring of webhooks feature