Version 3.5.304 changelog (#18)

* Version 3.5.3040 changelog + changes documentation

Author: DiogoTx

docs/pages/omnia3/Authorization/omnia3_authorizationmanagement.md

@@ -19,10 +19,11 @@ In the platform authorization area (option **Management / Security**) you can ma
 
 By default, Omnia Platform has one role, named *Administration*. This role cannot be removed and it has, by default, associated the user identified on platform setup as the *Platform Administrator*. Other users can be added to this *Role*.
 
-Additionally, when a tenant is created, two new roles are automatically created:
+Additionally, when a tenant is created, three new roles are automatically created:
 
 - Administration[TenantCode]: administration role for the tenant. The user responsible for the tenant creation is automatically added to this role. Users with this role can access the Modeling area.
 - Users[TenantCode]: general users role for the tenant. Other tenant users should be added to this role, so that they have access to the tenant.
+- Connector[TenantCode]: connector users role for the tenant. The users associated with all Connectors used on the tenant must be associated to this role.
 
 If needed, new Roles can be created to grant a set of policies to a group of users.
 

docs/pages/omnia3/Introduction/omnia3_platformchangelog.md

@@ -8,6 +8,34 @@ folder: omnia3
 toc: false
 ---
 
+## [3.5.304](#3.5.304)
+
+Release Date: 2024-04-05
+
+### Implemented enhancements:
+
+- Assets are available to be used on Text Templates
+- Features Management: Swagger endpoint can now be disabled 
+- Tenants: New Role on Tenants to grant connectors adequate privileges
+- Modeling area: Alert modelers if they make a _Build & Deploy_ request with unsaved changes
+- UI Modeling: new option to navigate to attribute settings, on the attribute context menu
+- State Machines: _Enabled operations/attributes_ feature supported on nested collections
+- Calendar
+  - Performance improvements when adding multiple events on same request
+  - Export events to CSV and ICS
+
+### Issues:
+
+- WebApp: When users logs out in a tab, it doesn't reflect on other tabs
+- Forms/Dashboards: vertical scroll is always shown
+- Modals: _Close_ button label is not translated
+- Modeler: on new Tenants, homepage dashboard data is not loaded until the first build is deployed
+- Modeler: If user makes changes using _View Json_ option, it is not alerted of changes pending save when navigating
+- Queries are not properly executed if there is an attribute named _User_
+- Calendar: dates available on metadata and on _Date Range Change_ behaviour are sensitive to the computer timezone
+- Management area:  When user clicks to filter a column but does not insert data, filter is applied but not visible
+
+
 ## [3.5.282](#3.5.282)
 
 Release Date: 2024-03-15

docs/pages/omnia3/Management/omnia3_management_features.md

@@ -19,6 +19,9 @@ After changing a feature state a **platform restart is required for the operatio
 
 The following features are currently available:
 
+* **Swagger**: Swagger documentation page.
+    * When disabled, the Swagger page is not available to any user;
+
 * **UserPasswordAuthentication**: Authentication using username and password.
     * When disabled, it will be not possible to login with a username and password. If there isn't any Authentication Provider configured, it will not be possible to authenticate in the platform;
     * Make sure you have an Authentication Provider connected to your accounts before disabling this feature.

docs/pages/omnia3/Modeler/omnia3_modeler_texttemplates.md

@@ -29,17 +29,19 @@ Selecting the option _Add new_ in the list of text templates, you need to fill t
 ### How to update the Text Template's expression?
 By accessing **_User Interface / Text Templates_** in the sidebar, select one of the text templates of the list.
 
-In the **_Text Template_** page will you have four different sections:
+In the **_Text Template_** page will you have five different sections:
 * **Template**: The place to write the Text Template's expression, using the [Liquid Templating Language](https://shopify.github.io/liquid/){:target="\_blank"};
 * **Test parameters**: A JSON representation of test data, using the [available parameters](#which-are-the-available-parameters), in order to preview the template's result;
 * **Language Texts**: A JSON representation of the current user language texts;
+* **Assets**: A JSON representation of the assets available on the model;
 * **Result preview**: The result of the template transformation using the test parameters.
 
 ### Which are the available parameters?
 The following parameters are available to use when writing a text template:
 * **Data**: A set of key-value pair entries, that can be sent in the request body;
 * **Context**: A representation of the request context (similar to what is used in the C# and Javascript behaviours);
 * **Texts**: The set of texts of the language in which the request was made. Example: `Texts.Hello` to use the text "Hello" from the current user language.
+* **Assets**: The set of assets available on the current Model. Example: `Assets.CompanyLogo` to use previously defined asset "CompanyLogo"
 
 ## 3. Using Text Templates
 Text templates can be used in all scenarios where a text content is required, based on different data and/or language (for example, in the body of an e-mail notification).