fix: call setDefaultValues also on update

[gramian]

What does this PR do?

This change fixes the behavior that default property values are not set on record updates. Now for mandatory properties the default is set anew on updates given the propertiy is null.

Motivation

Originally the problem arose when property fields with timestamps that were created as default values caused exceptions when the associated records were updated and the timestamp field was absent in the updated record (as it was expected to be set with the default value).

Related issues

#1814

Additional Notes

Could there be any corner cases where this causes problems?

Checklist

• I have run the build using mvn clean package command
• My unit tests cover both failure and success scenarios

[gramian]

I modified the change so only mandatory properties are set to defaults on updates, see #1814 (comment) .

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00%	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (f44ecba)	68799	43738	63.57%
Head commit (f44ecba)	68799 (+0)	43738 (+0)	63.57% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#1830)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}