Hi, I am having problem to allow an entitlement from a delimited text source to be requested. If I mark an entitlement as requested, it appears on request center but is never granted. If I add it to some role, role does not appear on request center. If I trhow entitlement from role, it appears.
I know provisioning is not a feature of this connector. It is a workaround to have some “flag” on an identity to perform some client desired action. Is a fact that a DF account can not have an entitlement assigned unless it is via aggregation?
@jsosa Did you see anyone else getting manual task assigned? As i have noticed this being source owner, tickets are getting assigned to someone else for Delimeter connector type.
As I did not find some better way yet, will post a workaround which worked, for me, until some better solution can be found.
Client goal is to have some way to disable users directly from ISC, no matter what comes from RH. This couses that a simple lifecycle change will apply until next aggregation.
So, I build up an empty role, which user can grant or revoke. This will be examined every hour by 2 workflows (one that fulfill an string field in a delimited text source, with true, other workflow just call a json patch remove of that attribute).
Finally, a transform with a first valid, taking precedence the occurrence of this attribute to put user in an intempestive disabled LCS, and other way, let some other RH status map to LCS.
