EspoCRM – Open Source CRM Application
Enhancements:
Improvements:
Changes:
readOnly to be taken into account server-side https://github.com/espocrm/espocrm/issues/2375
Security:
Front-end:
All issues: https://github.com/espocrm/espocrm/milestone/136?closed=1
Fields that are set as read-only (field parameter, not dynamic logic) will be ignored in POST and PUT requests. Example: When sending a PUT request to update a read-only field, it won't update anymore.
If you are sending an enum value that is not one of the available options, it will cause a validation error.
Example 1: Sending a status 'Success' when available values are 'Planned', 'Held', 'Not Held'. Example 2: Sending a value null when the empty value is not in the list of available options. Example 3: Sending a value 'closed won' when the available value is 'Closed Won'.
Omitting an enum field value in a POST request when the field does not have a default value will cause a validation error.