Click HERE to see how Saviynt Intelligence is transforming the industry. |
04/12/2022 01:00 PM
Hello,
Anyone notice that if you make the username the same for both the manager and secondary, that the UM campaign will not run correctly?
Use Case: Some of our depts. have sub depts, some don't. So if you wanted to target a 'team leader' of a sub-dept to certify, then you can use the secondary manager attribute.
In the user manager campaign you can only target either manager or secondary, there is no option that if the manager is not present then proceed to secondary manager. And of course, once you enter a manager name in the manager attribute you can never clear that field. So your stuck.
So in some cases you may have the same name for both attributes, but when you run the campaign, you will notice that not all the users will appear.
Is there a way around this?
Thanks
Solved! Go to Solution.
04/12/2022 02:08 PM
Hi David,
Yes you can either select a manager or a secondary manager for whom the user manager campaign should be launched. In case if the manager and secondary manager are the same person, then too the user manager campaign will be launched for the manager/secondary which is selected while campaign creation. In case if the manager is not present then you can use the "default certifier" configuration, in this case the certification will be launched for the default certifier in case if the manager is not present or is inactive (works when all certifier is selected under the "select certifiers" configuration.).
If you are facing an issue in launching a campaign can i request you to please raise a ticket with your field representative and we will look into the case.
Thanks,
04/12/2022 02:08 PM
Thanks Brian,
I understand what you are saying, and I am aware of that. The issue (SSM 5.4), as acknowledged by Saviynt Professional services, who witnessed this during our implementation, is that when the username is identical for both the manager and secondary manager, the campaigns will launch but will include all the users.
I didn't raise it as there were other issues with a high priority, I was just wondering if this is still an issue in 5.5.
Thanks
04/12/2022 02:08 PM
Will not include all users, I should have said.