We have 2 endpoint systems that need entitlements passed in a certain order. I do not see anyway to do this in AFX. Is there a way?
We have 2 endpoint systems that need entitlements passed in a certain order. I do not see anyway to do this in AFX. Is there a way?
As Ian said, the only available product feature here is when you have a Create Account and any subsequent access addition to that same account. The product handles that using the Java node you find in the default AFX workflow.
When it comes to cross-application dependencies, it's a bit more tricky.
Having said that, maybe if we understand the big picture we would be able to provide better recommendations. What is the relation between both applications and what type of entitlements and dependencies exist there.
I am not sure that either reply helps in our situation. The situation is - for example: one endpoint is sending across a group and a sub-group. The group has to go first and then the sub-group. These are both in the same request and are part of a employees access into this system when first requested. So the question is: How do we make the group go first and then the sub-group?
Thanks,
Lee
Hi,
tricky. Along with Mostafa's suggestion I would tackle this in the fulfillment workflow. That means you would need to create one new fulfillment workflows, pretty much as 1:1 copy of the out of the box AFX fulfillment. this copy we need to modify and attach to the application/directory that needs its things provisioned last.
It will be a bit convoluted, but doable. I have done similar things before, having one workflow wait for another one. Here things are similar.
You need to have the modified fulfillment workflow do the following
* check if in the same change request there are elements (change request details) for the primary application/directory
* if so, check if they are already PV, pending verification. If not, wait for X minutes. Check again.
* if elements of primary application are PV, then continue with the normal flow of invoking the AFX node etc.
Thinking about it, things don't look that complicated as you are in the same CR.
Frank
Internally for the specific use case "Add account to Group" we do create the Account, then subsequently add the account to the group. This is not a general feature as far as I am aware. Someone else may have a trick to do this.