Ability to chain or order when system tasks process

[jcolemn3]

Does the ability exist to chain or order when system tasks process? For instance, I have Business Adapter B that might depend on Business Adapter A to run completely. I want Business Adapter B to only run once Business Adapter A has finished. Does this exist? The scheduling capabilities in the beacon has no bearing on when a task will finish or in some cases when the task will start processing.

It would be nice to have the ability to chain or establish dependencies on other tasks.

[ChrisG]

In short, I can't think of any robust approach to directly achieve an ordering like you describe sorry.

I would guess (but haven't tested) that adapters will typically start running in the Flexera One environment in the order that the data is uploaded from your environment. But I don't know of any way to guarantee that one adapter won't start to run until another adapter has finished, beyond the brute force approach of manually checking that the first adapter has completed before running the 2nd adapter on the beacon. That obviously isn't feasible for an automated/hands-off operation.

In principle (best practice), adapters should be designed so that the order of execution does not matter, although I can imagine there may be scenarios where this principle may be hard to realize.

[jcolemn3 · Accepted solution]

Thanks @ChrisG 

---

In principle (best practice), adapters should be designed so that the order of execution does not matter, although I can imagine there may be scenarios where this principle may be hard to realize.

---

 This has been the general principle. However, we're dealing with the domain name limitation for Intune which is compounded by other variances in domain name for inventory pulled from the Flexera agent itself. So, we're battling two processes that are updating the machine domain names with different values. So, the need to chain an update to the machine domain name after these processes have completed will be essential in ensuring license checks work properly. Unless of course, there is a way to remove the need to factor in machine domain when doing license reservations and checks from app broker??