For my initial impression, I can’t say that the new experience is an improvement, and find it harder to use. I agree with @jrossicare that by moving the “Accounts” and “Entitlements” so far away and splitting them up, that it makes the new page would be harder to navigate. His suggestion for moving them to the top would help alleviate that to some degree, although there are other pages I would move too. I would argue the previous page was actually well laid out, with each tab clearly visible at the top, and the primary activity you would want to do was the first page shown when the tab was selected.
With Sources, my experience has shown that there are 2 distinct ways that admins use the existing pages: Regular Activities and Configuration.
The following I would consider Regular Activities:
- View Accounts
- View Entitlements
- View Access Profiles
- View Aggregation progress/history
- View Entitlement Aggregation progress/history
- View number of Uncorrelated accounts.
The Following I would consider Configuration:
- Correlation
- Password Settings
- Account Schema
- Anything under Source Setup (Differs by Connector)
- Create Account
- Update/Enable/Disable/Delete Provisioning Policies (as @angelo_mekenkamp mentioned)
- Attribute Sync
- Native Change Detection
- Connections (This could really go in either)
- Delete Source
The way that I differentiate these two groups is by what pages am I likely to look at on a regular interval, and what I am likely to look at/configure then not touch once the source is considered set up. Almost all of the items in the Configuration group are only accessed regularly while the source is being set up, and then only updated as needed. These items do not need to be on the primary page, and invites admins to make accidental changes easier.
On the other hand, the Regular Activities are things that an admin might check often to see the state of the source. For instance, they could check the status of the aggregations for the week, looking at the Account Creation/Deletion details that @shilpa_nc mentions above. An admin may also need to kick off a manual aggregation to pull in a new account or entitlement that was added by the Source Team. Similarly, when working to resolve the Uncorrelated accounts, it is often necessary to view the list of them and work through them.
I thought the direction that the changes were headed, moving the configuration items (Correlation, Account Schema, Create Account) under the Edit Configuration button, while leaving the others in the existing UI, was the right way to go. This move was starting to place the configuration items together, while leaving the reference items and actions on the main page.
If you are able to separate the source into Regular Activities and Configurations like this, it also opens up the option of having a Management Source Admin, who can view accounts and run aggregations, and a Full Source Admin, who can also handle updating the configurations as well. This separation I think would be beneficial to many clients who want users to be able to run and view aggregation details, but do not want them making changes.
We’re excited to announce that starting at the end of August, we’re migrating the source configuration pages to our new user experience!
