Changes or transactions performed on objects are called
In the Avaloq Object Model the and view are split.
The allows bank clients to structure their assets in different portfolios.
A position belongs to one and represents of one asset.
Persons define relations to other persons as well as to accounts (BPs)
The BP object represents the internal account as well as external account (customer contract)
One BP can only have one container
On the MDB the currency is defined through the contract of the money account.
provide structured storage of additional object data for internal use.
Customisation is done by:
Using scripting and uploading
Using scripting and reporting
Using scripting and parameterisation
Using uploading and parameterisation
Code table entries are done through:
Sources of type CODE TABLE DEFINITION
Sources of type CODE TABLE DATA
are the interface between Avaloq Script applications and database
OMD stands for:
Object Modelling Data
Object Modelling Definition
Contents of Avaloq ice installation: , and .
Contents of Avaloq Banking Suite instance.
Client, streams and customisation sources
Business data and customisation sources
Avaloq ice server, workspace and Avaloq source code
Avaloq core data and predefined streams
Avaloq instances are the Avaloq DBs which consist of core data, a defined Avaloq installation, customisation sources and business data.
Avaloq ice are logical entities which organise ABS development.
What has to be created on the Avaloq ice server for the bank?
Client, initial sources, streams/release config and initial users
Tasks, changes, components and MDB sources
Initial sources, streams/release confit and business data
Avaloq is used to develop and store customisation sources and to create installable units for Avaloq .
Defines the initial set and layout in the workbench window.
View
Perspective
Orderbook view
Perspectives are job related combination of views, editors and actions.
Support editors and provide alternative presentations as well as ways to navigate the information in the workbench
Views
Perspectives
Editors
Containers that help organising the work on source code modifications
Tasks
Changes
Tasks have a workflow which consist of several steps and statuses.
The orderbook view is organised with .
What information is displayed in the Instance Information view?
Tasks & changes
Invalids & errors
Background processes & invalids
Tasks & background processes
The version tree can be called from every context menu of a source version.
A closed source is removed from the Avaloq ice server.
It is possible to reopen / revive deleted source.
Possibilities for installing source code on an Avaloq instance:
Remote compilation
Reverse compilation
Create compilation package
Create installation package
OMD sheets are stored in ice.
OMD and LD sheets are Excel files stored with
BIN source type
BTC source type
BTC sources can be compiled to an Avaloq instance.
BTC sources are containers to store script.
Creates, modifies and maintains source code for the system
Developer
Release manager
Task manager
Acceptance tests performed after installation of the change are role of:
Business analyst
Who checks the task in:
Task is the smallest deliverable unit of source code customisation
Task is a medium for moving the source code through the workflow
OMD sheets are hosted as type sources on the Avaloq ice server.
Task can only be checked in when all source code modifications are done.
Relations are connections between the orders.
A business is a structured collection of business functions that are required for a specific role or performed in a certain bank department.
Collections based on search criteria and evaluated upon usage
Dynamic
Static
