Skip to content
Release: Australia · Updated: 2026-07-09 · Official documentation · View source

Sales and Service API Core

Enables seamless tracking and management of Sales Customer Relationship Management workflows through structured inbound and outbound request handling, configurable flow processing, and integration with external systems.

Overview of Sales and Service API Core

The Sales and Service API Core (com.sn_tmt_core) plugin has three key components.

TableDescription
Inbound Request \(sn\_tmt\_core\_inbound\_queue\)Tracks the status of both synchronous and asynchronous flows. It enables agents to monitor the progress of requests and also enables sequential processing of dependent records to maintain data accuracy and consistency. It captures detailed status information for each request. For example, when an order is created from a quote, it logs a confirmation message with the order header number. It also supports archival and cleanup policies enabling organizations to cleanup records by applying different durations for successful and failed requests to optimize data management.
Inbound Request Configuration \(sn\_tmt\_core\_inbound\_queue\_config\)Defines how each flow is processed and tracked. It’s a metadata table that is referenced by the Request Configuration field in the Inbound Request Table. It enables administrators to: - Configure synchronous vs asynchronous processing. - Adapt the Request Tracker across CRM flows. - Set notification types \(default, custom, or none\).
Outbound Request \(sn\_tmt\_core\_outbound\_request\)Facilitates outbound interactions with external Service Order Management \(SOM\). It supports end-to-end order fulfillment via bi-directional REST API integration and requires specific roles.
RoleAccess
sn_tmt_core.adminCreate, read, update, delete, report_view, and report_on
sn_tmt_core.viewerreport_view, report_on, and read

Related topics

Using lead-to-cash foundation applications

Lead-to-cash foundation reference