{"version":"2.1.242","anchor":"policy-helper-output-can-merge-into-a-source-s-settings-inst","canonical_anchor":"policy-helper-output-can-merge-into-a-source-s-settings-inst","heading":"Policy helper output can merge into a source's settings instead of replacing it","tier":"use","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/policy-helper-output-can-merge-into-a-source-s-settings-inst","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Policy helper output can merge into a source's settings instead of replacing it\n\nPolicy helper output can merge into a source's settings, so a failure costs less.\n\n**What**\n\nAn entry in an enterprise policy helper can declare how its produced managed settings combine with the settings of the source that delivered it: `replace`, the default and current behaviour, or `merge`, a deep merge over that source's own settings. Under merge a helper that fails costs only the keys it would have contributed, rather than the whole policy.\n\n**Details**\n\n- Under merge, helper keys win and arrays replace rather than concatenate.\n- Helper validation now also records the script's size and a flag for whether the entry merges its output.\n- Status notices include non-status errors when the helper merges.\n\n**Evidence**\n\n`\"How the helper's managedSettings compose with the settings of the source that delivered this entry: 'replace' (default) \u2014 the output is the policy; 'merge' \u2014 the output is deep-merged over that source's own settings (helper keys win, arrays replace), so a failed helper costs only the delta\"`\n\n- Area: Managed Settings\n- Names: `merge`, `replace`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}