-
Notifications
You must be signed in to change notification settings - Fork 35
Disable quick actions button while running the action (v2) #933
Comments
Disable quick actions button while running the action (v2) #933
[#905](metasfresh/metasfresh-webui-frontend-legacy#905) Add/ Remove KPI Widget functionality for User Dashboard [#486](metasfresh/metasfresh-webui-api-legacy#486) dashboard: support "position" when PATCHing a dashboard item [#482](metasfresh/metasfresh-webui-api-legacy#482) No Role Error for new User [#481](metasfresh/metasfresh-webui-api-legacy#481) Sticky empty Filter in modal overlay. [#485](metasfresh/metasfresh-webui-api-legacy#485) backend: refactor sticky filters [#949](metasfresh/metasfresh-webui-frontend-legacy#949) Board: adding a card as last is not user friendly] [#469](metasfresh/metasfresh-webui-api-legacy#469) Picking prototype (v2) [#923](metasfresh/metasfresh-webui-frontend-legacy#923) Packageables window: up/down arrows are working weird [#945](metasfresh/metasfresh-webui-frontend-legacy#945) dashboard: react to websocket notifications [#933](metasfresh/metasfresh-webui-frontend-legacy#933) Disable quick actions button while running the action (v2) me.45
Results of IT Tested on mf15releasetest webui The quick actions are disabled while the process is running: OK I found a detail problem for which I created a followup: #973 |
reopened because @metas-ts reverted it |
My observations not directly related to changes made for this story:
|
rolled out on our IT server for checking prior to integration |
Fix Disable quick actions button while running the action #933
(cherry picked from commit f576631) solved Conflicts: src/components/app/QuickActions.js
cherry-picked to the |
@metas-ts is this still open? |
Hi @wiadev, |
Tested. Works as required. Done/ Closing. |
Type of issue
Bug
Current behavior
When pressing a quick action the process is started right away.
But the quick action button is green even though the process did not finish.
Expected behavior
The quick action button shall always be disabled while the process is running.
After the process was executed, successfully or with ANY error/exception the quick action button shall be unlocked and it's state shall be reevaluated (i.e. ask API about quick actions).
This is just a shade of this cinquecento #500 :)
The text was updated successfully, but these errors were encountered: