{"version":"2.1.267","anchor":"new-workflow-keyword-trigger-setting-tracked-via-a-settings","canonical_anchor":"new-workflow-keyword-trigger-setting-tracked-via-a-settings","heading":"New workflow keyword-trigger setting tracked via a settings change-log abstraction","tier":"use","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-workflow-keyword-trigger-setting-tracked-via-a-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New workflow keyword-trigger setting tracked via a settings change-log abstraction\n\nSettings toggles like verbose mode and a new keyword-trigger option now go through a unified change-log system\n\n**Unclear.** The finding doesn't say what `ultracodeKeywordTrigger` does or how a user would use it.\n\n**What**\n\nSeveral settings toggles, including `verbose`, `permissionMode`, Fast mode, Default view, and a new `ultracodeKeywordTrigger` setting, are now updated through one shared change-log object with `record`, `toggle`, and `clear` methods, instead of each being updated with its own separate code.\n\n**Why**\n\nThis is mainly an internal cleanup that makes settings changes more consistent and easier to track, and it surfaces a new `ultracodeKeywordTrigger` setting related to triggering workflows by keyword.\n\n- Area: Settings\n- Names: `ultracodeKeywordTrigger`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}