What is the nature and description of the request?
Customer would like the Org level host limits to be tied to the total number of inventory items automated at the Org level. They asked if this could be changed to work more like the way subscriptions work in that the controller will only go into an out-of-compliance state if the number of hosts automated against is greater than the number of subscriptions allocated to the controller.
Why does the customer need this? (List the business requirements here)
The Accenture group that manages AAP is a central organization that provides AAP as a service to other organizations within customer. When they pull in inventory items from their SNow environment the inventory items come in without tags to allow them to partition the inventory or filter down that larger inventory. So, each org has a total number of inventory items larger than the org limit, and when this is the case automation is not possible for that org. Filtering is currently done within the playbooks. We are working with the customer to change this approach, but the customer's SNow team is not yet willing to make any changes for the AAP team.
How would you like to achieve this? (List the functional requirements here)
We see a couple of options. The first is the change the meaning of the Org Inventory Limit. I'm not a big fan of changing an interface such as this as it could impact others that rely on this behavior. The second approach is to add an option to control the meaning of the org limit to be either a total inventory limit current behavior and default) or to limit against the number of items automated against at the org level.
List any affected known dependencies: Doc, UI etc..