Jasper ad-hoc reporting : Invoiceables microservice
Invoiceables Schema
Tables
Contains tenant_uuid column
history
limit
cost_deletion
template
cost_creation
template_limit
category
Don't contain
tenant_uuid column
schema_version
template_version
New Tables
metadata
data_sync_process_status
customer_details
Tables eligible for sync
Full
Incremental
cost_deletion (created)
cost_creation (created)
category (created, updated)
limit (created)
template (tenant_id)
template_version (created)
Payment Microservice
Single Instance Multi Tenant
Environment
CTMS
sandbox
Customer
RDS
2019.3.1
1 Event Scheduler for all customers
Questions
- When to consider testing for invoiceable customer RDS?
Ans: Only PO to be tested for customer
- Ideal configuration for testing this story?
Release branch + Ubuntu16 + Sandbox RDS + Jasper 6.3
Ans: CTMS version doesn't matter. But Jasper version should be 6.3
- All the new tables will be created in the invoiceable RDS?
Ans: under Invoiceabble_sandbox
- Master db means?
Ans: Invoiceabble_sandbox
- Why is the history table removed (to Dev)
Server
Ubuntu16
Charters
MCC-603934
Create schema SP for Invoiceables
Charter 2: Explore initial schema creation and DataSync for Invoiceables after Stored Procedure Run
Charter 1: Explore current implementation of Invoiceables and set-up data
event_scheduler=ON
Event Scheduler
MCC-603938
Create Stored Procedure for Full sync and Incremental sync for Invoiceables
Charter 3: Explore Error Conditions while performing Data Sync from Invoiceables Schema to Customer Specific Schema
Charter 4: Explore Manual Data Sync after Full/Incremental Data Sync Failure
Charter 2: Explore Invoiceables data sync through Event Trigger at Scheduled Time 2am UTC
Charter 1: Explore Invoiceables data sync for custom schedule
Charter 5: Explore Data Sync when RDS is down during the Scheduled Process
Charter 6: Explore data sync activity while in parallel adding the data for Invoiceables
Charter 7: Explore for Duplicate Entries in the Customer Specific Schema Tables after DBSYNC