After Provisioning rule to create work item

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
8

Building on @neel193’s snippet, since you only want this once the account Create comes back committed, I would add the check before the launch and let the async part run through RequestManager

for (AccountRequest ar : plan.getAccountRequests()) {

    if (AccountRequest.Operation.Create.equals(ar.getOperation())) {

        ProvisioningResult pr = ar.getResult();
        if (pr == null) {
            pr = plan.getResult();
        }

        if (pr != null &&
            ProvisioningResult.STATUS_COMMITTED.equals(pr.getStatus())) {

            String workflowName = "Create Support WorkItem";
            long launchTime = System.currentTimeMillis() + 5000;
            String caseName = "Post-Provisioning Task: "
                    + ar.getApplicationName() + " (" + launchTime + ")";

            Attributes reqArgs = new Attributes();
            reqArgs.put(StandardWorkflowHandler.ARG_REQUEST_DEFINITION,
                        WorkflowRequestExecutor.DEFINITION_NAME);
            reqArgs.put(StandardWorkflowHandler.ARG_WORKFLOW, workflowName);
            reqArgs.put(StandardWorkflowHandler.ARG_REQUEST_NAME, caseName);

            Attributes wfArgs = new Attributes();
            if (plan.getIdentity() != null) {
                wfArgs.put("identityName", plan.getIdentity().getName());
            }
            wfArgs.put("applicationName", ar.getApplicationName());
            wfArgs.put("nativeIdentity", ar.getNativeIdentity());

            reqArgs.putAll(wfArgs);

            RequestDefinition reqDef =
                context.getObject(RequestDefinition.class, "Workflow Request");

            Request req = new Request();
            req.setDefinition(reqDef);
            req.setEventDate(new Date(launchTime));
            req.setName(caseName);
            req.setAttributes(reqDef, reqArgs);

            RequestManager.addRequest(context, req);
        }
    }
}

The Committed check should keep it from launching for a merely Queued result, preferring the specific AccountRequest result where the connector provides one and falling back to the plan-level result otherwise. The idea would be for the Create Support WorkItem workflow to accept identityName, applicationName, and nativeIdentity and create the support work item there.

On the imports, the wildcards @neel193 listed cover most of this. Since AccountRequest is a nested class, you would still need:

import sailpoint.object.ProvisioningPlan.AccountRequest;
import sailpoint.request.WorkflowRequestExecutor;
import sailpoint.workflow.StandardWorkflowHandler;

This roughly follows the async RequestManager pattern shown here, so it would be worth testing against your connector before relying on it.