Data integration - 2.2.4

Flavia Santos
2025-05-11T19:13:47Z

Data integration component created

In version 2.2.4, we have introduced a new data integration component, which aims at centralizing and simplifying access to the integration resources of SoftExpert Suite.

Before, users would experience difficulties in locating integration-related menus, which were distributed across different areas of the platform.

To solve this problem, we have gathered these features in one single component, which will be available to users with the Manager license.

The new Data integration component comprises the following migrated menus:

Former menu | New menu (Data integration)
Dataset (AD067) | Dataset (DI006)
Dataset type (AD068) | Dataset type (DI007)
Credential (AD069) | Credential (DI004)
Data source (AD047) | Database (DI003)
REST data source (AD052) | REST (DI001)
Web Service data source (AD053) | SOAP (DI002)
Data source history (AD064) | Data source history (DI005)
Tracking (CM015) | Import tracking (DI013)
Scheduling (CM017) | Import scheduling (DI014)
Synchronization history (CM024) | Synchronization history (DI015)
SCIM provisioning (CM033) | SCIM provisioning (DI009)

Credentials management improved

In this version, we have improved the Credentials feature with a view to providing greater transparency, traceability, and control over changes made.

Now, whenever a credential is changed by a user who is not its original creator, the system will send an automatic notification to the creator of that credential.

This improvement intends to ensure that those responsible for credentials are aware of any modifications performed by third parties.

Moreover, we have implemented a complete change history for each credential, including information such as:

Who created the credential.

Who made changes.

When each change was made.

Check out the main benefits of these improvements:

Greater visibility as to the life cycle of credentials.

Increased security and reliability as to the use of shared credentials.

Greater control for administrators and integration managers.

JWT token change history

For greater transparency, security, and control over access via token, this version brings important improvements to the management of users' JWT tokens.

Now, on the JWT token management screen, users count on two main new features:

JWT token change history

It is possible to view a detailed history of the changes made to the token, with the following information:

Former token (for reference).

Invalidation date and time.

IP address that made the change.

Identification of credentials impacted automatically when the token was changed.

Moreover, the screen displays the current validity of the token, allowing for better renewal planning.

New token update flow

When trying to generate a new JWT token, users will be presented with a screen showing all the places where the current token is being used.

From this screen, they will be able to choose between two options:

Update the JWT token only.

Automatically update all credentials that use the current token.

This feature prevents integration failures caused by outdated tokens and provides greater autonomy and security to users during the renewal process.

Check out the main benefits of these improvements:

Greater traceability of changes made to JWT tokens.

Greater control over impacts on credentials and integrations.

Reduced operational errors related to token changes.

Improved security governance.

Verification of compatibility between driver and data source – Database

As part of the initiative to improve the stability and predictability of database connections, this version includes a new compatibility validation between the drivers used and the versions of database servers.

New columns have been added to the list of records on the data source management screen: Driver version, Database version, and Connection status.

If an incompatibility is detected, an alert message will be displayed.

Check out the main benefits of this new feature:

Greater security and predictability as to the configuration of database connections.

Preventive alert for configurations that may cause errors or inconsistent results.

Support to technical governance, preventing the use of non-approved versions.

Integration documentation restructured

After conducting usability studies, we identified that the integration documentation had a confusing and little intuitive structure.

Faced with that, we performed a thorough content restructuring by reorganizing topics, improving navigation, and making the documentation clearer and more accessible.

This change aims to facilitate the understanding and use of integrations, providing users with a more fluid and efficient experience.

Check out the latest improvements made to this component:

SoftExpert Suite 2.2.3

SoftExpert Suite 2.2.2

SoftExpert Suite 2.2.0

SoftExpert Suite 2.1.8