We've released two additional API routes for configuring rule-based dimensions: allowing edits to a single rule-based dimension (RBD), or even a single rules list.
Previously, with only one API route to read/write the entire configuration covering all RBDs, any change involved uploading the entire configuration of every RBD in the org.
With these new API routes, it will be easier to write a policy that can update a single RBD, or even just one month's rule list for an RBD. It no longer has to touch the config of any other RBD.
For instance, a policy might want to populate an RBD to simulate an account tag. The policy would scrape a tag's value on all the accounts across multiple vendors, and use that mapping to generate a list of rules to populate one RBD. The policy could use the new API to write this rules list for the current month, without having to touch any other month or be concerned with any other RBD.