Generic Detection

Diagram of Relations Between the Affected CIs:

Required Configuration:

1. The service uses any provisioning workflow.
2. ASQL filter criteria are defined (where expression for SPSCommonClassBase).
3. ASQL target criteria AND/OR ASQL instance criteria are defined (additional columns for SPSCommonClassBase):
   • If Instance/Target is selected in the Apply Cost Center From drop-down, either target criteria or instance criteria must be specified.
   • If Recipient is selected in the Apply Cost Center From drop-down, instance criteria must be specified.
   • If a target is selected in the Required Technical Target drop-down on the Provisioning page, target criteria must be specified.
4. ASQL booking consumer criteria are defined (additional column for SPSCommonClassBase).
5. The ASQL Target column returns SPSTargetingClassTarget.ID.
6. There are any CIs that match the ASQL filter criteria.
7. The ASQL target criteria are mapped to the account or computer relation from the matching CI OR the ASQL instance criteria are mapped to the account or asset relation from the matching CI.
8. Target or instance is assigned to the user.

Optional Configuration:

1. ASQL Custom Comment Statement to insert a custom comment to the newly created service bookings. IF the ASQL Custom Comment Statement is empty, then no custom comment will be added to the new service bookings.
2. ASQL Custom Price Statement to insert a different price to the newly created service bookings. IF the ASQL Custom Price Statement is empty, regular price of the service will be added to the new service bookings.

Detection:

1. Retrieve all CIs that match the ASQL filter criteria.
2. Retrieve all targets from the CIs by applying the ASQL target criteria OR retrieve all instances from the CIs by applying the ASQL instance criteria OR retrieve all booking consumers from the CIs by applying the ASQL booking consumer criteria.
3. Retrieve all main users of the targets or instances.
4. Retrieve all service bookings (without uninstallation booking) for this service.
5. Check for all service bookings if the CIs still match the ASQL filter criteria.
6. If not, create an uninstallation booking.
7. If yes, check the combination of the CI and the ASQL filter criteria within the booking.
8. If wrong, create an uninstallation booking.
9. Continue with detection of missing bookings.