Install Trend
View Install Data
| Date | Install Count | Change |
|---|---|---|
| 2026-09-09 | 0 | - |
| 134 days of no change | ||
| 2026-04-27 | 23 | -23 |
| 19 days of no change | ||
| 2026-04-07 | 24 | -1 |
| 66 days of no change | ||
| 2026-01-30 | 25 | -1 |
| 4 days of no change | ||
| 2026-01-25 | 26 | -1 |
| 24 days of no change | ||
| 2025-12-31 | 28 | -2 |
| 111 days of no change | ||
| 2025-09-10 | 27 | +1 |
| 6 days of no change | ||
| 2025-09-03 | 26 | +1 |
| 43 days of no change | ||
| 2025-07-21 | 25 | +1 |
| 55 days of no change | ||
| 2025-05-26 | 24 | +1 |
| 4 days of no change | ||
| 2025-05-21 | 23 | +1 |
| 43 days of no change | ||
| 2025-04-07 | 22 | +1 |
| 158 days of no change | ||
| 2024-10-30 | 20 | +2 |
About
Kyndryl Integration - Incident Inbound is built to standardize all incident inbound integrations using Web Services that acts as publisher for all external tools. Incident inbound integration can be setup quickly using a properties console. This app also enables a developer to configure the integration based on specific customer requirements.
Key Features
- Based on **Publisher/Consumer concept** , inbound into this instance (Publisher) uses generic processing that all incident integrations are supposed to abide by.
- There is no unique custom code for each integration.
- Defaults and options are managed by configurable properties and not hardcoded.
- Fully utilizes the ServiceNow platform features (OAuth/Basic Authentication, Web Services, Import Sets, Transform Maps etc) and builds on top of them.
- All coding leverages ServiceNow’s no code/low code **Flow Designer**.
- Full support for both **Domain Separated Instances and Dedicated Instances**.
- Specific **security** role for Incident Integration.
- Clear JSON (or XML) responses.
- If configured, **enforces OAuth**.
- **Defaults** are applied at different stages of life cycle of the record. If the payload contains no value or incorrect value, defaults are applied based on the State of the record.
- Defaults can be specified at the global level or at a sub-parent domain level for Domain Separated Instances.
- Inbound – Easy consistent transformation for fields with numeric values
- Various ServiceNow instances may have customized State, Onhold numeric values.
- Application provides easy English labels (new, inprogress, onhold, resolved, closed, cancelled) so that numeric values for that ServiceNow instance can be locally set via a property so that Sub-flows & Actions don’t need to be updated.
- Inbound - Set external tool number fields
- Usually ServiceNow instances have multiple ITSM integrations
- Using properties, each & every external tool number can be saved in a specific ITSM field without updating Flow Designer. If no specific field is used, Correlation display & Correlation ID are used.
- Inbound – Support for “misrouted tickets”
- Built-in code to reassign the ticket and break the bond so that no further updates will bridge to that external tool.