# Configuring a disable action for all fields on an application now disables workflow, regression?

**URL:** <https://community.nextw.com/t/configuring-a-disable-action-for-all-fields-on-an-application-now-disables-workflow-regression/1761>\
**Category:** Nextworld Platform\
**Created:** [February 26, 2026, 9:43pm UTC](https://community.nextw.com/t/configuring-a-disable-action-for-all-fields-on-an-application-now-disables-workflow-regression/1761 "2026-02-26T21:43:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jess](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/jess/32/605_2.png) [@jess](https://community.nextw.com/u/jess)\
**Post date:** [February 26, 2026, 9:43pm UTC](https://community.nextw.com/t/configuring-a-disable-action-for-all-fields-on-an-application-now-disables-workflow-regression/1761/1 "2026-02-26T21:43:40Z")

</div>

Configuring a disable action for all fields on an application now disables workflow. Previously disabling an entire app only affected fields configured for the application. Is this change in behavior expected?

This is true when selecting “all fields” on the disable action as well as leaving the selection for “Page, Row, Field or Action Name” blank.

---

<div class="post-metadata">

**Author:** ![ian.p](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/ian.p/32/427_2.png) [@ian.p](https://community.nextw.com/u/ian.p)\
**Post date:** [March 3, 2026, 2:26am UTC](https://community.nextw.com/t/configuring-a-disable-action-for-all-fields-on-an-application-now-disables-workflow-regression/1761/2 "2026-03-03T02:26:02Z")

</div>

The folks I asked internally weren’t aware of a behavior change with this, thought it must have occurred quite a long time ago. These were the additional comments:

> Workflow should be disabled if we really are getting a disable app back (which should be what we get back from that). The only time it doesn’t listen to that would be workflow approvals.