Domain separation and Financial Services Document Processor
Domain separation is supported for Financial Services Document Processor. 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
- 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.
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.
For more information on support levels, see Application support for domain separation.
How domain separation works in Financial Services Document Processor
All Financial Services Operations (FSO) applications are built on top of Customer Service Management (CSM) 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
- sn_doc_processor_category
- sn_doc_processor_type
- sn_doc_processor_m2m_category_type
- sn_doc_processor_attribute
- sn_doc_processor_list
- sn_doc_processor_list_item
- sn_doc_processor_verification_task
- sn_doc_processor_extracted_value
- sn_doc_processor_document
Use cases
- Ability to use in any workflow in Financial Services Operations applications to collect and validate customer documents
- Ability to request deferment or exception of a document.
- When integrated with Document Intelligence, ability to extract and store document data attributes.