New release v0.7.8: Added basic Traffic validation: New validation rules for Traffic section and make some changes related to that component. It's worth noting that some changes have been made for validation to run same way for both client and server sides regarding sample_rate . So far this field was being transformed before sending it to the backend so its structure was different in the client and in the server. But validation must run both sides indistinctly. So that transformation has been delayed to do it in the backend just when preparing data to be saved in the database. That way, sample_rate structure is the same during the validation process (for both client and server) and we transform that field properly before saving it in the database. Now wiki and traffic/sample_rate are validated according to some validation rules that are included in the first AC of T396059 - Inline Server Validation for Wiki: "No wiki has been selected" when the field is empty - Inline Server Validation for Traffic (%): "No traffic assigned" when there is no value in that field - Inline Client Validation for Traffic (%) / Sample Rate: "Enter a value between 0 and 100" or "Enter a value between 0 and 1" depending when registering an experiment or an instrument - Default wiki row has been removed for experiments. By default one row appears but wiki is fully configurable and cannot be removed. For instruments, a default wiki row is still appearing: T396201 - Negative values are now validated properly: T384107 - Add 'performer_is_temp' to contextual attributes table - Limit instruments endpoint to active instruments