Service Automation

In some environments, like ours, users don't go through the normal active -> disabled -> deleted lifecycle. We just remove users from HelloID SA after their last day (technically, HelloID provisioning removes a group membership and this causes their SA profile to be removed from LDAP synchronization). It seems that user deletion doesn't cause their products to be returned. As deleted is the next step after disabled, I think it really should.

Many of our delegate forms have AD account search as the first step, which requires you to look up an account, click to select it and then click "Next" to proceed to the second page of the form. Would it be possible to simply confirm the user selection by double-clicking the account in the search results? If you used UMRA before, you know how practical this is, would be great to see it in HelloID too, thank you!

Note: this feature is part of the milestone "Recertification" and requires the HelloID Governance module license. I appreciate the valuable insights provided in the Recertification Insights section, which offers a clear overview of selected Campaign iteration. The ability to view recertification request states on the iteration details page is particularly helpful for tracking progress and managing requests effectively. However, while the current filtering and search options are useful, there is no filter for the recertification request state. Adding this filter would significantly improve usability by allowing users to focus on specific request states, making it easier to track and manage requests efficiently. Please add a filter for the recertification request state in the Recertification Insights section. This enhancement would allow users to refine their view and focus on relevant requests at any given moment

Note: this feature is part of the milestone "Recertification" and requires the HelloID Governance module license. Recertification campaigns can be configured either for insights only or to result in recertification requests. While most campaigns serve recertification purposes, some (such as the system campaign "Product assignments not linked to any other campaign") are exclusively for insights. Currently, the end-user interface for Recertification Insights does not indicate whether a campaign iteration is insights-only or also triggers recertification requests. This lack of clarity can lead to confusion for users interpreting the results. Please update the UI to clearly distinguish between insights-only campaigns and those that initiate recertification requests.

Note: this feature is part of the milestone "Recertification" and requires the HelloID Governance module license. Recertification requests can be recertified, leading to a progression in the campaign iteration. As a security officer, I want to see this progression information while using the Recertification Insights overview and the campaign iteration details page. This improvement will ensure that security officers have all necessary insights at a glance, enhancing the overall recertification workflow.

I would like to be able to use a height value on a "Dual list" form field. Just like this is available in a "Grid" form field.

The current Self-Service product category view is very helpful for navigating to the correct product category and requesting the desired self-service product. However, depending on the HelloID configuration—such as the number of products per category and the group structure for scoping requestable products—the category overview can take some time to load. Please optimize the UI performance by minimizing the amount of data queried during the initial page load. Instead of retrieving all data upfront, only essential data required for rendering the UI should be loaded initially. Additional data can be fetched asynchronously after the initial page has loaded. This approach ensures that the UI remains responsive while still displaying all relevant information without interfering with the initial page load.

Just like the request for provisioning, it would be good to have a version history of all parts of HelloID Service Automation that is restorable, like we had in IAM and UMRA.

Currently, all available user-defined and system automation variables are accessible in script actions by default. This approach is convenient for reusing values across multiple scripts without embedding them as plain text. However, there are scenarios where limiting access to specific variables is necessary. To enhance control and security, I propose a change to the default behavior of automation variable availability in script actions. By default, no system or user-defined automation variables should be automatically available in script actions. Users should have the option to explicitly opt-in to the necessary system or user-defined automation variables on a per-script basis.

Hello, we're fairly new customers and making use of a dual list in one of our delegated forms. The ">>" and "<<" buttons that move the entire list over leave the opportunity open for our internal users to do some damage. I would like to request the capability of either disabling these buttons, or the preferred option is the option to remove them entirely for a cleaner look to the form. I see this was requested in 2020 and didn't gain much traction as far as upvotes, but we'd greatly appreciate this capability at our company! I anticipate several uses for these dual lists down the road. Thank you for considering