> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/builder/builder-2021.1/case-configuration.md). # Case Configuration {% embed url="" %} You use the Case screen to create a flow of Actions which make up your business process. You can [add Actions](/enate-help/builder/builder-2021.1/case-configuration/adding-actions-to-a-case.md) in any order, either from the existing standard menu of Actions defined, or by creating brand new Actions from within the Case screen itself. The Steps for your Case are set as part of your initial set-up, and are not editable from the Case screen. Once you have added an Action, you then need to set the various attributes necessary to determine how it will act at runtime. Primarily you set ‘Who does it go to’ (i.e. which Queue, and perhaps which position), ‘When is it due’ and some further general settings. The options available for you to pick here are a [standardised list of ‘flavours’](/enate-help/builder/builder-2021.1/shared-standardised-settings-flavours.md), shared between Case, Ticket and Action configurations. If the Action involves [checklists](/enate-help/builder/builder-2021.1/case-configuration/adding-actions-to-a-case/checklists-on-actions.md), you can add two different levels of Action checklists: * **'Global' checklists** - these are added to the Action type and contain a standard checklist of activities that will be added any time this Action type is added to a Case flow. [See here for more details on how to configure global checklists](#defining-global-checklists). * **Local Checks -** these are added to Actions already in a Case flow to help support 'custom' activities that take place for that specific Action. [See here for more details on how to configure global checklists](#defining-local-checklists). As well as making Action-level settings, you also need to [set similar attributes for the overall Case](/enate-help/builder/builder-2021.1/case-configuration/case-info-section.md). Once you’ve finished setting these attributes, you can [set the Case live](/enate-help/builder/builder-2021.1/case-configuration/setting-a-case-live.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enate.net/enate-help/builder/builder-2021.1/case-configuration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.