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

Record history not being recorded if validation on metadata save is also enabled #8288

Open
alexarobu opened this issue Jul 31, 2024 · 1 comment

Comments

@alexarobu
Copy link
Contributor

alexarobu commented Jul 31, 2024

Describe the bug
We noticed that if you enable from the settings both Force validation on metadata save and Enable record history recording are enabled, then the record history is not recorded.

To Reproduce
Steps to reproduce the behaviour:

  1. Navigate to settings and tick the checkbox next to Enable record history recording (and save the settings changes)
  2. Create a new record (or edit an existing record)
  3. See the change being recorded in Admin console > Statistics and status > Versioning
  4. Navigate to settings and tick the checkbox next to Force validation on metadata save (and save the settings changes)
  5. Create a new record (or edit an existing record) - can be the same as before, but make a new change to it
  6. See the change NOT being recorded anymore in Admin console > Statistics and status > Versioning

Expected behaviour
We expect these settings to work in parallel, so a user should be able to enable the validation on save and also be able to keep track of the record changes.

@alexarobu
Copy link
Contributor Author

Just to add, I tested this in 4.2.5 and 4.2.9 as they are the versions we deploy to. This occurs in both versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant