Custom Investment type object having a Date field, that is made as a required field through a Blueprint Rule. Also this Date Field is configured to default to the present system date, from Clarity Studio. On MUX, when an instance of this Custom Investment is thus created, on the Create Modal Screen, if this Date Field is Blank, even being as a required field, the Investment record gets created with a blank value in the Date Field.
Steps to Reproduce:
Expected Results: Application should not allow creation of the record, since Approval Date field being a required field, has blank value
Actual Results: The investment record gets created with a blank value in the Approval Date field
DE77961 is fixed in version 16.2.1
The other scenario of the issue with a rule based required date field, is that when this date field has a value in it:
Create an investment record and mark it as a Template. Note, that the rule based date field: Approval Date, will have the preset date defaulted, as per the Step: 5, above:
Click on New From Template button and choose the above template. On the resulting Create modal screen, the Approval Date field, defaults to the system date and hence has value:
Clear the value of Approval Date. Then, edit any other remaining fields on the Create Modal Screen. Note that the moment any other field on the modal screen, is edited the Create Button gets enabled and the record could be created, disregarding the Approval Date field being blank
The Investment record gets created, however on the details screen, the Approval Date field has the defaulted present date, even if the value was cleared out on the Modal Create screen. So it seems like the date field is internally still referencing the defaulted value, even if the field's value is being cleared in the Modal Create Screen.