Unit 2 - Lesson 2 - Client Fundamental 1

Question 1

Define UIM

Answer 1

Curam User Interface Metadata
XML format that describes content and layout of Curam client screens
Best to use XML editor

Question 2

Describe benefits of using interface metadata (UIM)

Answer 2

Ease of development
Increased developer productivity
Promotes consistent user interface
Significantly reduces the number of client bugs
Makes it easier to change between different types of a client

Question 3

Describe the UIM elements that control the look of a page

Answer 3

m

Question 4

Define the use of the Localisation and externalising strings

Answer 4

No hardcoded text in UIM
Localised labels, titles etc stored in .properties file
Each UIM can have more than one .properties file - one per language.
All UIM files have a corresponding properties file.
Set LOCALE_LisT as variable for generators in project’s build.bat. Add locales to the list for another version of pages.
BankAccount_createAccount_en_CA.properties (UIM name + locale)
Generators create all JSPs in locale-specific folder.
URL can be used to specify locale-language version.
Property files are name/value pairs

Question 5

PAGE Element

Answer 5

Root element, everything else is nested within it.
Required attribute: PAGE_ID
Must match the file name in which the PAGE is described.
Used to reference the page from LINKs.

Must have at least 1 child.

Question 6

Describe client generation process

Answer 6

EJBServer/build generated
webclient/build client

Stage 1:
EJBServer build.bat generated -> model.xml & ServerAccessBeans.xml

Client generator. Model.xml & ServerAccessBeans.xml -> Bean generator -> Searver Access Beans (TextHelper) & Bean doc (index.html)

Stage 2:
XML (ServerAccessBeans) + UIMs + Properties -> UIM Compiler -> XML files (Intermediate XML)
(Extracted to webclient/build)

Stage 3:
Intermediate XML run through the JSP generators to create the complete JSPs.
XML file -> JSP Generator -> JSP files, XML file (Catalogue for the Front Controller - Struts-Config.xml)

Question 7

Describe how to use the generated bean document

Answer 7

build beandoc created a HTML version of ServerAccessBeans.xml

Question 8

Connect the client screen to the server side

Answer 8

m

Question 9

Define and use common UIM elements:

Answer 9

PAGE_TITLE - builds the title for a page
CONNECT - Connects to data
SOURCE/TARGET - Specifies if a field is readable or editable
CLUSTER - Groups related data fields and supports complex page layouts
FIELD - Allows display or data entry
PAGE_PARAMETER - Stores key values that are passed into a page
SERVER_INTERFACE - Connects a page to server-side calls

Question 10

PAGE_TITLE element

Answer 10

Display title of the page using Icon, static text and variable text retrieved from the server.

Attributes: DESCRIPTION, STYLE, ICON
Elements: CONNECT

Question 11

CONNECT element

Answer 11

Associates parent element to some data
Can have one or more of:
SOURCE - Where the values come from
TARGET - Where the value goes
INITIAL - A display value you can use to hide the real value

Attributes: NONE
Elements: SOURCE TARGET INITIA:

Question 12

SOURCE element

Answer 12

NAME attribute - one of the following values:
TEXT - To read a property from the properties file
CONSTANT - To read a property from Constants.properties
PAGE - To read a PAGE_PARAMETER of this page
The name of the SERVER_INTERFACE element
PROPERTY attribute:
Qualified name of the attribute or parameter.

Question 13

TARGET element

Answer 13

NAME attribute:
PAGE - To send a PAGE_PARAMETER to another page
The name of the SERVER_INTERFACE element
PROPERTY attribute:
Qualified name of the attribute or parameter.

Question 14

CLUSTER element

Answer 14

Defines the layout for a group of logically related fields.
At least on FIELD and options CONTAINERs.
Can add CLUSTER & LISTS to a cluster to display side by side (needs NUM_COLS set).
Has TITLE attribute and TITLE child element.

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.

Question 15

FIELD element

Answer 15

Defines a data entry or display field and its associated label

Generators create appropriate CONTROL based on property type e.g. checkbox for boolean, hidden stars for SEC_PASSWORD, text fields for Strings and Number.

CONTROL attribute can be set to specify whether code table hierarchies are displayed vertically or horizontally.

Have at least one CONNECT element.

Attributes:
LABEL, WIDTH, WIDTH_UNITS, HEIGHT, ALIGNMENT, USE_DEFAULT, USE_BLANK, CONTROL, DESCRIPTION

Elements:
LABEL, LINK, SCRIPT, CONNECT

Question 16

PAGE_PARAMETER element

Answer 16

Stores key information on a page.
Can be later passed to Server side or other pages as needed.
Declaration of parameter on the current page.
After a parameter is declared, it can be used as the source of a connection by setting the SOURCE NAME attribute to PAGE.

Question 17

SERVER_INTERFACE Element

Answer 17

Element used to access any of the operations or functions described in the ServerAccessBeans.xml.

Attributes:
NAME - a logical name that can be referred to by other elements
CLASS - The Facade Interface
OPERATION - The name of the function
PHASE - The timing of the call to the server. Can be DISPLAY to call it when the page is being loaded, or ACTION to call it when you click a Submit button.

Question 18

CONNECT to pass a value