ADE Flashcards
CONNECT element
Associate parent element to some data
Can have one or more of: source, target, initial
Can pass page parameter to a server interface
Can make Field editable if Connect includes Target
SOURCE, TARGET elements
Source name: Text (from property file), Constant (from Constants.priperties), Page (page parameter), Server Interface
Target name: Page (sets other pages Page Parameter), Server Interface
PROPERTY attribute is the qualified name of the attribute parameter
CLUSTER element
Defines the layout of logically related fields
Attributes: title, description, width, label width, show labels, num cols, style behaviour, layout order, summary, scroll height
ELEMENTS: field, container, action set, cluster, list, condition, description, widget
FIELD element
Data entry or display field and its associated label
Control attribute specifies type of field
Usually has one connect element
USE_BLANK for code table drop downs or server interface lists.
HEIGHT more then 1 displays multiple code table entries.
USE_DEFAULT can be set to force user to select a value.
PAGE PARAMETER element
Used to store key information on a page
Declares parameter of the current page
Build commands client
Beandoc - creates HTML version of ServerAccessBeans.xml
Inserttabconfiguration (
Sub target of DB) populates APPRESOURCE table with tab and menu information
SERVER INTERFACE Element
Name - logical name to be referred by
Class - the Facade interface
Operation - name of the function (method name)
Phase - display (on load) or action (submit)
ACTION SET element
Groups ACTION CONTROLs
Style depends on location within the page
Upon failed condition with Hide conditional links attribute in curam configure xml - link is displayed disabled
ACTION CONTROL Element
Represents a control (button, hyperlink)
Types:
Action: a link to another page
Submit: used to create a button to call Action phase server interface
Dismiss: used to create a button that closes a pop up page
Submit and Dismiss
File Download
LINK element
Mainly used to connect to another page
Normally child of ACTION CONTROL ( can be inside Field - dis lays a hyperlink )
Link invoked after SERVER Interface - which can be used to populate page parameter in turn
PAGE ID THIS points to itself
OPEN MODAL
Read multi Max
RSA Readmulti_max=60
Bootstrap.properties curam.db.readmultimax=100
Handling based on Readmulti_informational
(Readmulti, nsreadmulti, nkreadmulti, nsmulti)
Setting zero is treated as infinity.
If not set, default value from Curam Generator application.properties is used and exception is thrown.
In RSA, If Readmulti_informational is not enabled - Readmulti_max message gets logged and all records are returned.
If enabled, can be added to the Informational Manager for handling in Facade layer. Max number of records is returned.
Pagination
Global set in curam-confit.xml
Pagination true/false
DEFAULT_PAGE_SIZE number of rows displayed by default
PAGINATION_THRESHOLD minimum list size before pagination is enabled
Can be defined by LIST attribute in UIM/VIM. Page level definition overrides global definition.
Optimistic Locking
RSA set ALLOW_OPTIMISTIC_LOCKING on the entity
Set OPTIMISTIC_LOCKING on the modify operation
Multiple access, only one commit at a time.
Modify, nkmodify, nsmodify
Insert automatically populates and initialises the version number of the record.
Nsinsert has to revise version number in the details.
Version number is based on the domain definition VERSION NO
All OOTB tables have OL turned on by default.
Code table
Facilitates restriction of data.
Each entry contains code, description and language setting.
Codes appear in Cúram drop-down fields on the client.
Can be accessed programmatically.
Codes are to be unique within a table.
New custom entries - use different letter prefix for the entries.
Stored in DB as code table header, item and hierarchy.
Generating code tables
ctgen
Merges code table definitions according to component order
Translates resultant merged file in a java source code and sql
SQL artefacts are generated into server/build/svr/code table/SQL
Generated Java code compiled and packed into server/build/jar/codetable.jar
Must be followed by a database build
Also a build client for client to pick up changes
Code table hierarchy
Multiple code tables linked into several levels
Y selecting code at one level, you reduce number of codes at the next level
Lowest level code is returned and store, parents can be found via the code table API.
The FIELD attribute has a CONTROL attribute CT_HIERARCHY_HORIZONTAL to display horizontal hierarchy (default behaviour) and CT_HIERARCHY_VERTICAL for the vertical hierarchy.
Data manager
Tool to create database and load initial and test data.
Included SDEJ infrastructure tables (tables, indexes and constraints)
Application tables from .xml extracted from the model by generators.
Initial data.
Test data.
Contains:
Configuration file
ANT target
Large Object Manager (binary BLOB e.g. images and character CLOB e.g. Rules XML)
datamanager_config.xml is used to identify targets to includes and errors to ignore.
Application Navigation
Defined in configuration files (tab folder)
.app .sec .ssp .tab .nam .mnu
During build loaded to DB
Configuring application navigation
ID attribute must match file name
Localised via properties
Schema used to validate namespace
.app application-view.xsd
Defines application banner, referenced sections and application search.
.sec section.xsd
Defines referenced tabs and section shortcut panel in a section.
.ssp section-shortcut-panel.xsd
Defines the contents of a section shortcut panel.
.tab tab.xsd
Defines a tab, including context panel and referenced navigation and actions menu.
.nav navigation.xsd
Defines the content of a navigation tab.
.mnu menubar.xsd
Defines the content of a tab actions menu.