Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webui cache reset: don't invalidate new/changed documents #1245

Open
teosarca opened this issue Aug 24, 2019 · 0 comments

Comments

@teosarca
Copy link
Member

commented Aug 24, 2019

Is this a bug or feature request?

What is the current behavior?

Which are the steps to reproduce?

What is the expected or desired behavior?

Calling http://localhost:8080/rest/api/debug/cacheReset, by default, shall not invalidate new/changed Documents.

If you want to fully invalidate the cache (including new/changed documents), u shall call http://localhost:8080/rest/api/debug/cacheReset?forgetNotSavedDocuments=true

teosarca added a commit that referenced this issue Aug 24, 2019

@teosarca teosarca self-assigned this Aug 24, 2019

metas-ts added a commit to metasfresh/metasfresh that referenced this issue Sep 2, 2019
update ReleaseNotes.md
  * [#5440](#5440) Easy shipment candidate recording (Modal Overlay)
  * [#5447](#5447) Optionally include C_Location changes in parent record's changelog
  * [#5457](#5457) MaterialTracking - Support regular PP_Orders with heterogenous components
  * [#1245](metasfresh/metasfresh-webui-api#1245) webui cache reset: don't invalidate new/changed documents
  * [#5380](#5380) Fix timezone issues
  * [#1248](metasfresh/metasfresh-webui-api#1248) webui: don't apply role permissions when loading layout fields
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.