Hi Imraan,
Please open a support ticket.
Thank you
While the performance challenge is being looked at, could you also modify the text on the Email Notification List tab to "All SailPoint Admins" as it was previously.
unless the behavior has changed and is really to spam all SailPoint identities which I doubt.
Thank you
3 Likes
I would also like to voice support for the nav bar being present everywhere in general. When I need to look at settings or accounts in a Source, which has previously been removed from the nav bar, my mind is saying ‘Why can’t I just right click to open the next required admin link’? No, I have to open a new browser tab, navigate, etc… The idea this is done to keep the user on track may be valid during source setup, but not valid the 99% of time spent there after setup. I consider this a top annoyance with the UI.
3 Likes
@NataliaYunusov I also would like to request that the Navigation Bar be added back for all pages. There are many times when we need to compare a configuration between a lower environment and production, especially if something is not working exactly the same. All of my clients have updated their branding in lower environments to visibly differentiate them from production to aid in incorrect changes, so hiding that is a step backwards in functionality.
Also, what happened to having a button to turn on or off the new features when they were in Beta like this? I recall that used to be how the changes were rolled out, so that if the new feature was affecting the client’s workflow, they could turn it off while it was being fixed. Or they had the option to review the new features at their leisure, not forced to it when they might be working on critical development work for an upcoming Production release.
1 Like
I’ve spent a little more time comparing the new view to the original view and have some additional comments:
-
The new format removed the visual differentiation of the section titles on the Settings page, both the color and outline. The only distinction left is the section heading is bolded and slightly larger. Even though there is still a distinction, I find it harder to quickly differentiate when glancing over it, even though it is the same information. It doesn’t look as polished as before and more like a PoC.
-
The side bar takes up horizontal space unnecessarily. With the change to using the 2 columns for everything, this further limits the width of the viewable space. I see that when you make the width small enough that the sidebar hides, but this was not necessary previously. This also increased the click through for those users who may be using a tablet/Smaller screen/window to manage their instances. Once the side bar is hidden, that now adds an additional 2 clicks to change to another page to view the configuration of the IdentityProfile, one to unhide the side bar, one to change to the new config page, and then another to re-hide the side bar to be able to see what is on the page. This adds 2 additional clicks to the workflow process, when previously only a small portion of vertical space was taken by the tabs and did not require the 2 additional clicks.
-
When the IdentityProfile page is opened the first time, the sidebar is open and the Lifecycle Management (LCS) List is opened. If the sidebar is hidden, then the LCS List is also hidden once the sidebar is unhidden. It doesn’t respect the state it was in previously, and it is inconsistent between first open, and subsequent Unhide operations.
-
Additionally when the sidebar is NOT hidden, the Lifecycle Management (LCS) List Open/Close status is not respected when you switch pages. If I am on Settings and I close the LCS List then I click on the Mapping option, the LCS List is expanded again.
-
The Provisioning/Lifecycle State page seems to have the most visual differences. In the original version, everything was visible on the main page and one could quickly switch through the LCS and see what was configured for it. It DID suffer from not being responsive to page resizing (this would have been a better change for this page, making it go to a single column from 2 when the screen size went down.) On the new page, the sidebar with the LCS in it has been moved to the new sidebar, but now instead of 1 page to view the information about the LCS, 4 new Tabs have been added (however the visual queues of them being tabs have been removed also. ) This means that if you want to look at the complete configuration for an LCS state, you have to click through the 4 tabs now, instead of the singular click on the state. Additionally, if you want to Review the Email Notification List for the states, previously you just clicked through each state and look at the configuration. With the NEw layout, you have to click on the state, then click on the Email Notification for that LCS. Then you have to click on the next LCS and then click on the Email Notification List for that one, and so on. If your side bar happened to be hidden, the process then becomes:
- Open Side Bar
- Open LCS List if closed
- Select LCS
- Close Side Bar
- Click on Email Notification List and review
- Open Side Bar
- Open LCS List if closed *See Next item for issue with this
- Select the next LCS
- Close the Side Bar
- Click on Email Notification List and review
- Repeat the above 5 steps for each LCS to review
- The Settings tab does not adjust the Columns to the size of the screen. It always displays 2 columns, which is not good for smaller screens and makes trying to do anything difficult and more prone to error.
On an iphone 12 Pro with the larger screen, it reduces the 2 columns to their min size, but still requires the user to scroll left/right to see everything. Best Practices here would be to go down to a single column to make it usable.
I hope this feedback is helpful. If others have similar feedback, I would recommend providing it here so that they can have a better picture of how people are using it.
2 Likes
Hi all -
With the scalability issues some users have encountered where customers have greater than 300 ID Attributes causing this page to become unresponsive or slow, we’re rolling this release back globally across all staging (many have already had it rolled back). Apologies for the issues there.
We’ll update this announcement when this release has those performance issues resolved.
2 Likes
Hi Geoff - Thanks for the feedback related to the quick identification of environment when working across multiple. I believe this issue is exists in more places than just the ID Profile screens (for example, I’d imagine this context is very useful when redesigning a role or configuring a source).
We’ve reviewed this internally and are looking solve this limitation across all full-page takeovers like this. More to come, but we appreciate the specificity of the feedback here.
Regarding Beta: This UX Update is not a Preview feature (commonly called Beta), nor a Limited Availability feature. This is a General Availability feature, which does not come with a mechanism to opt out. Some features that require customer configurations to use successfully the first time (like Data Segmentation or Work Reassignment) do come with the ability to enable/disable at the tenant level on launch, but that is not the norm - especially when there isn’t significant new functionality.
@aaron_andrew Thank you for your response. This is an issue in all places, and has been brought up in the past I believe when the Source screen was updated as well.
There was many situations when configuring or debugging that developers may bring up both environments side-by-side as half screen windows to be able to view/compare data. For example:
- Debugging an IdentityProfile change that is not working the same as production
- Configuring a new identityProfile to be similar to an existing one to handle similar user type/multiple affiliations
- Configuring a new source that matches an existing source. In some companies, different departments/divisions may have their own instances of a software product that get configured essentially the same.
Another situation is switching to another task quick (answer email/slack message, talk to colleague, etc) and then look back to the screen to continue working.
I would also consider making the UI more mobile/tablet friendly. With many developers/conultants often away from their main PC, having the ability pull up the tenant and use the interface from the phone would be helpful. In my opinion, the IdentityProfile changes previewed did not make this functionally better.
I understand the point here, but I would make the counter argument that a General Availability Release should be able to be previewed by the users before it becomes primary. I mentioned it in the Source one as well, but changes to the UI Require that any user documentation that was put together for the customer needs to be reviewed and updated. It can, as with this release, affect in-development work, since customers are only provided a Sandbox and Production tenant to work from, so the Sandbox Environment is where most of the development work takes place. If the customer has a go-live scheduled for the timeframe that the sandbox is updated but production is not, this can delay their process/deployment. Many times the Deployment steps need to be documented or confirmed prior to the deployment and having 2 separate UIs makes that difficult.
3 Likes
@aaron_andrew I would also like to mention that when these GA items are released in Sandbox, there is no documentation related to the changes outside this product announcement. For a Developer who hasn’t joined or is not actively on here or compass, the first place you would look when you see something has changed is the documentation site. It would be good if there was documentation that was updated for use with these prior to the Sandbox preview being released so that if there are questions, that can be checked first. It seems like the documentation team is not engaged until the Production release occurs.
1 Like
@gmilunich Thanks for this feedback. I’ve shared your concerns to consider as we continue looking for ways to improve how and when we communicate product updates.
Please do not roll this out until the nav bar issue is fixed. Really seems like this change is going to cause more issues than it solves (does it solve any?) in general so I’m not sure where the motivation to change it in the first place is even coming from.
1 Like
@gmilunich thank you for the detailed write-ups, you’ve done a great job putting into words the concerns and complaints many of us share.
3 Likes
Yet Another Vote for visible navbar and branding everywhere.
1 Like
Hi all -
We have resolved the scalability that led to this rollback, and we are slowly rolling this out over the next two weeks in sandbox. We are targeting a production release on June 30th. I have edited this announcement with that information now.
The root cause of the issue was some page load times in situations where there were 300-500+ ID attributes. These were also not performant in the old UI, but this has been improved with this release.
We’ve heard the feedback around environment/branding visibility and nav bar visibility and are working with our UX team on some potential improvements there. We’re going through some efforts now to evaluate these improvements not just to ID Profiles, but to other administrative design patterns where I would imagine this visibility is useful (Sources, Access Items, etc).
Is there documentation to go along with this release in Sandbox that I can provide to clients/users to review?
I went back and briefly tested the UI and there are still some issues I noticed.
- I minimize the Lifecycle Management so that I don’t see all of the Lifecycle States (LCS), which is my preferred view, when on the IdentityProfile page. If I change between Mapping and Settings, it ALWAYS re-expands those out so I see all of them.
- Most previous comments still stand from above.
@gmilunich Official public documentation will be published when this becomes available in Prod environments on June 30th. We are actively reviewing our communication timing strategy, so as we improve that process, we’ll be sure to communicate those updates.
1 Like