Documentation Index

Fetch the complete documentation index at: https://help.csgi.com/llms.txt

Use this file to discover all available pages before exploring further.

📢 Announcement:  Xponent Journey Hub, Bill Explainer, and Xponent Communication Control April 2026 (26.1) Release Notes are now available – Check out the latest updates published on April 2026.

Integrations

Prev Next

The Integrations tab provides a consolidated view of the relationship between your Ascendon Listener, Kinesis stream, and event-driven graph. It serves as the operational hub where you can verify listener setup, monitor stream connectivity, and access the associated graph for event processing.

The Integration tab is automatically populated when an Ascendon Listener is created and connected to a Kinesis stream. It helps you verify the configuration and track key metadata, giving you confidence that your event-driven setup is working as intended. It displays the following details:

  • Stream Name - The name of the Kinesis stream created for this listener. This is auto-generated and uniquely tied to the listener.

  • Graph - The graph associated with this listener. This graph contains the event-processing logic and can not be opened directly from this tab.

  • Environment - The environment where the listener is configured. Matches the selection made in the Ascendon configuration. For Example - Default, Non-Prod, Production

  • Product Line - Indicates the product line or business domain the listener is serving.

  • Created At (Local) - The local timestamp of when the listener was created. This helps in tracking and auditing changes.

  • Region - The AWS region where the Kinesis stream is hosted. Important for understanding latency and compliance.

  • IAM Role (ARN) - The Amazon Resource Name of the IAM Role used to access the stream. This is configured during listener setup and is critical for permissions and security validation.

The warning indicator ⚠️ help users clearly differentiate between graph or listener removal scenarios.

  • If a graph is deleted, the associated stream loses its connection entirely. In this case, you’ll need to manually delete the disconnected stream from the Integration module.

    • When creating a new graph, you must create a new stream for it. Existing streams cannot be reused.

  • If the Ascendon Listener is removed or the listener type is changed for a graph, the stream remains disconnected.

    • However, if the Ascendon Listener is added again, the system automatically reuses the existing stream you don’t need to recreate the stream again.

Delete Stream

Deleting Stream will remove its instance within other graphs or versions of this project if used. To confirm you want to delete this stream, type Delete into the text box and click Delete Stream.

Stream Lifecycle & Retention

If you remove the Ascendon Listener and add it again to the same graph, there’s no need to recreate the stream credentials—the system will automatically repopulate them for the listener.

However, if you recreate the listener (even with the same hub and event type), a new stream will be generated with the same name. Previously captured data will not be restored—only newly generated events will be captured going forward.

Information

The Kinesis stream, which powers Ascendon, retains data for 24 hours by default.