Filter additional subscribers for reports

Hello Veronique,

Filtering the candidates endpoint /portal/candidates/Person is not recommended, as it is used throughout the portal for different purposes.
There is also no feature in the admin portal to remove the 'Add additional subscribers' step. You must alter the angular project to do so.
Maybe you could create a proces/script that removes the entries in the RPSSubscriptionCC afterwards, for reports where adding additional subscribers is prohibited. (poor man's solution)
P.s. this is just my best effort maybe there are other/beter options.

Thank you! Is there any documentation about the candidates endpoint? We indeed have this problem with every feature on the portal that allows to select everyone, as we don't want every portal users to see or select others they are not working with. Where could I change it?

For candidates filtering on endpoints:
One Identity Manager Administrator Portal: Configuration > Web Portal > Three-dots icon > Create configuration key
Choose: API method configuration
Value: candidates_Person

Then search your created key by name: candidates_Person
Property configuration > API method configuration / candidates_Person / Filter condition
Click on it and define your where clause: Isinactive = 0

And for candidates filtering on foreign keys:
https://www.oneidentity.com/community/identity-manager/f/forum/36953/api-server-filters-for-object-selection-what-does-it-do-and-how-does-it-work

thank you, it worked... until we restarted the web server. We did apply the changes globally and the keys were persisted across all CCC.CompositionApi.global.json files in the different portals but it only works at first, on the web portal we modified and that's it. 

Thank you, so it worked, but temporarily. I applied globally, and the app did save it across the different "CCC.CompositionApi.global.json" for each web portal. But as soon as I restarted the web server, it disappeared. It also didn't apply to the other web servers despite being in the config files. I tried deleting some of the cache files but that didn't help either. Have you encountered such issue before?

Not sure, but look in the bin folder of the API server where you made the change can you see the changed config in the CCC.CompositionApi.global.json
and if you saved it globally it should also in your DB.

select convert(varchar(max), convert(varbinary(max),filecontent)) As filecontent from qbmfilerevision where filename = 'bin\CCC.CompositionApi.global.json'

Thank you, the CCC.CompositionApi.global.json is correct and so is the one in the db (thanks for the query) so I'm not sure why it doesn't work.
I'm going to mark your answer as a solution because technically, it should work, even though it doesn't.

Thank you, the CCC.CompositionApi.global.json is correct and so is the one in the db (thanks for the query) so I'm not sure why it doesn't work.
I'm going to mark your answer as a solution because technically, it should work, even though it doesn't.