Skip to content
Developer resources › Financial Services Operations \(FSO\)
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Using case types and service definitions in FSO

You can use case types and service definitions to define the processes and data needed to resolve customer issues in Financial Services Operations (FSO). The topics in this section provide an overview and discuss choosing which implementation to use in various situations.

  • Case Types in FSO
    Learn about case types, how they’re structured, and how they’re used in Financial Services Operations (FSO).
  • Extending FSO Case Types
    You can extend from existing case types that are provided in Financial Services Operations (FSO) applications, enabling you to take advantage of prebuilt roles, business rules, and other business logic.
  • Creating FSO Case Types
    If you need a new case type that can't be extended from an existing application, you can create one by extending the FSO Base Case (sn_bom_case) table.
  • Service Definitions in FSO
    A service definition describes a service that a financial institution offers to support a product that they sell. Service definitions work with case types to provide different types of support inquiries and unique request and fulfillment processes. In FSO, a sample list of service definitions is preconfigured for each product and line of business.

Parent Topic:Developer guide