If the Software Release didn't exist, the values were been presented wrongly.

The generation should ignore users inputs to consider itself  "closed" or not.

Regards,
Rafael Monnerat

This helps navegate and get required information for debug problems.

erp5_web_renderjs_ui shouldn't be on View anymore (since it was added a login_form on it)

Reduce the size of columns

This help on quick find essential debug information w/o require navigate so much.

   Unify the versions at all bt5.

This prevent the field be named twice if the user selects raw parameter edition. In such case, we let the erp5 validate it instead.

On most of schemas, we are not strict with the format, so allow us be flexible, include additional fields for the user don't loose values if the schema changes.

Show states and allocation information on ERP5 UI, this make easier to Cloud Administrators navigate between the objects while investigate an incident.