Avaloq ACP

MEM_DOC_EXTN_"namespace"_"name" (e.g. MEM_DOC_EXTN_ACAD_FAVOURITES_XX)

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

It shows information about your assigned orders depending on the expression used.

In the MSG_EXTL_OUT database table.

No, if you are working with Avaloq ice, the rule sets are automatically activated during the installation of the corresponding change. There is no need to manually submit a task.

Known are % * _ ?

XYZ_RULE_LD

We specify the level at and the column in which the variables should appear.

He inherits the strongest general access right of his grantors.

A win definition needs an explicit DDIC binding.

The fields represent the values of a certain business object, which are held in tables on the Avaloq server.

Error codes are parameterised in the code_ui_err table, using sources (code_ui_err.*)

The system checks the rule with the highest priority first, e.g. 9999, until one rule matches.

It is the rule (usually with the lowest priority 0001 and usually with no matching criteria) that always matches. It is normally used to set a standard or default value.

An order is booked as soon as it is verified (transaction-based). An order is booked definitively when the value date is reached (value date-based). Revaluation is possible for value date-based booking.

No. APIs can not only be called from an Avaloq Script package. It is possible to call an API from outside the ABS.

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

For OBJ additions, the format is CODE_OBJ_ADD.{INTL_ID OF CODE_OBJ_TYPE}. e.g. CODE_OBJ_ADD.BP For DOC additions, the format is CODE_DOC_ADD.{INTL_ID OF META_TYP }.e.g. CODE_DOC_ADD.CARD

modify the source code_book_kind (type = code table data)

It's a standard configuration e.g. Boolean values

Single-value keys, Multi-value keys

All Rule Loader tables have the pattern “RULE_LD” included in their name. Rule Loader Views are always based on Rule Loader tables and have the pattern “RULE_LD_V”.

The role of the customisation specialist is to do the customisation. - To create changes - To modify source code - To approve the modifications - To check in tasks

The format for object keys is {NAMESPACE}${INTL_ID OF CODE_OBJ_TYPE}_{DESCRIPTION OF KEY} e.g. ACAD$BP_SYM.

Edit, switch, mandatory

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

A chart of accounts consists of an object (with object type 12 BALSTRU) and all the balance accounts (object type 13). The lowest balance accounts in a chart of accounts are called leaves, the others are called owner.

Override Codes can be translated.

No. Each customer created form is bound to exactly one business type. The only exception is the sub-window (win definition). It is independent from any business type.

You need access codes to protect objects, workflows and other subjects in the Avaloq Banking System (ABS). And you need access codes as well to grant the user access to these protected subjects.

The sequence of the groups and fields are arranged within the subwindows according to the entry in the form_order source code line.

Screen, File, Print, Script, Table.

To provide a maximum degree of usability for the user, you should define the order in which the cursor proceeds through the input fields when the user presses the [TAB] key. You can do this by including a tab order section in the Avaloq Forms source.

Booking is real-time <-> balancing is on demand Booking changes positions <->, balancing shows positions Booking is done on positions <-> balancing is the process of aggregating and valuating positions with the help of balance accounts