...
In addition, there are a multitude of settings available. As much as possible, these are managed at a Client level. It's important to note that a Tenant might just simply have one Client only. This is the most common configuration.
Settings are made available for Tenants to configure in several different ways. The way settings are altered is primarily based upon how risky to change or difficult to understand the setting is. In some cases, settings may have direct dependencies on the underlying service layer, which will go through a development process to change.
Self Configuration (Configuration Portal)
QFD includes a configuration portal, commonly referred to as "Config", which allows clients to customize application behavior and user experience. Configuration settings are typically broken down based on transaction type and/or the system/user process that is impacted. Select one of the topics below to browse the available settings.. These settings can be viewed and changed directly by users with appropriate access.
Examples:
- Auto Pay/PC/additional monetary thresholds
- Client logos
- Notification email addresses
- Document requirements
- Regulatory settings
- Approvals
Quavo Configured ("Client Info")
These are settings that are maintained by Quavo staff and can be changed via support ticket. In many cases, changing these settings could have extensive compliance, financial or work management effects. These changes are considered development and will go through Quavo's change process, which includes testing, approval, etc..
Examples:
- Accounting plan/fee mapping
- Available transaction types
- Work queues
- Network/processor settings
- Authentication details
- International settings
Quavo Development (Implementation Change)
Some settings are directly related to service integrations and changes to them require refinement, analysis, development, testing, etc.. minor changes are usually included in your support agreement. Major changes (such as a core conversion, switching networks, etc..) may require a separate engagement.
Examples:
- Transaction type mapping
- Account status codes
- Communication channels
- Letter styling/content changes
- Adding a Client
- Certificate changes
| Child pages (Children Display) |
|---|