I do business analysis for a license manager application that is about to be developped; it will manage all software licenses that we allocate to users in our institution.
Of course, the actual allocation takes place in the Administration Panel of that specific vendor - be it Adobe, Microsoft, Cisco, you name it. The app that we design will just aggregate data from the admin dashboards of all these vendors, for accounting purposes.
There are two distinct operations:
A. in the license manager app that we want to be developed, an admin will mark as accepted a user's request for a specific license (as an aftermath, this action is persisted and can later be viewed in a list of approved requests)
B. the admin will effectively allocate the requested license, in the specific administration panel (Adobe, Microsoft)
Normally, if both operations A and B are performed, there should be no problems. But in designing this concept, I fear human errors, such as: admin performs operation A, than receives a phone call to solve a more urgent matter, and later forgets to perform operation B.
No matter which order we enforce through policies - operation A first, and B second, or viceversa - if only one of these operations is performed, that will result in inconsistencies.
Main question: is there any way to enforce that operations A and B always take place together ?
(using REST API calls to pull data from vendor specific admin panel is out of discussion for the moment, given the vast number of software vendors that will be handled)

Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.