Release Notes | User Acceptance Testing

Add new GET Subscriptions endpoint (GET/billing/subscriptions) to support filtering by Billing Entity CaseSafe ID and Revenue Center CaseSafe ID

Query receives data from current_subscriptions and subscription_history document types

Response is grouped by Revenue Center, with each Revenue Center object including: revenue_center_casesafe_id; billing_entity_casesafe_id; name; store_number; platform; reference_id; subscriptions

Each object with subscriptions array includes: subscription_id subscription_type; name; current_status; enabled_date; disabled_date; was_active_during_period; period_overlap_days; source ; usage_stats ; sort_order_by_subscription_id

Expose POST/billing/subscriptions endpoint accepting JSON body with subscriptions array

Request body adheres to following schema for each object in subscriptions array: revenue_center_casesafe_id; billing_entity_casesafe_id; name; store_number; subscription_type; reference_id; platform; is_enabled; enabled_date; disabled_date

System determines internal subscription_id by matching input platform and subscription_type against stored Configuration Data

System identifies existing current documents by matching: billing_entity_casesafe_id (if unique) or revenue_center_casesafe_id (primary unique identifier)

If no match is found, create new document with document_type: current_subscriptions

Enable deploying service to different stacks

Create database module to access MongoDB

Configure ACL library for endpoint authorization

Configure module to access application secrets stored in AWS Parameter Store

README.md file with development instructions