Application Dependency

Which IIQ version are you inquiring about?

8.4p1

I have the following structure in the application dependencies in the provisioning policies:

  1. Application Y has a dependency on Application X
  2. Application Z has a dependency on Application Y .

Now I want to add another dependency on Application Z to be X.

Now I’m getting circular dependency on Y.

I dont understand why there is a circular dependency. Any help?

It looks like the circular dependency is happening because of how the applications are linked together:

  • Application Y depends on Application X.
  • Application Z depends on Application Y.
  • Now you’re trying to make Z also depend on X.

This as a loop because Z is already indirectly depending on X through Y, and adding a direct link to X creates a cycle:
Z → Y → X → Z, which triggers the circular dependency

Quick Fix:

  • You might not need to add X as a direct dependency for Z, since Z already gets it through Y.
  • Or, if possible, try flattening the structure a bit. Instead of chaining the apps, you could make X a shared dependency for both Y and Z separately.

Hello @vkaushik,

Thank you for response.

I’m using it in the provisioning policy values (I know we can populate the values using rules but it’s just easier)

When I don’t add Application X into Application Z, it’s not appearing in the options.

Also, from what I understand its Structured like this:

Z → Y → X,
Z → X

1 Like

I think it’s better to use a rule to populate the values. Instead of relying on a static dependency chain, you could use a rule to populate X for Z when Y is selected. This avoids having to directly link X to Z in the provisioning policies and helps SailPoint understand the context without creating a circular dependency.

Even though Z → Y → X looks straightforward, SailPoint might be recognizing that Application Z now has two paths to X: one through Y and one directly from Z. This dual path can cause confusion and be flagged as a circular dependency.

2 Likes

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.