AVQ Zusammenfassung Homepage www.cram.com Teil 2
Karteikarten aus Seite http://www.cram.com/flashcards/export/2711515
Karteikarten aus Seite http://www.cram.com/flashcards/export/2711515
-
- 1 / 170
-
Cartes-fiches
In ENV we have more source types.
It allows us to save and use PL/SQL code.
No, we should say that we can use Excel Files to produce the code that is going to parameterise an Avaloq instance.
Business Type Config (BTC)
BTC sources: They may have all kinds of very different parameterisations; this is why we call them unstructured"."
As many as we want.
Yes, we can.
No, Avaloq only proposes best practices"."
It depends on the workflow that the bank decided to implement.
False: Releases are a set of changes.
False: a service pack is of minor importance than a release.
Yes, it is.
Yes it does. It proposes, for example, a source versioning system.
The following parties are involved: Bank, Avaloq and Implementation Partners.
– Project initiation: Project Setup (Organisation, Project Plan etc.), Analysis & Design: Requirements specification, technical specification, Implementation & parameterisation: Source, finalised technical specification, Testing: Running System, Trans
In contrast to the evolution customer, a product customer can go live with Avaloq based on the delivered CD and possible available Service Packs without requiring further functionality (gaps) to be developed.
A new release of the Avaloq Banking System is rolled out to all customers every spring.
Upgrade initialisation, installation clean–up, parameterisation adaptations, testing, cutover, post–cutover.
– Parameterising the Avaloq Banking System., Discussing parameterisation issues with the bank's key business users and business analyst., Analysing functionality deltas within upgrade projects and defining migration scenarios to bridge them.
– Upgrade specification, Source code according to specification, Detailed technical specification, Input for test manager, use feedback of test manager to fix bugs etc., Input for communicating with Avaloq
A 24/7 information portal and knowledge resource for the Avaloq professional
Have a valid username and login to the Avaloq community
Use search and submit without entering search criteria
Use search and open the drop down field called Release""
Username and password
Avaloq Issue Tool on Avaloq community website.
– Evaluation: GAP, Initial Project and Upgrade Project: all other types of issues
Bugs and Questions
No, it represents just a naming convention but it helps to find the labels of frames in the table OUT_TEXT.
The maximum length of the form order is limited to up to ten characters. If you used the INTL–ID instead of the ID for an object type then you may exceed the number of ten characters.
No, they are not.
No, I do not have to because the compiler assigns the ID in the public ID range.
If not yet implemented it could be necessary to define a frame label in the table OUT_TEXT.
Client specific predefined values require editing more than one source (CODE_CONST_TYPE, CODE_CONST_.[Name of the addition], [the Addition on an object or on an order]).
Text, date, boolean, [name of a code table], obj_[name of the object type], number, code_const.
All the sources required to establish an addition are related to code tables. Therefore you look at the source of type 'code table definition'.
Because almost all rule tables (engines) contain a column to reference classes directly.
No. There is no source on the Avaloq database. So the only way to get the public ID ranges is to look at the documentation 'ID Ranges' (1152).
It is called 'obj_classif_ld'.
– PL/SQL accesses data through SQL queries in contrast to A(valoq) Script. A. Script does not offer direct SQL access., A. Script accesses data through the business objects e.g. Business Partner data, Asset data, etc.) that are exposed by the A. Banking