{"version":"2.1.293","anchor":"policy-for-withholding-deny-and-allow-entries-gains-a-tried","canonical_anchor":"policy-for-withholding-deny-and-allow-entries-gains-a-tried","heading":"A stored record gains a 'tried' marker and a filter that holds back sensitive values","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/policy-for-withholding-deny-and-allow-entries-gains-a-tried","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### A stored record gains a 'tried' marker and a filter that holds back sensitive values\n\nA saved record can now mark an entry as tried, and a new filter removes values and keys that match a sensitive pattern, counting what it held back\n\n**Unclear.** What the filter treats as sensitive, and where either addition is used, is not known.\n\n**What**\n\nTwo related additions:\n\n- A stored record that holds allow entries, each with a version tag and a time, can now also mark an entry as tried. A new check is true only when an entry exists and has not been marked as tried.\n\n- A new filter walks through nested data and removes text values and field names that match a pattern, keeping a count of how many it held back.\n\n**Why**\n\nThese appear to add a way to keep certain data out of a saved record and to remember whether something has already been attempted.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}