Financial Services Customer Lifecycle Operations (CLO) installs automated workflows for reviewing and approving customer account applications. These workflows create cases and route tasks to different agents, including KYC, document, tax, and credit agents.
Build your project structure quickly on the client side (browser) without saving details to the server for each interaction. This prevents time lags after you perform actions in the planning console and improves scheduling performance.
Group multiple MID Servers to form clusters, then configure clusters for fail-over protection or load balancing. Load-balancing clusters automatically balance work between each MID Server to improve stability and performance, as well as handle fail-over.
Several types of components are installed with the Intelligent Task Recommendations components feature, including tables and business rules.Intelligent Task Recommendations uses the following properties.There are two types of recommendation criteria, filter constraints and…
--- title: Tutorial part 4: Install and use a third-party library description: Install a third-party library from Node Package Manager (npm) and use it in a JavaScript module.
Define the fields that you want to map between the universal request and the target table fields that you already configured. This configuration enables you to copy the values of mapped fields from the universal request to the new ticket, and vice versa.
Provides actions for flow designers to use when creating Customer Service Management business processes. Requires the Customer Service Management [com.sn_customerservice] plugin.
Several types of components are installed with the push notifications plugins.These tables are installed with push notifications.These business rules are installed with push notifications.These outbound REST messages are installed with push notifications.These roles are…
Restrict access to subsets of playbook content by pairing a content definition with a filtering rule.
Using an agent or building an integration?
The same documentation is available through the public REST API.
GET /api/docs/search?q=GlideRecord&limit=20
GET /api/docs/document?path=…
GET /api/docs/:id?revision=…
Search returns document paths, IDs, snippets, and an index revision. Read by path for a stable reference; numeric IDs should be used with the returned revision. Document bodies are Markdown.