{"version":"2.1.219","anchor":"workflow-size-guideline-gets-a-default-and-a-policy-override","canonical_anchor":"workflow-size-guideline-gets-a-default-and-a-policy-override","heading":"Workflow size guideline gets a default and a policy override","tier":"use","area":"Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/workflow-size-guideline-gets-a-default-and-a-policy-override","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Workflow size guideline gets a default and a policy override\n\nWorkflow size now defaults to medium, and an admin policy setting overrides whatever you chose.\n\n**What**\n\nThe workflow size guideline now resolves to `medium` when nothing is configured, and a value set in policy settings takes precedence over the user's own setting.\n\n**Details**\n\n- The resolver returns `{ size, isDefault }`.\n- Prompts distinguish the two cases: \"This session has the default workflow size guideline:\" versus \"A workflow size guideline is configured for this session:\".\n- The \/config pointer is only shown when the value is the default.\n- The unrestricted notice was reworded to \"Workflow size is now unrestricted \u2014 no size guideline applies.\" and no longer attributes the change to the user.\n\n**Evidence**\n\n`Workflow size is now unrestricted \u2014 no size guideline applies.`\n\n- Area: Configuration\n- Names: `\/config`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 0\/5"}