Handling Displayed as Fields

Contents

• Introduction

• Why use Displayed as fields?

• Displayed as Fields on PageGenerators

• Displayed as Fields in EventHandlers

• Displayed as Fields in Patterns

• Example

Introduction

This document describes how displayed as fields should be handled from within Websydian.

The displayed as triple is used for fields that are displayed in a different format (external format) than they are stored in the database (internal format). A common example is a date field that is stored as a numeric value in the database, but displayed as an ISO date.

In Plex GUI applications displayed as fields are handled automatically by Plex; the source field is automatically removed from the panel, and replaced by the target field by Plex without any action needed from the developer. Plex uses the conversion functions defined by the developer for conversion between the internal and external format.

In Websydian, displayed as fields are also converted automatically. However, it is necessary to handle the removal of the source field and showing the target field manually by adding appropriate triples. In the following sections different scenarios are described, and the actions needed in each case are listed. The last sections contains an example of a PageGenerator with an EventHandler where the triples to handle a displayed as field are added.

For further information on displayed as fields please consult the Plex documentation.

Displayed as Fields on PageGenerators

A PageGenerator with Displayed as fields must inherit from the PageGeneratorWithFieldConversion pattern.

If displayed as field is placed in WsyDetails or WsyGrid, the source field must be placed in OmitDetailsFields or OmitGridFields to prevent it from being displayed on the HTML page. Similarly, the target field must be placed in WsyDetails or WsyGrid for it to be shown on the HTML page.

The tables below show in which variables the source field and the target field should be placed, respectively.

Displayed as Fields in EventHandlers

An EventHandler with fields that differ in external and internal representation must inherit from the EventHandlerWithFieldConversion pattern.

The source field must be added to Hidden to prevent it from appearing as an input field, and the target field must be added to WebInput to make it an input field instead of the source field. If the Integrity pattern is used it is also necessary to place the source field in the ExcludeFromSign variable to avoid signature check on this field (as the value is overwritten by the value of the target field when the conversion is applied).

 The table below shows in which variables the source field and the target field should be placed, respectively.

Displayed as Fields in Patterns

For patterns with scoped PageGenerators and EventHandlers, such as the WebEditSuite, it is necessary to manually perform the changes for all the inherited PageGenerators and EventHandlers as described in the sections above.

Example

This section describes an example with a simple PageGenerator, PG1, that includes a field, Field1, in WsyDetails, and scopes an EventHandler, EH1, that also has Field1 in WebInput.

Without the displayed as triple on Field1 the necessary triples are as listed in the table below:

If Field1 is displayed as Field2, the necessary triples are: