LevaData release notes version 3.2 Follow
Technical Enhancements
-
Migration from MySQL to PostgreSQL
With the increasing amount of data within the Levadata community, we encountered certain performance issues with MySQL. Performance is can be optimized in PostgreSQL which is now the backend for the entire platform.
-
Automation within Cognitive Sourcing Platform: Post Data Refresh Tasks, etc.
Post data load steps are now automated, this will remove all the manual errors that may have occured during the manual data load process.
-
MI Calculations are now part of the Data load process (DIS)
Previously a separate database where Market Intelligence calculations were performed was used to store calculations. The new This new approach will make Market Intelligence dynamic. That is any change in customer’s data we have an impact on community data. So Market Intelligence is always up to date. (Note: Customer will see the updated Market Intelligence data in Part Match, Competitiveness, and Raw Materials screens as it is dynamic. The updated Opportunities will reflect in UI only after Sisense data refresh. As MI > Benchmark is also Sisense based, the updated data will reflect in UI after Sisense data refresh)
Comments
0 comments
Article is closed for comments.