Metadata

Access  ARCAD-API Server Metadata Designer

The 5250 flow does not contain any functional information about what is displayed on screen. It only contains information about what must be displayed and how it must be displayed (character, display attributes, etc.). APIs must be able to interpret data displayed on the 5250 screen. To do this, you must assign IDs to the areas on your screen that contain data that the web service needs to interpret.

ARCAD-API allows you to assign functional attributes to specific areas in the 5250 screen. A screen area is a rectangle drawn on screen that delimits the portion of text to identify. This means that you can select a certain area in the emulator, that corresponds to a field in your application, and attribute an ID. These IDs are called metadata. Metadata identify one or more screen area(s).

Metadata IDs are used when designing scenarios for your web service. When a web service calls a metadata ID, the data contained in the related screen area(s) can be extracted from the 5252-flow and interpreted or manipulated if there are values to input in a given field.

Example

The Customer ID in your application is displayed on line 4, columns 5 to 10 of a given screen. The only information you can get at the 5250 flow level is the character sequence and the related display attributes. You need to create an ID that allows you to know where the Customer ID is found in your emulator on each given screen.

To assign a functional ID to an area of a screen, use the metadata designer to draw a rectangle around the area and assign a metadata ID.

Example

Two different users can run the same scenario using two different user accounts because the user and password fields are metadata. When executing the scenario via the web service, they each enter their own user/password and, via the metadata ID's, the system automatically replaces the scenario's values with the input values.

ARCAD-API can assign different types of metadata:

  • screens: a screen ID is created by one or more screen areas that allow you to identify a unique screen. The combination of the areas defined for a screen ID and their relative positions must be unique for each screen. This means that this combination of areas can only be found on this screen. The screen ID is important because it is the parent ID for all other metadata.
  • fields: a field ID defines a specific screen area that contains individual data.
  • lists: a list ID defines a portion of the screen that is used to display a list of items as a table. A list's area must cover the entire portion of screen that is used to display the elements of the table.
    • columns in lists: a column ID defines the area that covers one column in a list. The column's area must be included in the area covered by the parent list ID.
    • end of list messages: an end of list ID defines the portion of the screen where a message appears when the end of the list is reached. The text value that will be displayed when the end of the list has been reached while browsing the entire element of the table may not be found on the same screen as the parent list if the list flows over multiple screens.

The Metadata designer

The metadata designer allows you to assign IDs in advance. Pre-defined metadata are available in the scenario designer. Metadata can also be created while you are recording scenarios in the scenario designer, however creating them in advance via the simplified metadata designer may save you time. There is also a possibility to duplicate metadata that are reused from on screen to another.

Note

The F2, F5 and F12 keys can be used inside the emulator because they have been removed from the standard key binding context.