As enterprises become ecosystems, exchanging work records is increasingly important – bespoke point to point integrations are not the answer, as systems, data, tools, and processes differ. This creates challenges.
ConnectQuick allows organisations to quickly integrate with organisations, partners and suppliers in a standardised, repeatable way. This is a full end-to-end business framework providing a seamless experience for users, while the technical complexity is taken care of by the ConnectQuick integration framework.
Our standard templates allow for integrations to be set up in minutes, and can be configured to meet other organisations' requirements regardless of the system they are using.
ConnectQuick has been developed from good practice shaped over countless integration engagements and we recognise it as a key innovation for organisations on a Service Integration and Management (SIAM) journey.
ConnectQuick provides:
- Rapid connections – Configure an integration in minutes using our standard templates.
- Seamless user experience - Simply assign the record to the external team and the integration will be taken care of.
- Enterprise functionality out of the box - Handle complex scenarios such as multiple reassignments, multiple integrations, error handling, logging and more out of the box.
- Simplify support and reduce technical debt - A common framework and pattern with support available from our App support team, provides reduced technical debt and overhead.
- Reduce expense - Swap customers and providers with ease, eliminating costly integration projects. No need for both parties to use the app.
Summary:
- Link an integration with an assignment group so all work is seamlessly routed to the external system or embed ConnectQuick into your custom Flow as an Integration Hub spoke
- No need to alter existing workflows or fields
- Handles complex multi-party integrations
- Secure information through Basic or Oauth 2.0 authentication
- Pre-configured templates available
- Fully configurable mappings and extensive transaction logging, with automated error handling.
Supported patterns:
Available work records that can be integrated:
- Incident, Request, Problem, Change
- Any record extended from Task in global scope
- Please contact us to enquire about expansion packs to use ConnectQuick with other ServiceNow Products such as CSM Case, FSM Work Order, HR Case etc.
Use cases supported:
- Consumer/provider - where one system is fulfilling work for another (default typical integration scenario between two or more parties)
- Sync - mirroring a ticket in another system (e.g. where a team wants to track their work in another system)
- Direct - integration directly updates the target record independently (e.g. one-way read-only updates)
- Flow - any of the above in a flow, using ConnectQuick as an IntegrationHub Spoke (consumes IH transactions)
Available methods:
- API - REST
- API - SOAP
- Email (to system)
- Service Bridge
Available formats:
- JSON
- XML
- Key:Value pairs
- Binary (attachments)
Any combination of the above is supported (including multiple at the same time).
Features:
- Can handle complex payloads and updating of multiple records
- MSP ready - supports Domain Separated instances
- Common security framework with zero-permissions model - external users can only act in accordance with the definition configured
- Logging and configurable error handling - automated transaction replay for delivery failures, can raise a record of choice (e.g. raise an Incident & dynamically assign it based on the error type), or notify an administrator of any integration failures
- Handles common failure scenarios automatically: optional flood prevention, duplicate prevention, reference ID fallbacks, monitoring alerts. Ability to configure response messages using mappings
- One-click documentation generation - one-click creation of API specifications based on the configured integration
- User input validation - specify required fields from your users to be able to trigger an integration to give the other party receives the information they need
- Dashboard to monitor transactions, errors and latency
Version 4.3 adds a number of new configuration options for even greater versatility
- New dashboard to monitor integration timings and latency
- Improved logic for structured records (with flows like Request). The flow can create a blank task assigned to the integration user and CQ can do all the field population; simplifying the task of designing flows.
- Conditional integration: powerful feature to allow multiple definitions to be processed based on conditions. Great for mapping different fields for different catalogue items.
- Binary attachment processing allowing integration with cloud storage providers
- Validation now extended to work within nested payloads
- Configure error responses using mappings to return specific messages for the other system to process
- Internal integrations with CQ possible through the spoke. Example use case with SFTP integration.
Version 4.2.1 enhances several features to support document generation and testing
- Sample value generation from a specified record to reduce manual effort to specify this for documentation
- Enhancements to generate sample payload functionality; simpler interface that supports Create and Update payloads.
- Spoke enhancements: option to override payload from flow
- Logging enhancements & bug fixes
- Improved installation process with the new Global Component Installer standard from ServiceNow
Version 4.1 adds advanced error handling and performance enhancements
- Alerts can be raised on any table from integration errors with the payload mapped to the table (e.g. raise an Incident)
- Emails can be sent to a specified mailbox
- Errors are indexed to prevent floods of error messages based on the selected conditions (Generally for any errors, for specified HTTP codes, and/or specified custom payload values)
- Mappings can also be used to enrich the alert (e.g. set an assignment group to route an alert for a team to fix)
Version 4.0 adds significant additional functionality
- Data types for mapping (ability to handle complex payloads)
- Timeout & retry policy
- Variables can now be mapped
- Flow step/spoke
- REST: GET
- Synchronous option
Version 3.4 adds further resiliance measures and support for empty fields
Version 3.3 adds no-code conversion to mappings, for instance to convert state values
Version 3.2 adds automated error handling options for duplicates and flood prevention, as well as monitoring alerts and the final use case: direct integration.
Version 3.1 added additional logging and error handling
Version 3.0 is a major feature upgrade which adds significant flexibility to the framework (see features list) and support for Managed Service Providers using Domain Separation.
ServiceNow Core Platform