# Hide 'Fill Form with AI' for a specific case type/s'

**URL:** <https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871>\
**Category:** User Experience\
**Tags:** user-experience, generative-ai, case-management\
**Created:** [October 27, 2026, 1:11pm UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871 "2026-10-27T13:11:50Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nirushiya](https://avatars.discourse-cdn.com/v4/letter/n/57b2e6/32.png) [@Nirushiya](https://forums.pega.com/u/Nirushiya)\
**Post date:** [October 27, 2026, 1:11pm UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871/1 "2026-10-27T13:11:50Z")

</div>

I need to hide the “Fill Form with AI” button for a specific case type or a specific Flow Action view. Since the related OOTB rules (e.g.pzEnableFillFormWithAI) are marked as final and cannot be overridden, what would be the recommended workaround approach to achieve this?

 ![image](https://pega1.discourse-cdn.com/pega/original/3X/a/f/affe3f9d6486bfb813116db773190fc2d29d906a.png)

---

<div class="post-metadata">

**Author:** ![Arunkumar\_Velmurugan](https://avatars.discourse-cdn.com/v4/letter/a/50afbb/32.png) [@Arunkumar\_Velmurugan](https://forums.pega.com/u/Arunkumar_Velmurugan)\
**Post date:** [October 27, 2026, 1:50pm UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871/2 "2026-10-27T13:50:59Z")

</div>

Hi,

At the moment, the “Fill Form with AI” button can’t be hidden for a specific case type or view. .

The only supported control is the EnableGenerativeAI toggle, which can be scoped by access group / persona:

1. Go to Configure \> System \> Release \> Toggles.
2. Find the row for EnableGenerativeAI and click Edit.
3. Instead of Enable toggle for all, select only the access groups that should have GenAI features, or exclude the ones that shouldn’t.

---

<div class="post-metadata">

**Author:** ![Nirushiya](https://avatars.discourse-cdn.com/v4/letter/n/57b2e6/32.png) [@Nirushiya](https://forums.pega.com/u/Nirushiya)\
**Post date:** [October 28, 2026, 6:39am UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871/3 "2026-10-28T06:39:24Z")

</div>

Thanks @Arunkumar_Velmurugan Thanks for your prompt response. Do you have any idea whether upcoming Pega versions will include a feature to enable or disable this functionality for specific case types?

---

<div class="post-metadata">

**Author:** ![AMARNATH\_Srinath](https://avatars.discourse-cdn.com/v4/letter/a/50afbb/32.png) [@AMARNATH\_Srinath](https://forums.pega.com/u/AMARNATH_Srinath)\
**Post date:** [November 2, 2026, 8:55pm UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871/4 "2026-11-02T20:55:24Z")

</div>

I think you should suggest it for a product update. this is a good feature to have and can be used in multiple places

---

<div class="post-metadata">

**Author:** ![MarcCheong](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/marccheong/32/23266_2.png) [@MarcCheong](https://forums.pega.com/u/MarcCheong)\
**Post date:** [November 3, 2026, 2:15pm UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871/5 "2026-11-03T14:15:18Z")

</div>

Actually the DSS EnableGenerativeAI is a common misconception. You can control this feature directly.

- [Disabling the Fill with sample data button](https://docs.pega.com/bundle/platform/page/platform/gen-ai/disabling-sample-data.html) outlines how to use _pzEnableFillFormWithAI_ though it is a final rule - so be curious why you want to disable it?

---

<div class="post-metadata">

**Author:** ![Nirushiya](https://avatars.discourse-cdn.com/v4/letter/n/57b2e6/32.png) [@Nirushiya](https://forums.pega.com/u/Nirushiya)\
**Post date:** [November 11, 2026, 7:51am UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871/6 "2026-11-11T07:51:52Z")

</div>

Thanks @MarcCheong ! This link helped me. As this feature is not available in the production environment and cannot be made visible through customization, I’m good with the current behavior since the requirement is not to have it in production. I had initially misunderstood its usability.

---

<div class="post-metadata">

**Author:** ![Arunkumar\_Velmurugan](https://avatars.discourse-cdn.com/v4/letter/a/50afbb/32.png) [@Arunkumar\_Velmurugan](https://forums.pega.com/u/Arunkumar_Velmurugan)\
**Post date:** [November 11, 2026, 3:23pm UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871/7 "2026-11-11T15:23:32Z")

</div>

Hi @MarcCheong,

Thanks for pointing out the documentation and correcting the EnableGenerativeAI point. You are right that the toggle is much broader than this feature.

I am curious about one thing, though. The Fill with sample data button is already disabled in production, and pzEnableFillFormWithAI is final, so the only way to change it is a private edit. As I understand it, that only affects the developer who made the edit and can’t be checked in or shared with the team.

Given that, I am struggling to see a real use case for turning it off in lower environments. Is there a scenario Pega had in mind, such as data-privacy concerns during demos, or controlling GenAI usage? Or is the private edit mainly meant as a personal preference for individual developers?  
Thanks again for your input.

---

<div class="post-metadata">

**Author:** ![MarcCheong](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/marccheong/32/23266_2.png) [@MarcCheong](https://forums.pega.com/u/MarcCheong)\
**Post date:** [November 11, 2026, 3:31pm UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871/8 "2026-11-11T15:31:24Z")

</div>

It’s a good point, this is only local change to hide the option. The option is there to accelerate testing in lower environments. No more names as “Test 1” or a mash of keyboards “sfakfjkdsjfkjds” in fields - realistic data leads to more realistic testing.

Given this isn’t marked for extension, I don’t believe it was intended to allow wholesale turning off/on.

---

<div class="post-metadata">

**Author:** ![Vaisakh.V.A](https://avatars.discourse-cdn.com/v4/letter/v/eb8c5e/32.png) [@Vaisakh.V.A](https://forums.pega.com/u/Vaisakh.V.A)\
**Post date:** [November 11, 2026, 3:50pm UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871/9 "2026-11-11T15:50:52Z")

</div>

It would be helpful to have a central option to disable this button globally across the environment, rather than requiring a private edit. Many business users will use the lower environments for User Acceptance Testing and may not be familiar with this button as they are in PROD. According to the when rule pzEnableFillFormWithAI, the button will be visible at production levels 1 through 3, including levels 1 and 3. UAT is usually performed in the Quality Assurance environment at product level 3, which raises this concern. Could this be improved in future releases?

---

<div class="post-metadata">

**Author:** ![RameshSangili](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/rameshsangili/32/23377_2.png) [@RameshSangili](https://forums.pega.com/u/RameshSangili)\
**Post date:** [November 12, 2026, 1:51am UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871/10 "2026-11-12T01:51:11Z")

</div>

I agree with @Vaisakh.V.A! Though it can be hidden in lower environments, but Private edit is not an option for end users because it’s a final rule. @MarcCheong - Any plans to control this behavior in future using Toggles to limit this functionality only for Authors access group for unit testing?

---

<div class="post-metadata">

**Author:** ![MarcCheong](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/marccheong/32/23266_2.png) [@MarcCheong](https://forums.pega.com/u/MarcCheong)\
**Post date:** [November 12, 2026, 10:10am UTC](https://forums.pega.com/t/hide-fill-form-with-ai-for-a-specific-case-type-s/13871/11 "2026-11-12T10:10:39Z")

</div>

@RameshSangili @Vaisakh.V.A I haven’t see this raised before. It’s good feedback though, so I have raised this (FDBK-150492)
