Please enable JavaScript.
Coggle requires JavaScript to display documents.
Temporary Cache for each Document Controller Call Test Approach https…
Temporary Cache for each Document Controller Call Test Approach https://jira.mdsol.com/browse/MCC-461067
Problem:
Each placeholder currently makes multiple calls to Plinth for Team Memberships - this affects performance by causing delays and timeouts especially in Production.
Test Plan
Setup
Templates
Multiple placeholders
-
-
- [issues_and_actions]
- [visit_conduct_method]
- [issues_and_actions] :star:
- [monitored_saes]
- [combined_action_items] :star:
- [visit_assignee_name]
- [visit_assignee_phone_number]
- [principal_investigator_name]
- [next_visit_date]
- [visit_dates_list]
- [todays_date] ls"
- [visit_assignee_email_address]
- [site_name]
- [main_address]
- study_environment_site_number]
16 [protocol_id] SUCCESS
-
-
-
Checks
Single request to plinth per transaction (any request placeholders make to plinth for team memberships)
-
-
-
Solution:
Template Editor can make repeated identical calls while performing an action:
Examples are: Calls to Visit while resolving a document, Calls to Plinth while commenting a document.
Acceptance Criteria:
Sumologic will Indicate that a call is being resued from the CACHE object instead of making a NEW call to the endpoint.
Sumologic will indicate that the cache is cleared AFTER the Controller action has been performed.
Focus needs to be put only on those network intensive calls, (Plinth Visit etc) in order to gain performance benefits under load.
-
-
-
-