Manage ITP checklist updates with injected client
Use an injected client to ensure all ITP checklist updates are routed through your own service layer while keeping read behaviour unchanged.
This guide is designed for project manager.
Steps
Step 1: Open the ITP checklist for a component
Navigate to the ITP checklist for the relevant component so you can review current template details and item statuses fetched from the standard API.

Step 2: Configure the checklist to use your injected client
Ensure your environment or integration is set so that the ITP checklist is initialised with your injected write client, allowing all write actions to pass through your chosen service.

Step 3: Update an ITP item status
Change the status of an individual ITP item, confirming that the update is processed via your injected client while read operations still use the generated API client.

Step 4: Mark the component as complete
Complete the component in the checklist, ensuring the completion write is handled by your injected client without altering how checklist data is read.

Step 5: Reopen a component for defects
Reopen a completed component to capture defects, verifying that the reopen action is routed through your injected client while the checklist continues to display data from the read-only API.

Step 6: Manage hold points within the checklist
Trigger or clear hold points in the inline workflow, confirming that each hold-point change is sent via your injected client and that the generated write methods remain unused.

Last updated: 2026-08-12