and more in a single search tool across platforms. Read the announcement here. |
03/28/2023 09:27 AM
Can we extend the system default "userStatus" attribute in the certification? If yes, which version is it supported?
If no, is there a way out?
03/28/2023 09:31 AM
Hi @UdaySai ,
Can you please elaborate on the ask with more details around it. Which certification exactly are you looking at and what's the business use case around the ask etc.,
Thanks,
03/28/2023 09:39 AM
We have a requirement to populate user status in the campaign as there have been times where certifiers might be reviewing inactive user as accounts might not have been terminated due to some reasons. We need to capture status in this case to ensure certifier is making informed decision.
03/28/2023 11:21 AM
@UdaySai , in order to exclude inactive users you can exclude them in advanced config and only include active users. Also you can include status in config 'show user attributes' to have the status shown in the certification for the certifier.
Thanks,
03/29/2023 02:17 AM - edited 03/29/2023 07:58 AM
We need to capture inactive users and not exclude them.
user status is not available under show access attributes for application owner.
show user attributes is only available in user manager and that campaign is only launched for active users.
version 5.5sp3.
03/29/2023 10:57 AM
For default user status - it is available under show user attributes for entitlement owner campaign and user manager campaign. Having user status in UM campaign doesn't help as it is launched for active users only.
04/05/2023 08:07 PM
Hi,
In Application owner campaign , by default both Active and Inactive users will be included in the certification. This is expected behavior of the product.
If any inactive user is having active account in the system then this can be handled in the application owner certification by the application owner
In the campaign config, you can include the user status in "Show Access Attribute"
Thanks
Devang
04/14/2023 01:38 AM
04/14/2023 06:04 AM
Hi,
This might be a product issue. Can you open Saviynt ticket and check? I am able to see the same in my environment.
Saviynt version 5.5
Thanks