What’s new in INFLOR Sociall?

See the new INFLOR Sociall updates available in this release.

Authorized Service Request

[IS-4312] – Improvement in SISPART

Request
The scope of this improvement is to remove from the “Evaluation Method” of a request the “Deferred / Unallowed” suggestion when the activity is a Record Analysis activity.

Adopted Solution
A rule based on activity type was created to not display “Deferred / Disallowed” of the “Evaluation Method”

Problem

[IS-8606] – Error while syncing in the Sociall app

Reported Scenario
When running the data synchronization to insert new occurrences by the application, it did not insert the occurrence and returned error.

Adopted Solution
The equalization of all Mobile X Sociall calls was made.

[IS-8782] – Error when trying to advance the flow of a request from activity “Responsible Area 1” to the “Response” activity in Suzano’s environment

Reported Scenario
When trying to advance a call from “Responsible Area 1” by the HTTPS protocol gives security error.

Adopted Solution
Amazon Load Balance (ALB) was set to force redirection to HTTPS

[IS-5594] – Problems in the questionnaire interface

Reported Scenario
When viewing or answering a questionnaire, questions that contain details or justifications are single-line fields, making it impossible to see the full text entered.

Adopted Solution
Screen adjustments were made to visualize and respond, evaluation. Extending to multiple lines the questions that contain details or justifications, and even the restriction of quantity of characters.

[IS-10606] – Problems with permission to access Relationship History in occurrence

Reported Scenario
It has been identified that even without user access permission is accessing the menu social inventory.

Adopted Solution
Correct adjustments were made by creating a unique permission for the Relationship History report in.

Incident

[IS-9056] – Additional information: report occurrences in QA

Reported Scenario
In the Periodic Occurrence Report (SOCIALL) report there is the feature of selecting the columns that will appear in the report. Columns for additional occurrence information fields (companion information) are always appearing even though they are not selected.

Adopted Solution
Correcting field validation.

[IS-8300] – Occurrence Side Menu Correction

Reported Scenario
It was not showing up the menu occurrences on the dashboard, even when the user had permission.

Adopted Solution
It was verified that the menu only appeared when the user has some occurrence in its name. This validation has been removed, now the menu always appears regardless of whether or not user-linked instances exist.

[IS-7156] – Printing Reports on Orders

Reported Scenario
When you export a report as PDF, encode error occurred.

Adopted Solution
Using encode UTF-8 when generating PDF.

[IS-6246] – Required field deactivation

Reported Scenario
Applicant field does not appear in the request form, either for fill or for display.

Adopted Solution
Internal correction on the component.

[IS-6201] – Screen Improvement Demand History

Reported Scenario
It was identified by the client that the “Result” field in Demand History did not reflect the status of the activity, we evaluated that there is no error, since the “Result” presented in History refers to the result of the evaluation.

Adopted Solution
Adjustments were made on the demand history screen, changing the label “Result” to “Evaluation Result” and created a new field labeled “Activity Status” to facilitate understanding of the history.

[IS-6186] – Correction in “Close” functionality on the screen

Reported Scenario
When the applicants are edited, and we click the NEW icon, we can’t return to the form through the CLOSE icon.

Adopted Solution
Fixed call function to return to PI.

Other Evolutions

[ISTD-2701] – Parameterize decimal places of indicator mediation

Reported Scenario
Some types of indicators require more than two decimal places.

Adopted Solution
You have created a global parameterization that defines a default value, you can also set the number of decimal places in the indicator type separately. If neither is configured, a default value of 2 decimal places is used.

[ISTD-3589] – Main Menu: Problems in the side menu

Reported Scenario
It was identified by the client that the “Result” field in Demand History did not reflect the status of the activity, we evaluated that there is no error, since the “Result” presented in History refers to the result of the evaluation.

Adopted Solution
It was identified that on the Sociall main page the side menu was not showing up as it should. In the analysis of the error it was identified that a function that is not native of Java 7 presented errors, preventing the appearance of the lateral menu.