Hi All, Is there a way to stop the manual workitem creation for delimited application? Need Help Urgently on this

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

8.3
*

Share all details about your problem, including any error messages you may have received.

Is there a way to stop the manual workitem creation for delimited application?. I dont want workitem created for delimited app when certification revoke happen.FeatureString use are DIRECT_PERMISSIONS, NO_RANDOM_ACCESS, DISCOVER_SCHEMA Hidden Text

2

Manual work items are the default provisioning pathway for IIQ. The best way to stop this from happening is to take away all of the ways that could trigger provisioning for this application. If there are no requestable entitlements for the application, no entitlements bundled into IT/birthright roles, no certifications configured that target the application and no attribute sync setup for any attributes of the application, there shouldn’t be any provisioning unless you have custom code that’s creating provisioning plans for it for some reason. I guess my big question is, why are you certifying this application if you don’t care about what the decisions are?

But if you can’t remove all of the ways that things are being provisioned, you can create a custom IntegrationConfig object like this:

<IntegrationConfig name="Null Integration"
executor="my.example.package.IntegrationConfigUniversal">
<!--
  <Attributes>
    <Map>
      <entry key="operations" value="Create,Modify,Delete,Enable,Disable"/>
      <entry key="universalManager" value="true"/>
    </Map>
  </Attributes>
-->
  <ManagedResources>
    <ManagedResource name="MyIgnoredDelimApp">
      <ApplicationRef>
        <Reference class="Application" name="MyIgnoredDelimApp"/>
      </ApplicationRef>
    </ManagedResource>
  </ManagedResources>
<!--
  <PlanInitializer>
    <Reference class="sailpoint.object.Rule" name="TraceIntegrationRule">
  </PlanInitializer>
-->
</IntegrationConfig>

If you use the ManagedResources section, the IntegrationConfig will take priority for those applications even if the application itself has a different provisioning pathway configured. If you use the universalManager attribute, the IntegrationConfig becomes the provisioning pathway of last resort instead of manual work items for all applications (if those applications already have non-workitem provioning already configured, they will keep doing that instead). The universalManager attribute and ManagedResources are independent of each other.

Then you need to create the class listed in the executor field. It should implement sailpoint.integration.IntegrationInterface. There are notes for this interface in the javadocs, and you can probably get away with just implementing the provision(ProvisioningPlan) method if you just want to throw them away and return a ProvisioningResult with STATUS_COMMITTED as the status.

3

Hi @uttu2022,
Create a provisioning policy form, may it helpfull