1] What is the nature and description of the request?
The customer is requesting the ability to use Service Catalog Task (SC Task) state changes as event triggers within the Event-Driven Ansible (EDA) Notification integration in ServiceNow. Currently, only state changes at the Service Catalog Request level are supported, which does not provide the necessary granularity for their workflow automation.

2] Why does the customer need this? (List the business requirements here)

• The customer's existing workflows depend on task-level automation within ServiceNow, particularly Service Catalog Tasks, not the broader Service Requests.

• Many of their Service Catalog items consist of sequential tasks, some of which are automated using Ansible, while others require manual intervention.

• State changes at the request level do not provide sufficient detail or control to trigger automation at the correct point in the workflow.

• Migrating their existing automation logic to EDA requires the ability to monitor and act upon changes at the SC Task level to maintain consistency and operational integrity.

• Without SC Task support, the customer cannot fully transition to Event-Driven Ansible and is forced to rely on less efficient and fragmented automation methods.

3] How would you like to achieve this? (List the functional requirements here)

• Add support for triggering webhooks in the Event-Driven Ansible Notification integration based on state changes of individual Service Catalog Tasks (SC Tasks) in ServiceNow.

• Allow users to configure triggers specifically for SC Task state transitions (e.g., from "Open" to "Closed", or "In Progress" to "Completed").

• Ensure webhook payloads include sufficient SC Task context (e.g., task ID, parent request ID, state, assigned user, etc.) to allow Ansible Rulebooks to make decisions based on the task's metadata.