ServiceNow Integration scenarios and Best Practices with IBM Cloud Pak for AIOps

Question

Servicenow integration with AIOps scenarios :

a) Is the ServiceNow connector limited to ticketing only for incidents, or can it also be used for ticketing alerts?
b) Does the ServiceNow connector support XML communication? The documentation references REST API and JSONATA Mapping. If ServiceNow integration utilizes SOAP/XML endpoints or payloads, can it integrate with AIOps?
c) What is the purpose of the ServiceNow App? Is it intended for ServiceNow to connect with IBM Cloud Pak for AIOps? How does it differ from the connector?
d) When triggering ticket creation, does the JSONATA mapping in the connector define the payload sent to ServiceNow? Can you provide a detailed example payload for reference?
e) How are ticket updates in ServiceNow tracked back to AIOps? Does the connector automatically resync updates, or is additional configuration (such as Impact policies or custom coding) required?
f) Are the workflows for tickets and incidents independent or dependent? Does the incident lifecycle (e.g., in progress, closed, assigned, resolved) impact or associate with the ticket lifecycle?
g) Is there an auto-resync facility available between incident notes and the worklog of ServiceNow tickets when a new alert is added, an alert is cleared, or when an incident is closed/resolved?
h) What is the maximum tested parallel request capacity handled by the connector in a ServiceNow integration?
i) Can the same connector be used for ticket analysis and change risk assessment? Is it necessary to maintain identical payloads for ticket creation and similar incidents, or should multiple instances of the connector be deployed for each purpose?
j) Can the connector support bi-directional integration, allowing updates from both AIOps and ServiceNow to be synchronized automatically?

k)  For the sample payload provided for JSONATA Mapping, is the provided payload the default mapping defined within the connector for every candidate incident configured for ticketing?

l) If you would like to configure Impact, Urgency, and Assignee/Assignment Group during ticket creation. For example, if there is an incident generated for a Link Down alert, and you want the ticket to be created with Impact = High, Urgency = 2-High, and Assignee Group = "IPCore". How can they configure this in the mapping?

m) Since we can use same connector for ticket analysis and change risk assessment, so can the same connector be used for ticket creation (for AIOps incidents) or do we need to have a separate connector exclusively for ticket creations/ updates and another one for ticket analysis and change risk?

n) Similar to netcool where the alarm is cleared but the service now ticket is not closed, alarm remains in the system until we receive the close status updated back to alarm. How can we control the same in AIOps?

o) In case if we need to reopen the service now ticket, how can we pass the updates (severity change, aiops incident status or any other parameters) to service now and will service now consider all these changes while reopening the ticket

p) While two way sync is enabled, if the update is not synchronized back to AIOps, will it try again during next sync or will the failed updates be ignored?