ACP (Comprehension Checks)

A static data order creates or modifies an object.

Normally a transaction order generates bookings

Wherever there is a context menu on the Avaloq GUI (Graphical User Interface) available and the user has the access right to perform this context action.

Yes, we call these functions in Avaloq the field validation and the order validation.

If you have access to more than one business unit, the Application Start window will open automatically after entering your login credentials (user & password).

The Recent Orders report shows orders that were created recently. It opens in a new tab in the main window by default when you start the SmartClient.

Yes, this is possible with context action in the navigator window.

Yes, you can set up, store and manage individual filter criteria with the use of templates, layouts and parameters in the task and reporting desk.

Orders. Any changes or transactions you perform on objects are called orders.

A new bank client will be opened typically with all bank required personal data. Regarding the object model you create in Avaloq usually a Person (PERS) with Address (ADDR), a Business Partner (BP), a Container (CONT) and a Money Account (MACC) to start a business relationship with a new bank client.

? Beneficial owner ("wirtschaftlich Berechtiger", "Niessbrauchberechtiger") ? Account owner (contracting partner) ? Payee within the scope of EUSD ? Authority (person to business partner) ("Bevollmächtigter") ? Legal guardian (person to person) ("gesetzlicher Vertreter", "Vormund")

The Business Partner (BP) object represents the customer contract (i.e. the account - internal as well as external). The customer relationship and customer contract are defined on the Business Partner.

Yes, of course. This will be designed with the business operation model of the bank or in other cases potentially regarding individual client instructions.

On the Model Bank (MDB) the currency is defined through the contract of the money account.

In the Avaloq object model the internal and externalview are split. The container allows bank clients to structure their assets in different portfolios for different reasons. A position belongs to one containerand represents a quantityof one asset.

Classifications and classes, keys, additions, remarks, relations, collections.

Remarks provide structured storage of additional object data for internal use. They serve informational purposes only, contain free-format text and can be defined with a valid-to date.

The purpose of relations is to logically link objects.

Dynamic Collections & Static Collections.

Relations are always between two objects.

Lookup forms are special forms used to search for objects.

No, screen reports show read-only data (e. g. reports or lists). In the Report Writer course you will learn, how to create reports.

Users can sort a screen report by a selected column if sorting is enabled by parameterisation.

If an input is required the filed will be coloured light orange, with a dark orange border.

See doc.ID 2352 pages 59-60 for possibilities

The system allows the use of various wildcard characters in search fields. Known are % * _ ? and : (see doc.ID 2352 page 61-62)

The elements of a desk are: sidebar, work area and favourites button.

No, Avaloq delivers an MDB, which is usually the basis for the parameterisation in the implementation project.

Parameterisation means the setting of parameters, scripting means the enhancement of functionality, usually with Avaloq Script.

Yes, with Avaloq Script (e.g. in order validation, reports, etc.)

No, it depends on the area of customisation and on that what you want to have as a result.

Correct answer is: c

False. Sources are never written in PL/SQL.

Sources can be found within the ABS using the Task& Reporting Desk or the Parameterisation Desk. In Avaloq ice sources can be found in the Sources View.