In the latest release of Juriba DPC you can:
Easily create projects using the new project wizard
Execute application management projects using the new application project type
Better control your project scope with advanced project scoping options
Collaborate and share important updates using notes
Plus much more…
Here is what’s new and improved.
The create project form has been replaced with a wizard that guides you through the process of creating a new project. This is the first step in simplifying the process for creating projects in Juriba DPC - we’d love to hear your feedback and ideas for expanding the capabilities of this new wizard.
Thanks to a new application project type, you can now create and execute application lifecycle projects, including upgrades, replacements, and retirements.
Like other project types, application projects can be scoped to a dynamic list of applications - ensuring that all devices (with those applications installed) and users (who have an entitlement to those applications) are onboarded to your project.
Before this update, it was difficult to include users in a device-based project who weren’t the owners of an in-scope device, leading to challenges with changing the owner of an in-flight device.
Now the user scope in a device-based project can be extended to include as many additional users as needed. The same is true for a user-based project, now enabling additional devices to be included in the scope, even if those devices are not owned by an in-scope user.
The notes functionality provides a simple way of recording ad-hoc notes against any device, user or application in your projects. Up until this release, notes could only be added and viewed in the legacy interface.
In this release, notes can now be added, edited, and deleted from the modern device, user, application, and mailbox pages. Plus, a new report enables you to view and filter all of the notes added to a project on a single page.
When devices go through a lifecycle process multiple times, it can be useful to reset the self-service status so that the process can be started over. In the previous release, we added support for resetting the self-service status using bulk update, and in this release, that support has been extended to add a new automation action for resetting self-service.
When coupled with automation actions for resetting your self-service tasks, this can be used to reset the entire self-service process, ready for the device’s next pass through the lifecycle process.
When presenting your end-users with questions in self-service, it can be beneficial to hide the existing answers to ensure accurate or updated data is provided - now you can do just that.
This can be especially useful in cases where the planned migration date has been set for planning purposes, but you don’t want that date to influence your end-users preferred date, or where you are asking an end-user to provide an updated shipping address and want to hide the existing address to ensure a fresh entry.
The save list button now remains visible while scrolling through lists, making it easier to save changes without needing to scroll back up to the top.
Three new email placeholders have been added that can be used to include the current date or year in the subject or body of an email. To use them, add {$CurrentYear}, {$TodaysDateDMY}, or {$TodaysDateMDY} to your email template.
In some circumstances, Juriba DPC’s bulk emailer process sends emails to your SMTP server faster than they can be accepted. This can lead to emails being rejected and not sent.
This new setting allows a short delay to be added between each email sent. Note: this is only relevant for on-premises customers and should only be used if required.
In Active Directory, the last logon time for a user account is stored in a few different ways. The LastLogon attribute is updated when an interactive logon occurs, but only on the domain controller that processed the logon. The LastLogonTimestamp attribute is replicated to other domain controllers but only periodically (every 14 days by default).
Prior to this release, the Integration Connector for Active Directory only used the LastLogon attribute when determining the user's last logon. With this update, Integration Connector will compare LastLogon and LastLogonTimestamp and take the most recent value, resulting in a more accurate last logon value for each user account.
Understanding how many objects have been imported from each of your source systems is important for troubleshooting and gives you confidence that the import is working as expected.
The object count on the Data Imports page has been enhanced to not only show the total count of objects but also the count of each object type.