Contents
SmartOps is enabled with the capability to archive transactional data stored in the platform. The archival can be performed for period older than a specified date (as per business requirement). This helps in
Improving the performance of the platform by limiting active data
Enhance security by limiting the range of data that is accessible via the platform
Save cost by moving older, unused, data to cheaper storage
Data older than a specified threshold will be moved to another table in the same or different database. This table will be named based on the version of the original table.
Version of clones engine cache is centrally maintained in a Redis store to ensure consistency across replicas in high availability deployments.
Error handling and retry mechanism for Clones inbound queue listener
Messages that fail retry will be pushed to a dead-letter queue
iHub is enabled with support for Office 365 as email channel using OAuth2 protocol. Currently IMAP is being used as the protocol for email channel
iHub high availability deployment is enabled by synchronising channel polling for e-mail channels.
iHub is enhanced with the capability to read and extract inline attachments in e-mails.
SmartOps PWF framework is enhanced – If the “Project Status” is in “Installing” status, only installation workflows should be executed. This will restrict the execution of all other workflows for projects with installing status.
Enabled migration of UI library to Mono-repo architecture.
Leveraged the capability of Jest as unit testing framework in all UI frameworks.