> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/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/whats-new/older-versions/changes-overview-older-versions/2022.4-changes-overview/other-enhancements.md). # Other Enhancements ## US English Language Option We have also added the option to select US English (en-us) as your [system language](https://docs.enate.net/enate-help/work-manager/work-manager-2021.1/user-settings#language), in addition to British English, French, German, Spanish, Portuguese Brazilian, Romanian, Polish, Hungarian and Russian. ## Defect Modification Restriction We have added a new 'Restrict Defect Modification' setting in the [System Settings section of Builder](https://docs.enate.net/enate-help/builder/builder-2021.1/system-wide-settings/general-settings#restrict-defect-modification) which allows you to set restricted access on modifying any information in the Defects Card of Cases, Actions and Tickets. Service agents are always able to ADD a defect record and to mark one as resolved, but when this 'Restrict' setting is enabled in Builder only the agent who created the defect in the first place is able to subsequently modify or delete any of the details of that defect record. ![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2F6ySBWDJ7OKegPjRpaUd0%2Fimage.png?alt=media\&token=fbc848ef-f157-4bbf-b28f-1f49c731576a) ## Improvements to Viewing Work Items We have made improvements to working with related work items. Now you can easily see the parent Case of a work item. For example: * When a Ticket is split into multiple child Tickets, a link to access the parent Ticket will appear on all child Tickets. * When multiple work items are merged into one child item, a link to access all the parent items will appear on the child item. * When a Ticket is converted into a Case, a link to access the parent Ticket will appear on all child Case. ## 'Start New Case' Action Improvements If you choose to start the new Case (by adding a[ 'Start New Case' Action in into your Case flow in Builder](https://docs.enate.net/enate-help/builder/builder-2021.1/case-configuration/info-section/start-new-case-action-info-tab)) as an independent Case, i.e. by not ticking the Sub Case option, you can now choose to copy the defects, files (including tags), links and custom data across into the new Case. You can also choose to copy work item communications i.e. emails (including email attachments) and notes from to the new Case. Note that when choosing to copy communications, you will not only copy communications from the current Case, but also from any Actions & Sub Cases which are related to it. See [here ](https://docs.enate.net/enate-help/builder/builder-2021.1/case-configuration/info-section/start-new-case-action-info-tab)for more information. --- # 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/whats-new/older-versions/changes-overview-older-versions/2022.4-changes-overview/other-enhancements.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.