1E Solutions 24.3 release notes
Schedule
The release will be deployed on March 26, 2024 at 8:00 AM UTC.
Solutions UI change
The UI of the Solutions portal has been modified to improve its look and feel. The major changes made to the UI are as follows:
The Solutions Menu has been relocated to the top-right corner, adjacent to the logged-in user information.
The header is now broader and the solution name font has been enlarged.
We have introduced a new left menu to browse different pages. The menu can be expanded or collapsed using the chevron icon located at the bottom of the pane.
We have added a new toggle to show/hide VMs on the Device Refresh dashboard.
1E for MS Intune
Updates to the MS Intune DEXPack https://exchange.1e.com/product-packs/solutions-intune/.
The Intune solution now uses rules instead of events for reporting.
New RoI dashboard for MS Intune.
New pages for Operational dashboard, Rules Occurrences and Policies and Rules:
Operational Dashboard: Provides compliance status of devices against the Intune policy.
Rules Occurrences: Shows details of the rules that occurred on devices in a specific period.
Policies and Rules: Policy page for Intune policies showing details of included Checks and Fixes.
Configure Rules: Allows you to set different configurations which are used for calculating RoI data.
Microsoft Intune integration with ServiceNow and Jira:
Admins can configure rules that allow Solutions to open incidents if an Intune rule has failed.
1E for Incident Automation
RoI dashboard to show the effectiveness of Endpoint Automation, and provides a view on the following:
Automations run and support tickets avoided.
Related financial savings.
Related savings on support and end-user hours.
Operational dashboard providing actionable data.
View of All policies and all Rules enabled in 1E platform.
Incident automation integration with ServiceNow and Jira. Admins can now configure rules to allow solutions to open incidents if a rule has failed.
Note
1E for Incident Automation is a restricted release and will be available only for early adopters and on-demand.
Other features and enhancements
The Device Connectivity dashboard now shows the number of devices added/updated, device events, and rules that occurred in the past 24 hours and the past 30 days.
Updates since the last release
Type | Product/Client | Issue ID | Summary |
---|---|---|---|
Fix | Device Refresh | DEXSOL-406 | The Device History page now shows event details of all the events that occurred on a device. |
Fix | Device Refresh | DEXSOL-409 | The Event History page now shows the correct data in every grid. |
Fix | Device Refresh | DEXSOL-430 | The Device History page now shows events for audit logs. |
Fix | Device Refresh | DEXSOL-446 | We have made performance improvements and code optimization for faster processing of device and event data. |
Fix | Device Refresh | DEXSOL-480 | The Status Calculations has been modified to run in a controlled way and to process data faster. |
Fix | Device Refresh | DEXSOL-481 | The Model Averages timer has been modified to run in a controlled way and to process the data faster. |
Other improvements and fixes in this release
Type | Product/Client | Issue ID | Summary |
---|---|---|---|
Improvement | Core | DEXSOL-489 | The ServiceNow integration now includes device |
Improvement | Core | DEXSOL-380 | The audit log now can now be filtered to show a specific number of records. |
Fix | Device Refresh | DEXSOL-415 | The link to view incidents has been changed to View Incidents from View ServiceNow incidents. |
Fix | Device Refresh | DEXSOL-495 | The End of Life page has been fixed to show devices when the rule is executed. for the first time. |
Fix | Device Refresh | DEXSOL-492 | The relationship between the previous hostname and the new hostname for a device is now correctly seen in the Device History page. |
Fix | Device Refresh | DEXSOL-502 | Some of Device Refresh rules showed a warning for storage limit on the client. This has now been fixed in the DEX Pack. |
Fix | Device Refresh | DEXOL-484 | Device Refresh rules threw an error when more than one user was active. This has now been fixed in the DEX Pack. |