Coverage Maps are a great way to provide a better mapping of Reviewers or Approvers other than simply supervisor/manager/owner.
You can specify data based criteria with lots of flexibility, and the more I look into it, the more I like it. The problem is, once created and in use it cannot be deleted. (This makes a fair bit of sense, programatically).
However in real life, approver criteria change over time and needs to be updated.
A dynamic load of a file, when it is needed (So being read dynamically at run time, each Review) would allow for keeping the file up to date.
Right now, to update a coverage map in use in a Review, or Request you have to change the Review/Request to stop using the Coverage Map, delete and recreate, then change the Request/Reviews definitions for reviewers/approvers back.
by: Geoffrey C. | over a year ago | Configuration
Comments
I see why this is an issue. The CSV file is read in and stored in the DB as sort of SQL like code. So it is loaded, parsed, and then usable. Thus the file itself is only read once and then loaded. However, would be nice if there was some way to make it more dynamic so updates were easier/automatable.