Skip to end of metadata
Go to start of metadata


If you use the learning and evaluations multilingual feature, click here and check out the changes before applying this update to your platform.

Check out below the new features available in the fluig 1.6.1 update:


Service Levels Agreements (SLA) and many new features!

Transparency and security are fundamental aspects for a good relationship between customers and service providers in any kind of business process. For clarification purposes on both sides, Service Level Agreements (SLA) help define the services to be provided and the deadlines to be met, thus eliminating possible misunderstandings between customers and service providers. In this update, fluig is bringing to you the concept of Service Level Management - which is a set of features that will assist you in all the steps for obtaining the highest performance within your company. These features will be available from the planning stage of deadlines to management dashboard installation. All that is now at your fingertips, just a few clicks away.

Dashboards and Charts to manage requests

With the new fluig dashboards, management is particularly noticeable in every process of your business. With the new requests chart, you can create sophisticated management dashboards that are available for those that need them, wherever they need them, displaying information on the health of their processes on their cell phone pages and even in management panels.

New fields to control deadlines in your task central

We have created new fields to help you control your requests on a daily basis in order to make it easier for you to perform and control tasks in an orderly manner, allowing you to create a list of priorities where you are carrying out your work. Here are the fields:

  • Request Deadline - It shows the date and time expected to end the request as a whole.
  • Execution Time - It shows the time in hours during which the request remains open.
  • Request Status - It indicates the status of the request in relation to the deadline, indicating if it is “Expired”, “Warned” or “Within the deadline”.

Note that these fields will only be available after the filter has been created with the fields configured, using the new "Process Filters" feature. More details can be found here in the documentation.

By using the “Request Status” field as a filter, you can filter requests and sort them in a way that allows you to perform the requests orderly, based on the priority level.

Favorite filters - Set a default filter for each process tab in your central

Setting a default filter for your process tabs will bring more efficiency to your everyday life. Whenever you access the “Due tasks” tab in the Task Central, for example, it will be pre-selected with the filter that is best suited to your activities, displaying the fields and requests that are most relevant to you.

News: Process Filter Center

Create and manage filters for you and your team quickly and efficiently. The new filter center will allow you to create or keep task central filters more organized, making it easier to improve continuously. The new filter sharing features will bring much more efficiency to filter deployment in different work groups in your organization.

Learn more

For more information, also check out our documentation on Process filters.

New notification tasks

When you set deadlines for your request, you can also choose to receive notifications when a particular request has expired or is late. You can receive these notifications via Notification Center, e-mail or fluig Mobile.

Web process activities now have a new look!

No matter the complexity of your processes, now you can reset your deadlines and other process management information over the web easily and efficiently. In addition, you can now set the form fields to be used in the Task Central filters. 


Task Central 6x faster

With significant improvement in performance, Task Central has become much more efficient, making it much easier to monitor tasks. Performance gains can reach up to 600%, depending on the assignment mechanism settings.

New SLA APIs available

New public API methods allow process information to be taken to other systems more easily. Now we can provide you with information about status, execution hours and deadlines so that you do not have to perform any extra calculation for that. For more information on API, access fluig API and, to access it, go to


Learn about the new learning and evaluations menu!

In order to improve usability, streamline everyday tasks and make LMS even more beautiful, we are launching the new learning and evaluations menu. Now you can have access to some features directly from the main menu, which makes your day-to-day quicker and more fluid. Check it out!

Cool! But, where do I find the catalogs now?

Don’t worry, it’s super easy to find them. Look:

  1. The learning catalogs, which previously belonged to the Catalog tab, now are items in the Learning menu. You can find them in:
    • LearningCourse subjects and classes;
    • LearningTracks and training.

  2. The questions catalog is available in:
    • EvaluationsTopics and questions.

And there is more!

There is also a new feature in the Learning menu! Now, the Certificates feature, which belonged to the Control Panel, has been moved to the Manage item in the Learning menu. Click here and check out the news!

Tracks and training catalog now has a new look

The new tracks and training catalog is ready to make it much easier, more efficient and convenient to manage these items, contributing to making your day-to-day much more fluid, and it has a much more beautiful and intuitive look. Please visit and check it out!

Don’t worry!

The information and features available in the previous catalog are also in the new catalog.

Go to to check out more information on the tracks and training catalog and its features.

