Here's what needs to be done:

1. New table 'tool_dataprivacy_request_contexts' to hold contexts for a given request
Should have cols:

• requestid
• component
• contextid
• status (for now: pending, approved, rejected but allow for more)

2. New constants in the api class to hold the context statuses above (pending , approved, rejected etc)
3. 'New request made' adhoc task updates:

• generate the contextlist_collection
• for each contextlist:
  • store the component, context, etc in 'tool_dataprivacy_request_contexts' table
• progress the request (current code does this already)

4. At the point of approving (before scheduling the adhoc task):

• set status of all respective contexts in the table to 'approved' (may evolve to a UI control eventually)

5. 'Request approved' adhoc task updates:

• fetch list of approved contexts (those with status 'approved')
• reassemble a contextlist collection for these using approved_contextlist instead of contextlist.
• pass to manager->export()
• TODO: consider how to 'mop up' the contexts in the 'tool_dataprivacy_request_contexts' table. Do we do now or later? (scheduled task ?)

Note: This work should be based on the tool: https://github.com/moodlehq/moodle-tool_dataprivacy and on MDL-61307 work.