Reltio Cloud provides a couple of options for developers. One way is by working with an internal JSON file where changes can be made and reflected directly in Reltio. The second method is through the Reltio UI, where developers can modify components like the UI, data model, or data quality. Initially, the UI was limited in features, and although it has improved, not all functionalities are available through the UI yet. Reltio focuses on enhancing the UI to make it more user-friendly and developer-friendly. This transition aims to simplify configurations and support no-code and low-code development.
There are many issues. For example, sometimes, errors related to tokenization occur while creating a match rule. Many tokens need to be created when setting up the match rule, and we need to influence that process so that no digital tools are created incorrectly. Another issue is that we are working with around six tenants. Sometimes, there are differences in the UI between tenants with product data. Recently, we had an issue with our lookup (IDM) values. We had around 37 IDM values, but only 20-22 records were shown in the dropdown when creating an app. We had to type and search for the rest of the records. When creating customer accounts, the client won’t necessarily know the exact IDM value name, so they need to select it from the dropdown.
The solution's UI could be enhanced, and its record filtering could be expanded. A few functionalities should be added, like the dynamic population of attributes.
Architect at a computer software company with 5,001-10,000 employees
Real User
Top 10
2024-05-21T12:33:00Z
May 21, 2024
Whether we want to manage the data or not, Reltio Cloud allows us to onboard it seamlessly. Some features are more robust when exporting. Enhancements are needed to improve the system's capabilities in managing relationships. There is significant room for improvement in how relationships are viewed and managed. Reltio is a cloud-based graphical model, but enhancements in this area would be beneficial.
Reltio Cloud could be improved in two specific areas. Firstly, the API capability needs to be enhanced, as when utilizing the REST API and posting a significant amount of data, there are multiple rejections from the MDM side. This can be due to the MDM server not responding or being unable to process the request. Therefore, I suggest that the API capacity should be increased to handle larger amounts of data. Additionally, I have noticed that the response time from the servers can take up to a minute or a few seconds, which can be improved for a faster response time. Lastly, another area where Reltio Cloud could be improved is in terms of encoding characters, specifically with regards to SK characters, as every system has its own encoding character and sometimes this can be quite challenging. Sometimes when sending a particular character, it can be treated differently due to improper encoding, leading to the creation of duplicate account profiles in the MDM and hindering the merging process. Therefore, improving the encoding of SK characters and coding would be beneficial for the overall functionality of Reltio Cloud.
Sometimes, the service goes down for maintenance or when we run a lot of jobs so things get pushed to the queue and results don't get delivered on time.
Reltio Cloud excels in Master Data Management (MDM), offering real-time data synchronization and a unified data view across diverse sources. Praised for its scalable architecture and user-friendly interface, it enhances operational efficiency and compliance management, making it ideal for handling large volumes of data and improving organizational productivity.
Reltio Cloud provides a couple of options for developers. One way is by working with an internal JSON file where changes can be made and reflected directly in Reltio. The second method is through the Reltio UI, where developers can modify components like the UI, data model, or data quality. Initially, the UI was limited in features, and although it has improved, not all functionalities are available through the UI yet. Reltio focuses on enhancing the UI to make it more user-friendly and developer-friendly. This transition aims to simplify configurations and support no-code and low-code development.
There are many issues. For example, sometimes, errors related to tokenization occur while creating a match rule. Many tokens need to be created when setting up the match rule, and we need to influence that process so that no digital tools are created incorrectly. Another issue is that we are working with around six tenants. Sometimes, there are differences in the UI between tenants with product data. Recently, we had an issue with our lookup (IDM) values. We had around 37 IDM values, but only 20-22 records were shown in the dropdown when creating an app. We had to type and search for the rest of the records. When creating customer accounts, the client won’t necessarily know the exact IDM value name, so they need to select it from the dropdown.
The solution's UI could be enhanced, and its record filtering could be expanded. A few functionalities should be added, like the dynamic population of attributes.
The deployment is difficult. It takes time.
Whether we want to manage the data or not, Reltio Cloud allows us to onboard it seamlessly. Some features are more robust when exporting. Enhancements are needed to improve the system's capabilities in managing relationships. There is significant room for improvement in how relationships are viewed and managed. Reltio is a cloud-based graphical model, but enhancements in this area would be beneficial.
Reltio Cloud could be improved in two specific areas. Firstly, the API capability needs to be enhanced, as when utilizing the REST API and posting a significant amount of data, there are multiple rejections from the MDM side. This can be due to the MDM server not responding or being unable to process the request. Therefore, I suggest that the API capacity should be increased to handle larger amounts of data. Additionally, I have noticed that the response time from the servers can take up to a minute or a few seconds, which can be improved for a faster response time. Lastly, another area where Reltio Cloud could be improved is in terms of encoding characters, specifically with regards to SK characters, as every system has its own encoding character and sometimes this can be quite challenging. Sometimes when sending a particular character, it can be treated differently due to improper encoding, leading to the creation of duplicate account profiles in the MDM and hindering the merging process. Therefore, improving the encoding of SK characters and coding would be beneficial for the overall functionality of Reltio Cloud.
Sometimes, the service goes down for maintenance or when we run a lot of jobs so things get pushed to the queue and results don't get delivered on time.