Version 3.5.392 changelog (#32)

* Version 3.5.392 changelog

* Added filter fix to changelog

* Increment version

docs/_data/sidebars/omnia3_sidebar.yml

@@ -303,6 +303,10 @@ entries:
             url: /omnia3_application_menu_favorites.html
             output: web, pdf
 
+          - title: Export list data
+            url: /omnia3_application_data_export.html
+            output: web, pdf
+
       - title: Authorization
         output: web, pdf
         folderitems:

docs/pages/omnia3/Application/omnia3_application_data_export.md

@@ -0,0 +1,28 @@
+---
+title: OMNIA 3 Data Export
+keywords: omnia3
+summary: "OMNIA 3 Data Export"
+sidebar: omnia3_sidebar
+permalink: omnia3_application_data_export.html
+folder: omnia3
+---
+
+## 1. Introduction
+
+On tenants, the data available on lists can be exported to a CSV file.
+
+## 2. How to export list data?
+
+To export list data you must select the option on the bottom right side of the list, next to the pagination options.
+
+Please note that the option availability is configurable, so it might not be available on all lists.
+
+## 2. How to configure the list export parameters?
+
+When the user is exporting for the first time on a new machine/browser, a prompt is shown so that the user sets the following parameters value:
+
+- Column Delimiter: the character used to delimiter the CSV columns. Default value is comma (',')
+- Decimal separator: the character used to separate the integer from the fractional part for a decimal field. Default value is period/dot ('.')
+- Date format: the format for date fields to be exported. Default value is dd/MM/yyyy
+
+The configuration is saved on the browser local storage, and it can be changed on the _Change CSV settings_ option on the top right side _user_ menu.

docs/pages/omnia3/Application/omnia3_application_notifications_and_operations.md

@@ -17,7 +17,7 @@ On the top right corner of the screen, you will see a small bell with a number n
 
 In order for this area to have entries, you'll need to have an application that has **After Save** behaviours modeled. When a user saves an entity that has an [After Save behaviour](omnia3_modeler_behaviours.html), the contents of this entity will be saved to an **outbox**, a platform-wide 'staging area' for requests to be processed. Gradually, all of these will be sent to be executed and, if successful, a **success** message will pop up on the users' screen, in the notification area.
 
-If the After Save fails, the after save execution will be marked as a failure, removed from the outbox, and a **failure** notification will be sent. An error, defined by the modeler on behaviour code is shown, and a *Retry* option is available, so that operation can be retried after the error cause is fixed.
+If the After Save fails, the after save execution will be marked as a failure, removed from the outbox, and a **failure** notification will be sent. An error, defined by the modeler on behaviour code is shown, and a _Retry_ option is available, so that operation can be retried after the error cause is fixed.
 
 ## 3. Operations
 

docs/pages/omnia3/Connector/omnia3_connector_install.md

@@ -34,7 +34,7 @@ After you have downloaded the connector (see our [Downloads page](omnia3_downloa
 To run it, you should just do `Omnia.Connector.Windows.exe` (in cmd) or `./Omnia.Connector.Windows.exe` (in powershell) from the folder you extracted it to. In order to install the Windows service, add `install` to the end of that line. To uninstall it, add `uninstall`. In both of these scenarios, ensure you are running as an administrator.
 
 **NOTE:** Depending on the Windows policies, the downloaded _zip_ file containing the Omnia Connector might be locked.
-To ensure the connector will be properly installed, before unzipping right click on the file and view its properties. If the _Unblock_ button is present, click on it and apply the changes so that the file is properly unblocked.
+To ensure the connector will be properly installed, before unzipping right click on the file and open its properties. If the _Unblock_ button is present, click on it and apply the changes so that the file is properly unblocked.
 
 ## 4. Manage connector
 

docs/pages/omnia3/Connector/omnia3_connector_introduction.md

@@ -7,44 +7,49 @@ permalink: omnia3_connector_introduction.html
 folder: omnia3
 ---
 
-
 ## 1. Introduction
 
-The **OMNIA Connector** is the software that the OMNIA Platform uses to communicate with the customer's servers in order to execute external behaviours. 
+The **OMNIA Connector** is the software that the OMNIA Platform uses to communicate with the customer's servers in order to execute external behaviours.
 
 ![Connector architecture](images\connector.png){: .image-center}
 
 ## 2. Communication
-The Connector initiates a communication socket with the Platform servers. During the connection the connector is authenticated in the platform using the configured Id and Secret. 
+
+The Connector initiates a communication socket with the Platform servers. During the connection the connector is authenticated in the platform using the configured Id and Secret.
 
 This way, the connector is treated by the security system as a user, enabling the platform administrator to manage the privileges to that connector user.
 
 Besides the authorization part, is highly recommended to configure the [OMNIA Platform to work with HTTPS](omnia3_deploymenttutorial.html#53-configure-https), in order to use a secure communication channel.
 
 ## 3. How behaviours works
+
 The **OMNIA Connector** shares the same behaviours engine as the **OMNIA Platform**. When the connector starts it'll launch a **Behaviours Manager** process. The manager is responsible for locating and launching the required **Behaviours Servers**. The server, aside from the execution of the desired behaviours, is also responsible for their compilation.
 
 ![Connector architecture](images\connector_arch.jpg){: .image-center}
 
 The manager will launch a new server process when configurable maximal number of builds is reached. This new process will co-exist with the other server processes in the connector.
 
 ## 4. Debugging behaviours on the connector
+
 By default, the behaviours the connector executes will be downloaded to the temporary folder of your system, under an "omnia" folder, i.e., `%temp%/omnia` on Windows, and organized inside that folder by their tenant/environment codes.
 
-Following the instructions on [this page]( omnia3_modeler_developingbehaviours.html), you will be able to develop and/or test any behaviours that are meant to run connector-side. Our recommendation is to, if possible, install Visual Studio on the same machine that is running the connector, so you can reference all the same DLLs and local files that are being used in the behaviours.
+Following the instructions on [this page](omnia3_modeler_developingbehaviours.html), you will be able to develop and/or test any behaviours that are meant to run connector-side. Our recommendation is to, if possible, install Visual Studio on the same machine that is running the connector, so you can reference all the same DLLs and local files that are being used in the behaviours.
 
 ## 5. Connectivity
-Once the connector is running, the connection between it and the server will be kept active without the user having to do anything. 
+
+Once the connector is running, the connection between it and the server will be kept active without the user having to do anything.
 
 However, there are scenarios where it is necessary to perform manual maintenance on the installation, namely, when disconnections occur, or the connector is failing to start its behaviour executing components.
 
 ### 5.1. Start policy
-If the connector cannot establish a connection when launching, it will retry that connection for up to one minute before crashing. 
+
+If the connector cannot establish a connection when launching, it will retry that connection for up to one minute before crashing.
 
 ### 5.2. Disconnection retry policy
-If the connector is running and a disconnection is detected, it will begin a process of **exponential backoff**. 
 
-This means that the connector will keep attempting to re-establish the connection, with more and more space between attempts. 
+If the connector is running and a disconnection is detected, it will begin a process of **exponential backoff**.
+
+This means that the connector will keep attempting to re-establish the connection, with more and more space between attempts.
 
 By default, if after **24 hours** connection is not established, we assume there is a _permanent_ issue with the connection and will stop trying to reconnect.
 
@@ -53,15 +58,19 @@ If the default reconnection time is not adequate, [it can be configured](omnia3_
 This will lead to manual intervention being necessary.
 
 ### 5.3 Single connection per Connector
-Only one connector can be connected using the same pair of configurations (client and secret). For this reason, if you start a new connector with the same configuration, the platform will request the previously active connector to shut down. 
 
-In this case, you will see a warning in the new connector saying *"Another connector or connection has been disconnected."*. This message can also mean that the connector for some reason (network instability for example) needed to start a new connection with the server.
+Only one connector can be connected using the same pair of configurations (client and secret). For this reason, if you start a new connector with the same configuration, the platform will request the previously active connector to shut down.
+
+In this case, you will see a warning in the new connector saying _"Another connector or connection has been disconnected."_. This message can also mean that the connector for some reason (network instability for example) needed to start a new connection with the server.
+
+Additionally, on the same machine the connector can be run as either a Windows service or console mode. If the connector is already running as a service and is started on console mode, the following message is shown: _"The omniaplatform_connector service is running and must be stopped before running via the console"_.
+If it is intended to run on console mode, the service must be stopped.
 
 ## 6. Requirements
 
-* Internet access
-    - Access to the OMNIA Platform address (Port 443 or 80 if not running under HTTPS).
-* .NET Framework 4.7.2
-* Compatible Windows version:
-    - Windows Server 2012 or higher
-    - Windows 8.1+ or 10 (Anniversary Update and beyond).
+- Internet access
+  - Access to the OMNIA Platform address (Port 443 or 80 if not running under HTTPS).
+- .NET Framework 4.7.2
+- Compatible Windows version:
+  - Windows Server 2012 or higher
+  - Windows 8.1+ or 10 (Anniversary Update and beyond).

docs/pages/omnia3/Introduction/omnia3_platformchangelog.md

@@ -8,6 +8,37 @@ folder: omnia3
 toc: false
 ---
 
+## [3.5.393](#3.5.393)
+
+Release Date: 2025-02-17
+
+### Implemented enhancements:
+
+- Lists: precision is now configurable on decimal columns
+- Authorization Roles: role description can now be configured
+- Improved error messages when disabled attributes are changed on a collection
+- Editable Grid: added a label when there are no records and they cannot be added
+- Validate required attributes and other rules when data is inserted on a modal (Grids on mobile devices and Calendars)
+- CSV Export settings are now configurable after selection
+
+### Issues:
+
+- Authorization Roles: it is possible to add users to roles without any privilege
+- Authentication providers: LinkedIn authentication provider not working
+- Authentication providers: Error on authenticating when there is more than one active OpenID Connect provider
+- Modeler: It is possible to define a collection with minimum and maximum as 1
+- Modeler: error when removing entries from an automatically generated menu
+- Modeler: when an entity is created with a different case of a removed one, an error occurs
+- Modeler: Events and Commitments should not be available to be added as a _reference_ attribute
+- Modeler: It is possible to drop unsupported attributes on a Tab Control
+- Modeler: Filters by integer or boolean columns on lists not working
+- Modeler: On Query list, filter on _Definition Type_ column are case sensitive
+- Asynchronous operations for a tenant are retried after the tenant is removed
+- State Machines: Attributes and operations can be enabled multiple times
+- Enumerations: Tooltip shows the value instead of the description
+- Calendar: When select range is active and a new entry is added, it changes existing records
+- UI: When a temporary fails to update, the user cannot proceed with data insertion
+
 ## [3.5.362](#3.5.362)
 
 Release Date: 2025-01-08