Bug fixes: 2025.3

Throughout the Administration section, UI labels will no longer show placeholder text in some cases, and will instead correctly show the specified label text.

If an external SSO system is used to provision users in Uptempo, the Uptempo system-default SSO group will no longer be automatically assigned to new users who are not recognized by the external SSO system when this group is deactivated (when the Use as default setting is turned off for this group).

Storage Groups (VDBs) that were missing after upgrading to BrandMaker 8.0/Uptempo Work are once again visible, and can be assigned to users again.

When you open the Create Activity setup assistant, the footer in the dialog is now displayed at the correct width, and the Next button is no longer cut off.

In the Create Activity setup assistant, entering a value into the Planned Inquiries field (under Impact > Planned) and then deleting it no longer causes an error message to be displayed.

In the Create Activity setup assistant, when in-market dates are set as required, clicking the heading of the second step (for example Details) instead of the Next button no longer causes the setup assistant to crash.

When you create an activity and select an Activity Type that does not require a parent activity, the Next button is no longer deactivated until the Activity Type has been selected a second time.

When you connect an activity to an investment, entering a search term that matches a very large number of activities no longer causes an error.

When you are in Investments section, hovering on any other section in the navigation sidebar no longer displays duplicated tooltips for the name of the hovered section.

If you leave a tab with a Financial Management module page open but inactive for some time, returning to the tab later no longer causes a white page with the text "null" to be displayed. Instead, the system now correctly allows you to resume using the page (if your session is still active), or redirects you to the login page (if your session has expired).

Using ActivityCollection.getAll to retrieve all activities no longer causes the connection to the API to drop with a timeout error in cases where the response takes longer than usual.