Hi Kapil,
Thanks for your response! We also have a requirement to create tickets for other changes to the account i.e. create or update access. We have more than one sources with such requirements and because of that we added all our sources into the Service Desk integration. The integration is able to create a ticket for Create, Modify access or even for disable request. Like you mentioned, we have added our sources to disable list on particular life cycle state and that triggers a ticket but the problem is the account stays enabled and therefore on the next identity life cycle state where it needs to enabled it doesn’t create a ticket to reactivate the account. Hope this explains the problem
Also, as per this discussion, it seems that once we add a source to service desk integration any rules defined on the source won’t trigger - Before Provisioning Rules and SDIM Integration. Otherwise, we could have used the rule on JDBC source to flip the appropriate flag on the enable/disable actions. Also, it seems it is not possible to skip ticket creation for certain actions once you add the source SD integration. So, I guess our option is to let SD integration create tickets for CREATE, UPDATE and DISABLE action but do the enable ticket via Workflow on LC state change?