Check out the new features available in the fluig update 1.5.10:
Do you use Microsoft SQL Server 2008?
Warning!
As previously informed (on 11/28/2014 and 6/22/2016), the fluig update 1.5.10 is not compatible with the Microsoft SQL Server 2008 database. Therefore, the platform startup will be blocked in installations using this version.
If you use the SQL Server, you must update to version 2012 or greater, as described in our Portability Matrix.
For more details, see the press release issued by the fluig product Strategy team.
Architecture
More convenient and safer access to external services
Platform developers and administrators now have a new option in the Control Panel to manage access and security settings for REST services, further streamlining the communication between the platform and these resources.
You can configure the authentication of external services using Basic, OAuth1 and OAuth2 protocols, in addition to testing the validity of the registered information, all in one place!
Register the client to call external services.
After the registration, test the communication with the service.
To learn more about the potential of this new feature, check the documentation that we have prepared for you in Authorization for REST Service client.
LMS
More convenience with automatic enrollments in track trainings
To speed up access to training, when enrolling to a certain track, the student is automatically enrolled in all trainings comprised in such track.
If there are requirements for any of this trainings, don't worry! The automatic enrollment will only be concluded if these requirements are also part of the trail. Otherwise, the registration will be held only in case the student already meets the requirements.
Attention
The automatic enrollment process is performed asynchronously to avoid drops in performance.
BPM
Stay tuned! New rules for using custom messages
Custom confirmation, warning or error messages of the Style Guide accept the inclusion of HTML codes; however, this is not a practice approved by fluig, as it can cause instability when moving requests.
To ensure a smooth flow of movements, we recommend the use of character \n for breaking lines in the texts, and the removal of other HTML codes in custom messages, because soon the platform will no longer interpret them in this component.
Below is an example of how to adapt line breaking in messages to the recommended standard:
function validateForm(form) {
if (form.getValue('product_code') == 'A8973') {
throw "Atenção! \n Este código de produto não é válido. \n Por favor informe outro código.
}
}
function validateForm(form) {
if (form.getValue('product_code') == 'A8973') {
throw "Atenção!<br /> Este código de produto não é válido.<br /> Por favor informe outro código."
}
}
Style Guide
Another way to use autocomplete
Check out our Style Guide for a new sample deployment of the Autocomplete component using an array, without REST calls to Web Services.
More information
Access the Autocomplete component on the Style Guide and get more detailed information.
Visão Geral
Import HTML Content
Conteúdo das Ferramentas
Tarefas