DRYiCE ROAR R6

With this release, we have introduced a new architecture to improve application performance, ensure seamless operations and increase user efficiency. We have also introduced new capabilities to automate processes, enhance security, customize data and reports. Please find the same put forward in this release note. 

Onboarding

The Onboarding module is used to configure the basic details required to set up the application for the user. Following are the feature enhancements in this module:

• We have introduced "Date Picker" functionality in the Resource Unit creation module to configure the nth day of the month and year for specific attributes such as ‘AMC_Start_Date’, ‘AMC_End_Date’, ‘HW Last Scanned on’ etc so that the nth date of the month and year can be auto-populated for the attributes based on the calendar month saving the time and effort of the users in having to fill them up manually for each month.

• We have introduced additional date formats in the Company Creation/Update section e.g., dd.mm.yyyy, mm.dd.yyyy, yyyy.mm.dd allowing the application administrator to select from an array of options based on the preference of the customer. These new date formats have also been extended to support the import of data to and from ROAR since customers have specific formats of choice to represent dates.

• We have introduced a feature to enable the application administrator to specify the preferred date format for a company in the User Profile section which will apply as the default date format for all users of that company throughout the application. All reports will also be downloaded displaying dates in the default format set by the application administrator.

• We have enabled the display of an error message to alert application admins while creating a user in case the user already exists in ROAR, in either active or inactive state. This will ensure duplicate user IDs are not created for any company. In case the user is in an inactive state, the application administrator will be prompted to activate them.

• With the implementation of a new authentication system, we have moved away with the existing manual process of password creation for new users. Instead, passwords will now be system generated and notified to users via email.  The migration to a new authentication system will save time and effort needed to manage user’s identity and also improve data security.

Aggregation

The Aggregation module identifies potential records from different sources for merging and merges them to remove duplication and create a clean and accurate record database called the Golden Dataset. Following are the feature enhancements in this module:

• We have introduced the capability to download a single consolidated Golden Dataset (GDS) output for all classes instead of the existing option of being able to download only class-specific GDS outputs. With this feature, customers will have the option of downloading one consolidated GDS output to get a holistic view instead of multiple class wise outputs.

• We have introduced additional operators in the prioritization rule for class prioritization from a data source. Earlier the rule could accommodate only numeric values in the form of greater than and less than. We have added more criteria for numeric values and introduced criteria based on alphanumeric strings. This will offer more options for setting class prioritization qualification rules.

General product enhancements

• We have migrated to a new architecture with high performance, availability and, scalability to handle heavy production workloads. This will ensure reliable and seamless execution of jobs to enhance process efficiency for the users and eliminate process breakdowns. Improved performance capabilities will lower the overall processing time through seamless import of data source files from manual imports or automated processes.

• We have added a new capability on the onboarding and normalization module where the filters selected by users to generate reports on the data within the modules will be retained as long as users remain on the same page to make it more convenient for them and improve their user experience.  Earlier the filters would be reset to their default value once the reports were downloaded resulting in a poor experience for users if they wanted to reuse the filters on a different set of data on the modules.

• We have implemented multifactor authentication and cloud directory capability in ROAR to authenticate login attempts of valid users and allow access to ROAR. The authentication code issued to the user on their registered email ID  will be valid for 15 minutes from issuance.

• We have disabled the existing feature of authentication of a user through the secret question for a password reset. Now users will receive a link on their registered email ID to reset their password, removing the inconvenience of having to remember answers to security questions.

• We have built dedicated connectors to automatically ingest data from CSV files, Active Directory, and Microsoft System Center Configuration Manager to ROAR to enable automatic import of data into ROAR.

• We have built dedicated connectors to automatically ingest data from ROAR to IBM Maximo Asset Management and ServiceNow to enable automatic export of GDS from ROAR.

• We have enhanced the reporting capabilities for duplicate and unbilled CIs using object-based storage.

Defects

• We have fixed the critical, high, and medium-risk vulnerabilities identified in the SAST during third-party security assessment.

DRYiCE ROAR creates a single source of truth by processing data in the IT environment from multiple IT & OT tools in the enterprise, which can drive the accuracy of downstream applications by removing data reliability issues.

For product-related inquiries, please reach us at [email protected]