Each UI project is designed as an extension of the Atoti UI “host application”. This section explains how you can easily combine these extensions into a running Atoti CVA Risk Capital application.Documentation Index
Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt
Use this file to discover all available pages before exploring further.
Activating Atoti CVA risk capital
-
Download and set up the latest version of the Atoti UI starter application.
See the Atoti UI tutorial on how to set up the UI.
-
To activate Atoti CVA Risk Capital, make the following changes:
In
package.json:Inindex.tsx:Inenv.development.jsandenv.production.js, ensure the following exist:- A server used as the Content Server
- An Atoti CVA Risk Capital server with the key “CVARC”
- Build and run the starter, now with the Atoti CVA Risk Capital features enabled.
Configuring Atoti CVA risk capital
The example above activates Atoti CVA Risk Capital with a default configuration and default settings. Here’s how to modify them.Change the configuration
Theconfiguration parameter is the entry-point to configuring the Atoti UI “host application”. It is supplied to the activate function that modifies it to add the Atoti CVA Risk Capital features. If you want to make changes like adding or removing a plugin, changing the application’s title or adding an HOC, you can modify the configuration object after invoking activate.
For example:
Change the settings
Theactivate function accepts a settings and a basSettings argument to let you configure the Atoti CVA Risk Capital features and the BAS features respectively.
You can use the default values exported from the SDK as an override basis:
Combining Atoti CVA risk capital with other solutions or modules
To combine multiple solutions and modules, simply repeat the steps in the combined SDK’s “Activating” section.You can only combine solution SDKs that have an Atoti UI peer dependency equal to 5.2.*.