---
sourceDocument: Xanadu Financial Services Operations
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/financial-services-operations

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Financial Services Operations

ft:clusterId :

    - finso

bundleId :

    - finso

workflow :

    - Customer and Industry


---

# Domain separation and Financial Services Card Operations

# Domain separation and Financial Services Card Operations {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Domain separation is supported for Financial Services Card Operations. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

## Support level: Basic {#domain-separation-fso-card-operations__section_crd_jrb_5mb}

{#domain-separation-fso-card-operations__domain-sep-supported}  
* Business logic: Ensure that data goes into the proper domain for the application's service provider use cases.
* The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.
* The owner of the instance must set up the application to function across multiple tenants.
{#domain-separation-fso-card-operations__ul_yhr_g2j_xkb}

Sample use case: When a service provider (SP) uses chat to respond to a tenant-customer's
message, the customer must be able to see the SP's response.{#domain-separation-fso-card-operations__p_lsc_nfg_h1c}

For more information on support levels, see [Application support for domain
separation](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=xanadu&pubname=xanadu-platform-security&ft:locale=en-US).{#domain-separation-fso-card-operations__p_msc_nfg_h1c}

## How domain separation works in Financial Services Card Operations {#domain-separation-fso-card-operations__section_tpn_ksb_5mb}

All [FSO integrations](https://servicenow-prod.fluidtopics.net/g9KvqGjOL40ZDwvoXQhMCA "The ServiceNow Financial Services Operations (FSO) solution helps financial services institutions to reduce costs through automation, improve customer satisfaction, and embed risk and compliance controls across workflows. FSO is a cloud-based digital workflow platform that is purpose-built to solve the unique challenges that banks face.") applications are built on top of and use many CSM tables. The key reference tables are the customer tables such as Consumer, Account, and Contact, and these tables are domain-separated.

## Tables {#domain-separation-fso-card-operations__section_blb_cyc_vmb}

All tables added in Card Operations are domain-separated:  
* sn_bom_credit_card_service
* sn_bom_credit_card_task
* sn_bom_credit_asmt_task
* sn_bom_document_task
* sn_bom_credit_card
{#domain-separation-fso-card-operations__ul_fjs_cyc_vmb}  
Note:  
There are two system properties that are not domain-separated for Card Operations:

* sn_bom_credit_card.reserverd_hours_to_unblock_credit_card
* sn_bom_credit_card.reserverd_hours_to_update_credit_limit
{#domain-separation-fso-card-operations__ul_plz_3xc_vmb}

## Use cases {#domain-separation-fso-card-operations__section_ipb_qqb_5mb}

Credit Card Requests
:   There are six different ServiceNow base system request types
    for credit cards:

    *
      * New Credit Card Requests
      * Increase Credit Requests
      * Decrease Credit Requests
      * Block Credit Card Requests
      * Unblock Credit Card Requests
      * Close Credit Card Requests
      {#domain-separation-fso-card-operations__ul_j15_xkd_vmb}
    {#domain-separation-fso-card-operations__ul_i15_xkd_vmb}
:   Customers create these requests from the Customer Service portal
    (activated as a separate plugin)
:   Front office workers (Branch workers, Call Center) create these requests on behalf
    of their customers via the Service Catalog and customer
    interactions
:   Each request type has a dedicated flow that triggers tasks from the parent credit
    card service case.

    * Credit Card Service Cases are assigned to credit card agents, and used to track the overall credit card request and triggers all tasks.
    * Credit Card Tasks are assigned to credit card agents, and used for follow-up tasks that are triggered from credit card service cases.
    * Credit Assessment Tasks are assigned to credit assessment agents, and used in multiple workflows that go beyond credit cards, such as Loan Operations.
    * Document Service Tasks are assigned to document service agents, and used in multiple workflows that go beyond credit cards, such as Loan Operations.
{#domain-separation-fso-card-operations__ul_ajp_ypd_vmb}  
Note:  
Sometimes a ServiceNow® platform feature or application may be able to effectively support service provider use cases even though the domain framework is not being used. In this case, the application may be assigned Basic\*, Standard\*, or Enhanced\* for its domain support level, and include detailed use cases. For example: Before the New York release, Service Catalog had no domain support. But the instance owner was able to configure separate catalogs and items for each customer in a domain-separated instance. This allowed Service Catalog to be used at a Standard support level. To learn more, see domain separation [Application levels of support](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=xanadu&pubname=xanadu-platform-security&ft:locale=en-US).
**Related topics**   

* [Domain separation for service providers](https://www.servicenow.com/docs/access?context=domain-sep-landing-page&version=xanadu&pubname=xanadu-platform-security&ft:locale=en-US)