View tracks and training courses that have been archived or are under conclusion in the catalog

Would you like the tracks or training courses whose status are “Archived” or “Under conclusion” to continue being displayed in the catalog? Well, now that is possible!

The new options Allow viewing archived training courses and tracks and Allow viewing training courses and tracks under conclusion from the Learning settings feature in the Control Panel allow you to set whether or not these items should continue being displayed in the catalog to those who have, at least, reading permission on them.

More modern skill management

Managing the skills that the students can acquire when they complete a learning item – a track, training course or subject – is more beautiful and modern. Register the skills, engage your team to improve their knowledge and acquire it.

Here is a tip!

You can display the skills acquired by your team by using the widgets Achievements and Achievements details on your pages.

    Registering skills

    Viewing skills

    Displaying skills on a page

    Create custom certificates much more easily

    Managing certificates that are related to training courses, tracks and subjects has been redesigned to make the experience much more enjoyable. Now it is more convenient and easier to register and configure certificate content: you can do everything in the same place!

    Stay tuned for more info!

    In addition to all this, the Certificates feature has been moved to a new location in the menu. Now you can find it in Learning → Manage → Certificates. Much more convenient, isn’t it?

    And the tokens? Where are they?

    To improve viewing of all the tokens that you can use in certificates, we have created a specific page for them.

    And the best part is: there are new tokens available for use! Discipline coordinator is one of them: ${discipline.coordinator.fullName}.

    Visit the page Tokens in certificates and check out the rest!

      New location for the Certificates feature in the menu

      Registering certificates

      Viewing certificates

      Certificate issued

      More usability managing evaluations and their questions

      We have remodeled the creation and editing of evaluations and question blocks in order to provide the person responsible for the evaluations of the company with more usability and convenience. The pages are visually more beautiful and intuitive. In addition, we have also improved topics and questions catalog browsing experience, allowing you to perform actions more quickly and with fewer clicks. Take a look!

      Learn more!

      Check out the full documentation on how to use it in Evaluations, Blocks and Topics and questions.

        Registering evaluations

        Registering blocks

        Topics and Questions catalog

        Pick up the evaluation where you left off

        Now you can define how to count completion time when the student starts an evaluation and, for some reason, closes the evaluation window. When the new option Allow resuming from the last point in the registration of evaluations is checked, it allows the student to pick up where they left off, i.e., the time during which it remained closed will not be deducted from the remaining time to finish the evaluation.


        The maximum time to complete an evaluation is 60 minutes and the new option is checked. A student spent 20 minutes taking the examination and closed it. Two hours later, he picked up where he left off. In this case, the remaining time that he will have to finish the evaluation will be 40 minutes.

        Stay tuned for more info!

        When that option is not checked, evaluation time continues to run even if the evaluation execution window is closed.

        For more details, see Creating evaluations.

        Simplified multi-language

        The multi-language feature available in the registration of learning and evaluation items has been simplified. The great motivator for this change is the increased platform performance, mainly in the catalogs (tracks and training, classes and disciplines, and topics and questions). Now the availability of the translated content follows the same concept as the other cards on the platform.

        Understand the changes:

        To make this change clearer, we have created documentation containing all the details for you to understand everything you need. See: What are the changes in multi-language from the 1.6.1 update?


        Office Store, here we are! 

        Now fluig is also available in the Office Store, with fluig Connect for Outlook. With it, you can post e-mails quickly through Office 365 and its Outlook for Mac (Yes, you asked and we listened!)

        Check out fluig Connect for Outlook:

        Fluig Connect for Outlook is compatible with Outlook 2013 or higher, Outlook 2016 for Mac, Outlook on the Web. For more information, click here.

        Visit Office Store and download it now:

        Soon we’ll release more features, stay tuned!  

        Update the field “Research” on your forms! 

        On your forms, do you use the “Search” field (also known as “Zoom”), where a popup opens displaying the information you want? Update your form and replace that popup with our new zoom component, which now includes all of the features you used in the popup! Here you find the full documentation, with the new available options:

          • maximumSelectionLength selectable record limit, allowing more than one value.

          • placeholder - a text in the zoom field that can be used for instruction, for example “Enter your city”

        Define people responsible by form field on the web generator! 

        Now, on the form generator, when using the “Search” component, you can define the value field to be saved - in addition to the traditional “Description” field.  

        Thus, you can create a group from where to select the person responsible for a process activity on fluig. All that just a few clicks away ... Cool, right? 

        A new review or a new version? It is up to you! 

        Now it is much easier to restore a document review: you can choose whether to create a new version (2.000, 3.000) or a new review (2.001, 2.002)!  

        In addition, you can detail the reason to restore a version, to enrich the document history. 

        Native Digital Signature 

        You no longer need to worry about installing or updating the fluig Digital Signature component! In fluig 1.6.1, the Digital Signature mashup is native, making the update and installation process easier!

        If you already use Digital Signature, relax. After updating it to fluig 1.6.1, you do not need to do anything else - you will have the latest version available. If you do not use Digital Signature on fluig yet, visit fluig Store and order it today!

        WebDAV and modern browsers! 

        To keep up with the evolution of WebDAV (the protocol that you use to edit documents without downloading the file) we did some updates for you to have a good experience, regardless of the browser you use. 


        Create richer posts using the multiple images feature

        To make image sharing quicker and create richer posts in communities, from now on you can add multiple images to the same post. Images can be selected from the user’s workstation and displayed in carousel format in order to enhance the look of their posts.

        For now, displaying and posting multiple images is only available on the web. The fluig Mobile app only displays the first image posted, but don’t worry! Soon we will have news about this feature in our mobile application. (wink)

        Learn how to enable image posting in a community through the documentation available at fluig Help! 

        Conversations a click away with the new fluig Messaging shortcuts

        To make communication in your company more dynamic, fluig now has shortcuts to start a fluig Messaging conversation directly from a contact’s profile or business card. If you keep the mouse cursor over the name of the user who you want to talk to, the business card will be displayed with the new Message button. Just click on it to be directed to the conversation on fluig Messaging.

        In addition, the Message button was also added to the user profile page, offering yet another way for you to communicate with your contacts on the platform.

          Start a conversation using the Message button in the business card.

          Start a conversation using the Message button in the user profile.


          Fluig installation in modules: Check out this new feature! 

          Thinking about different types of environments and their size, we offer modularized platform installation. Now you can install only the Indexation Server and/or RealTime service on different servers quickly, executing commands in character mode. 
          For more details on the procedure, see the documentation
          fluig Installation Guide


          If you use fluig Analytics, we have an important message for you!


          To help identify problems and provide more efficient services, we have sent the new data from your environment to the fluig Analytics service. Everything continues working as usual, however, as of 3/312018, submissions to fluig Analytics using the previous format will no longer be accepted. Ensure that there is a platform update schedule by that date for a 1.6.1 update or higher so everything continues working smoothly.

          Documentation News

          • The Dataset Synchronization documentation has been updated with information about the TEXT field type, developed for environments that use Oracle databases.
          • Having trouble connecting to the license server? See the documentation on emergency files and learn how to apply an emergency key on the platform.
          • Did you create a user on fluig using a wrong e-mail and the environment is integrated with fluig Identity? Check out this  FAQ to learn how to fix this situation.
          • See how to use the new onlyActiveUsers parameter to list only active users when using the User selection component on a page or widget.



          • When the user viewed a document, a message was created, stating that the document had been modified externally, but it was exactly how the user had posted it. Resolved an issue so that the documents that have their controlled copy properties updated are correctly displayed.
          • Using the mobile data network, when trying to add files to the process, it displayed an incorrect message. Improved the message to make it clearer and more user friendly.
          • The title property that displays whether the document is expired or not was pointing to a nonexistent property. Update it to version 1.6.0 or higher to fix the situation.

          • When a document was deleted, no message was displayed confirming the action. Added confirmation so that, when the user deletes a document, they do not delete documents by accident.
          • When updating to fluig 1.5.13, forms always searched for the first version attachments. We made changes for fluig to search for the correct form attachment version among the updates 
          • When trying to print protocol documents with controlled printing, they were not printed. Fixed a bug to print controlled copy documents correctly.
          • Inconsistency in fluig 1.6.0 when trying to print office controlled copy documents. Adjustments made so that when trying to print documents, they are printed correctly.

          • External Jar condition is that only “documents” containing keywords are exported from ECM 3.0 to fluig. Adjustment made for form records, forms or any other type of document to have their keywords exported.

          • When loading a form containing a zoom field, it is very slow because the number of logs displayed on the console is large. Adjustment made to delete the logs from the console.

          • Fixed main list creation options, because some options did not work in folders located in the ECM root. 

          • Inconsistency in viewing the form when updating it in ad hoc as a subprocess, because it had the wrong separator. Base updated in order to fix the situation. 
          • Adjustment made to fix approval routine, because users who have once been but are no longer approvers were still able to approve documents.  
          • Adjustment made so that the approval notification is only sent when the document is in fact approved and not when it is submitted for approval.
          • Fixed an issue in checkout comments, because when you sent a document to checkout and entered a comment, it was not displayed in the document properties.
          • Adjustments made since setValue in the validateCustomMetadata event was not defining the values as expected.
          • Deleted hibernate_sequence table that was created in error, and adjustment made so that collaborative editing via Google drive works properly.
          • Resolved an issue so that textarea and text fields can be saved in non-Oracle databases, because values over 4000 characters prevented the form from being saved.
          • Adjustment made so that the index does not accept non-numeric characters in forms containing parent and child item fields.
          • Applied document type validation when performing the updateFolder method because it did not validate the document type when updating a folder.
          • Fixed an issue in the zoom component and the web service, since the zoom component in the form was not working properly.
          • Fixed inconsistency in reports that use custom datasets because the dependency that is used for BIRT reports has changed since version 1.6.
          • Improved field validation to block only the use of JS events because fluig was blocking the word “on” in the inputs.
          • Added confirmation validation to the bin, when selecting the option “Restore all documents”.
          • Fixed API services, because API was not considering the downloadEnabled parameter when creating the document.
          • Fixed report URL to allow retrieving at runtime its URL.
          • Fixed the value in the form storage field to display the correct value because it was only considering the option “Single database table”.       
          • Document-specific permissions are being lost when performing check-in. Changed permissions to search permissions on old documents.
          • Resolved an issue with the radiobox element so that it searches for the checked attribute, because it was loading blank forms.
          • Resolved an issue with the method that loads form data because wdkAddChild was not working when it was called in the document ready.
          • Resolved an issue so that the Outlook plugin perfectly authenticates to Identity in environments that are not multi-company.
          • Adjustment made so that Connect perfectly authenticates to Identity in environments that are not multi-company.
          • Resolved an issue because FTP showed inconsistency when authenticating using LDAP password.
          • Improved download routine performance in folders that contain many subfolders. 
          • Added validation preventing documents with version lower than 1 (one) from being added.
          • Version update adjustment because of inconsistency when documents were approved returning a value greater than the number of records.
          • Adjusted the inconsistency in the dates displayed incorrectly on the form when accessed via mobile devices.
          • Resolved an issue to check whether there were logos to be adapted to the new structure, since forms lost reference to the company logo when the version was updated.
          • Deletion of the attachment from the upload volume folder because it was not deleting the file from the folder when posting the attachment.
          • Fixed parameter that validates document downloading so you can print documents from the folder “My documents”.
          • Fixed copy controlled printing so that it considers the use of Microsoft Excel when it is installed on the fluig server.
          • Fixed inconsistency where, when posting a document in a folder with approval, e-mails were sent notifying the users that followed that document, although it was still under approval and had not been posted in the folder.

          • Adjustments made to document view to allow opening several different forms in several tabs. 
          • Resolved an issue so that the controlled copy log displays all the documents printed during the day, because when it was an Oracle database, this behavior was not respected. 
          • Adjustment made to allow printing documents using controlled copies in the following formats: jpg, png, ppt and txt.
          • Adjustment applied to fix situations where, when using the updateSimpleDocument method, the “Use internal viewer” property value was disabled.
          • Resolved an issue in situations where quota control, if enabled, rejected file upload. Adjustments made to WildFly (application server) local cache settings.

          • Adjustment made so that deleting mirror documents works perfectly, being deleted from the folder in question.
          • Changes made to increase security of protected fields on forms. 
          • Fixed inconsistency in order to allow downloading access report to documents in situations where it was requested and not generated.
          • Adjustment made so that the Advanced Search respects the date range registered in general parameters.

          • Adjustment made to the Outlook plugin so that, in some settings, it continues working properly.
          • Adjustments made so that the check-in comment is no longer mandatory via collaborative editing.
          • Resolved an issue so that, when rotating the Android device and returning it to its original position, the zoom fields are no longer misconfigured.
          • Changed Digital Signature literals to the correct language, because they were not translated.
          • Fixed inconsistency when downloading a document that was not configured to use the internal viewer.


          • Fixed inconsistency when entering a text with more than 255 characters in the content field in the e-mail sending activity. And you can now enter up to 4000 characters.
          • Link to access the page to start a request was not working, due to a change. This inconsistency was fixed so that the request with the previous URL is redirected to the correct URL.
          • Fixed inconsistency when selecting people responsible for an activity. When starting a new Request, the list containing people in charge is reset, displaying once again the screen to select the user responsible for the request.
          • The inconsistencies generated when deleting a filter were resolved. When a file under editing is deleted, the feature “Update” will be hidden, and the filter will also be deleted from the user’s session whenever an error is generated in the search.
          • Adjustment made so that you can view request details when the process has a slash “/“.
          • Fixed inconsistencies that hid the “Help” icon when accessing process settings..
          • ECM attachments can be viewed even before starting or saving a request, which helps identify potential errors when attaching files.
          • Request transfer through the transfer screen was adjusted, allowing transfers to be made correctly, without delaying activity progress
          • The start date of a process now is considered from the moment it is saved and, when it is moved and not saved, the routine remains the same
          • Resolved inconsistency generated in the values set in the form field
          • Adjustment made to allow transferring requests with an assignment mechanism by form field.
          • When an activity is configured by an executor and the process has a manager, this being the first activity, the process moves this activity to the manager and not to its executor. This inconsistency was fixed.
          • Resolved inconsistency that did not allow form values to pass between the process and subprocess
          • Fixed inconsistency message when creating a process documentation site, which did not allow exporting the project to the site format
          • Warning message, when moving a request, had a misconfigured text in Spanish.
          • Adjusted inconsistency in the subprocess with the flag to move to the next checked task, accessing the task central
          • Adjusted inconsistency when validating and sending process attachments.
          • Adjusted logic to validate the automatic activity scenario configured with an assignment mechanism followed by another activity configured with a pooled mechanism.
          • Adjusted sorting for empty fields to be validated on an Oracle database.
          • When an activity is configured by an executor and the process has a manager, this being the first activity, the process moves this activity to the manager and not to its executor. This inconsistency was fixed.
          • Resolved inconsistency that did not allow form values to pass between the process and subprocess
          • Adjustments made using controls from the process control and opening tabs, allowing viewing data without the form disappearing
          • SetAutomaticDecision parameter lists all users of the system and not only users from the group assigned to the activity. This inconsistency was fixed
          • Added validation to allow a service activity within a process to be moved to an intermediate status and not return to the previous one
          • Fixed inconsistency in the setAutomaticDecision method that assigned the wrong user to the activity
          • Fixed delay in the task central when sorting requests that need to be in red (expired) and bold (not yet viewed).
          • Fixed inconsistency that generated looping to check permissions on the attachment when using a custom mechanism for attachment security
          • In the tab “view custom mechanisms”, when trying to delete the mechanism, the screen keeps loading and will not close. This inconsistency was fixed
          • Adjusted inconsistency in the message “successfully converted request”, which was misconfigured when converting a request
          • Due to release 1.5.8, some activities are still displayed as active in the process design. Update performed so that the design no longer shows tasks with that status
          • Resolved an issue so that intermediate activities that did not add a note when moved by the process manager can now do that
          • When the user has a process with an e-mail activity followed by two automatic ones and a task configured by group, the inconsistency occurs because it cannot resolve the target user. Inconsistency fixed with validation that allows using the first user on the list.

          • The “startProcess” method of the “ECMWorkflowEngineService” Webservice has been improved with required field validation.
          • Fixed the parallel activities and automatic activity situation, so that they do not incorrectly skip the join.
          • Task Central, when sorting, activated the same method twice, causing performance loss. Resolved an issue to adjust method sorting in the central, making it more performative.

          • Fixed inconsistency where, when using an assignment mechanism by form field in an automatic activity, the user filter screen did not show any users.

          • Fixed inconsistency in the assignment mechanism by association with collaborator groups mechanism
          • Fixed inconsistency when starting requests through Internet Explorer and the process code had accents and spaces
          • Field “Overlap activities and flows” deleted from the process export by the plugin
          • Resolved an issue so that canceled task notifications are correctly sent to the requester and the person responsible for the activities
          • Description of a process version with more than 200 characters will warn the user about the excessive number
          • Cancellation notifications are being correctly sent to the requester when a request is canceled by the manager.
          • Assignment mechanism for a group showed inconsistency when the process was moved to a subprocess. This situation has been fixed
          • Fixed inconsistency that was shown when creating a new filter based on one that was already registered and had form fields.
          • When manually moving an intermediate activity, task scheduler ran the next activity automatically. This inconsistency was fixed
          • Fixed inconsistency that created receipt of duplicate e-mails for activities with automatic input and output flow
          • Fixed inconsistency when choosing form descriptor fields in a new process version, where the request form values did not update in earlier versions

          • A request that contains accents in its process code does not allow displaying its diagram on the “Details” and “Next activity” screens. This situation has been fixed for this version.

          • Fixed inconsistency that sent e-mail to the user who was responsible for the task whose request has a deadline and automatic flow, even when the option “notify person in charge” was not checked

          • After exporting a new process version, it was not possible to convert old requests. This inconsistency was fixed in this new version
          • When deleting an attachment from a subprocess that was transferred from the parent process, it deleted the document (attachment) physically, not allowing it to be viewed in the parent process anymore. This inconsistency was fixed.
          • Dates were not in the correct format in the Add-ons tab, where request history is displayed. Fixed inconsistency in the use of the “Calendar” component
          • Name of the person responsible for the task is different from the name in the activity design, in the task central.  This inconsistency was fixed
          • Resolved inconsistency that prevented releasing a new process version and generated timeout in the browser
          • Resolved an issue to remedy the inconsistency created when configuring an activity that uses an assignment mechanism by form field, where user permission checks got lost, preventing users from taking on the task.
          • Style guide component uses a parameter that conflicts with process files. Fixed inconsistency so that the parameter can be used without creating visual conflict
          • Deleted the requirement that prevented an ordinary user from taking on tasks on behalf of other users through takeprocess method
          • Ajustado mecanismo de atribuição para que o sub-processo atribua o usuário por executor de atividade sem causar inconsistência.
          • Adjusted assignment mechanism for the sub-process to assign the user by activity executor without causing inconsistency
          • Added info log lines to the beginning and end of each method to fix the inconsistencies that were generated when calling request initialization methods in the webservice
          • Created e-mail templates for the requester user and the manager to receive notifications in final activities

          • Created new configuration to be added to the tag, which allows changing response time for a service activity
          • Fixed the word “Responsibility” in the notifications.
          • Validation performed so that, when changing forms in a process on Studio with different descriptors fields, they remain selected when the user changes forms
          • Fixed inconsistency that prevented the user from posting an attachment using the hAPI’s publishWorkflowAttachment method, stating that they did not have posting permission, even though they had all the permissions on the folders.
          • Deleted the options Assignment mechanism by association for a Group and for a Role on Studio.
          • Security when querying requests has been increased so now, when a user tries to check other users’ information, the system will inform if they are the logged-in user’s substitute; only then will they be allowed to query other users’ tasks
          • Fixed inconsistency that showed the request as completed when, in fact, it was canceled
          • Fixed an issue with a substitute user on iOS because, when a user was set as a substitute, they were required to first log out and then log in to the app again in order to view pending items on the mobile app.
          • When trying to search for a user and select them for the next activity in a process, they could only be found if they were visible on the list; this situation has been fixed and now you can filter users correctly.
          • Fixed situation where the image downloading component did not show the images of the process diagram.


          • Adjustment made to grading open-ended questions to display the next question to the grader even when the answer was left blank by the student who took the test.
          • Changed the feature “Learning – Export/Import tracks and training courses” to “Learning – Export/Import training courses” in the Permissions in the Control Panel, because currently the Import and Export actions are available only for training courses.
          • Adjustments made to correctly create the community of subjects or classes when migrating fluig from earlier updates – 1.5.4, for example – to the 1.6.0 update.
          • Adjustment made to update the External ID field in fluig’s user registration when updating the single integration identifier (IDP_ID) in a scenario where fluig LMS is integrated with TOTVS RM and fluig Identity.
          • Translation applied to the notification e-mail template that is sent to the user when they register in training courses, tracks or classes using the Spanish language.
          • Adjusted the time displayed in an online event session because it was showing different times for the session creator and for the guests.
          • Fixed evaluation scheduling in order not to allow the evaluation to be started – from the Task Central – after the date or time set in the scheduling.
          • Fixed comment query in questions in an anonymous evaluation, because the comments were not being displayed.
          • The name of a column in the AMS_ASSESSMENT table was shortened because it had more than 30 characters, causing inconsistencies when starting up the platform and using the Oracle database.
          • Changed the grading open-ended questions feature to allow performing the process correctly when using an Oracle database and, also, to display inconsistencies – if any – when grading.
          • Made changes to prevent lock when querying LMS tasks service (/api/public/lms/tasks).
            Also set the maximum value of 9999 for “Class registration validity days” so that there are no inconsistencies when querying service/api/public/lms/tasks/count when using an SQL Server database.
          • Adjustments made to only update the security of a class when a user to be registered in it does not have execution permission, in a scenario where fluig LMS is integrated with TOTVS Educacional.
          • Added validation to the Certificates feature to warn the user when a sentence in a token is null, avoiding inconsistencies when the student issues their certificate.
          • Changed features Manual score and Adjust score – when accessing a class as person in charge – to display users alphabetically.
          • Adjustments made to processes for requesting and completing registrations so that there are no inconsistencies when registering a group that has several users – 196, for example – in a class.
          • Changed dataset method transactions and learning tasks to allow the use of webservice /api/public/lms/tasks in a widget developed on the platform.
          • Fixed public API  services to enable cancellation of requests and registrations, because they were showing inconsistencies and, consequently, such cancellations were only possible from the graphical interface.
          • Changed way to upload a file to be registered as learning content to optimize the process and avoid inconsistencies in which the file is not saved correctly.


          • Enabled display of throw messages, included in JavaScript developments, on the Dataset synchronization status screen. This change is intended to make it easier to identify problems or unavailability when implementing synchronization. Previously the message was only displayed in the platform’s log.
          • Added use of a sliding gesture to update in the Task Central on the fluig Mobile app for Android. Thus, when a change is made in the Task Central such as changing the substitute, the user will be able to streamline the update on the mobile app by sliding their finger down the screen.
          • Display of the warning “Invalid username or password” when trying to access the platform by entering a valid username and wrong password.
          • Fixed permission inconsistency and added company ID to the parameters sent by the feature Dataset synchronization.
          • Added message informing the user that the time set on the mobile device where the fluig Mobile app is installed is different from the time set on the application server.
          • Adjustment made to the indexation task performed via scheduling so that the procedure is properly completed in the companies that have process attachments registered.
          • Application users (OAuth users, for example) deleted from user selection pages and added to groups and roles.
          • Hid user role while editing user registration data, as this role is default for all users and cannot be deleted or edited.
          • Improved message displayed by the platform when the licensing slot 4012 is not found on the License Server to make the reason for the issue clearer to the user.
          • Resolved an issue to ensure “fluig” service creation and initialization in environments whose JBOSS_HOME environment variable references JBoss/Another application’s WildFly installed on the same service.
          • Enabled editing registration of fluig users that are not registered with the same e-mail address in the company’s context on fluig Identity. This situation is only valid for companies that are integrated with fluig Identity.
          • Added support for authenticated proxy with username and password when sending data to fluig Analytics.
          • Fixed fluig’s specific datasource settings that prevented the media from detecting the used database.
          • Fixed an issue when displaying blank information in a database table that crashed the Company’s Additional Information screen.
          • Added new date format (yyyy-MM-dd) when setting the type of offline dataset structure to Date.
          • Fixed an issue with deletion of language templates from the platform. Thus, the template with the language that is not used can now be deleted without affecting the others.
          • Implemented sorting in the registration table of the e-mail template by column.
          •  Fixed an issue to migrate WSDL settings between versions of the platform.
          • Fixed information generated from handling datasets and displayed in logs, making it more efficient to trace it.
          • Fixed an issue to perform port-offset calculation on internal management ports of the fluig service in domain mode.
          • Fixed an issue to allow access to the platform’s administration pages using LDAP authentication without combined login.
          • Fixed session control when there are improper OAuth headers.
          • Fixed message regarding minimum version of the platform when fluig is updated in character mode.
          • Fixed an issue to clear the platform’s internal cache when the session is over.
          • Fixed wizard screen that prevented installation progress and platform update.
          • Fixed validation that created an on-screen message preventing deactivation of companies that had substitutes and/or pending documents on fluig.
          • Fixed inconsistency that disabled the List calendar component. Thus, when adding a Date column, by adding or editing a new record, the calendar button will be enabled for selection and completion of the procedure.
          • Fixed an issue to ensure an effective operation because, when adding a second account to the fluig app or changing the color of the theme and changing the company a few times, there came a point where the account would not change any more.
          • Fixed a bug in the getValue (“WKUser”) method to return the correct value (logged-in user) in the afterCreateUser global event. Thus, as a value, it returns the login of the user responsible for creating the logged-in user.
          • Fixed an issue with querying permissions by group, which did not show results when the database was converted from TOTVS ECM to fluig.
          • Fixed a bug in the REST request, allowing changing the timeout value when calling external services.


          • Fixed an issue in the fluig’s account change mechanism when the change was performed via fluig Mobile app for iPhone/iPad.
          • OAuth 2.0 service automatically configured in the Intranet Kit’s Slideshow widget deployment to ensure that the integration between this widget and Instagram is working properly.
          •  Adjusted editing of pages containing Content Editor widgets, on which the description is not filled out, to avoid more inconsistencies when editing them.
          • Restored view of articles posted in communities via fluig Mobile app for iOS, when fluig server URL does not use port 80.
          •  Adjusted page Chart in fluig Style Guide so that it shows examples of available graphics.
          • Page code displayed next to the title in the Permissions feature in the Control Panel for easy identification of pages and communities.

          The code is set when creating a page (Single identifier) or community (alias).

          • Widget sorting mechanism was adjusted to fix situations where manually changing widget placement in slots was not being respected after posting the page.
          • Application of the “Resize” and “Extend” options in the SlideShow widget to image rendering on the fluig Mobile app.
          • Implemented paging on the list of birthdays in the Intranet Kit’s Birthdays widget. Learn more at fluig help.


          • Adjustment made to community administrator selection in order to list only the active users in the company.
          • Fixed inconsistency “Invalid ID”, which prevented a new account from being created after deactivation of previous settings.
          • Adjusted relevance and sorting of search results by user when creating a conversation on fluig Messaging.
          • Fixed adding users with identical names to the same group conversation on fluig Messaging.
          • The fluig Messaging mobile applications (iPhone/iPad and Android) adjusted to always display the contact name in the title of the conversation.
          • Fixed image loading to display a new group conversation on the fluig Messaging app for iPhone/iPad, so that the image of the listed conversation is not shown just below the new group.
          • In order to make the search for users more efficient on the fluig Messaging app for Android devices, the results will be loaded in batches of 50 users. When it reaches the last result on the list, a new batch of users will be displayed.
          • The message displayed to the user when entering invalid username and/or password on the fluig Messaging app for Android has been adjusted to be clearer.
          • In addition to checking the expiration date of the session, fluig Messaging now also checks the token validity with the supplier, even if this is still within the validity period. This action is intended to ensure that users have uninterrupted access to their conversations on Messaging.
          • On iOS devices, when tapping a new conversation notification sent by the fluig app, the user will be redirected to the fluig Messaging app.
          • Increased reserved space in the database for the storage of the session token on fluig Messaging to avoid session loss.
          • Fixed icon that displays the number of unread messages displayed in conversations to correctly reflect the number of messages (iPhone/iPad).
          • Created filters in the CommunityDataset to return only the values corresponding to the selected column, such as the name column, without also returning community participants.
          • Implemented auto-scrolling at the end of the conversation when sending a new message via fluig Messaging (Web).
          • Selection of multiple images enabled in fluig Messaging (Web) conversations to allow multiple images to be sent in a single message.
          • Added thumbnails to the list of fluig Messaging (Web) conversations to ensure that all started conversations are loaded.
          • Improved extraction of reports from forms in communities to make retrieval of results more efficient.