{% set aParams = oUIBlock.GetParams() %}
<div id="{{ oUIBlock.GetId() }}"
     class="ibo-field ibo-field-{{ oUIBlock.GetLayout() }}
        {% if oUIBlock.IsHidden() %} ibo-is-hidden{% endif %}
        {% if oUIBlock.GetAdditionalCSSClassesAsString() %} {{ oUIBlock.GetAdditionalCSSClassesAsString() }}{% endif %}"
     data-role="ibo-field"
     data-attribute-code="{{ oUIBlock.GetAttCode() }}"
     data-attribute-type="{{ oUIBlock.GetAttType() }}"
     data-attribute-label="{{ oUIBlock.GetAttLabel() }}"
		{# Note: This might not the best way to this, we might rather have some properties for this flags in te Field class. #}
		{# For the moment this just aims at restoring the metadata introduced in iTop 2.7. Refactoring the Field class with specialization for each type must be designed by all the team #}
		{# as we might want to re-use / adapt the Field classes introduced with the end-user portal #}
	 data-attribute-flag-hidden="{{ oUIBlock.IsHidden()|var_export }}"
	 data-attribute-flag-read-only="{{ oUIBlock.IsReadOnly()|var_export }}"
	 data-attribute-flag-mandatory="{{ oUIBlock.IsMandatory()|var_export }}"
	 data-attribute-flag-must-change="{{ oUIBlock.IsMustChange()|var_export }}"
	 data-attribute-flag-must-prompt="{{ oUIBlock.IsMustPrompt()|var_export }}"
	 data-attribute-flag-slave="{{ oUIBlock.IsSlave()|var_export }}"
	 data-value-raw="{{ aParams.value_raw }}"
>
	<div class="ibo-field--label">{{ oUIBlock.GetLabel()|raw }}</div>
	<div class="ibo-field--value" {% if oUIBlock.GetValueId() %}id="{{ oUIBlock.GetValueId() }}"{% endif %}>
		{% for oSubBlock in oUIBlock.GetSubBlocks() %}
			{{ render_block(oSubBlock, {aPage: aPage}) }}
		{% endfor %}
	</div>
	{% if oUIBlock.GetComments() %}
        <div class="ibo-field--comments">{{ oUIBlock.GetComments()|raw }}</div>
    {% endif %}
</div>