Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

Purpose and use

Placeholders are required so that dynamic data can be displayed in layouts.

Defined placeholders, configured via the Placeholder Definition function on a parent template, such as a layout or a master template, can be provided with the respective data via this function. The data can be generated from Forms or via the Fields function.

Basic structure

Code Block
languagexml
<PlaceholderMappingConfiguration>
  <Mappings>
    <!-- Placeholders -->
  </Mappings>
</PlaceholderDefinitionConfiguration>

...

Attributes

The following attributes must be set for all available element types (Text, Picture):

Attribute name

Description

Name
(required)

Is required for identification. Must not contain any spaces and must be unique.

SourceField
(required)

Is required to map the field from Forms or Fields. Accordingly, the ID of the corresponding field is entered here.

Example

Code Block
languagexml
<PlaceholderMappingConfiguration>
  <Mappings>
    <!-- Data in header -->
    <Text Name="CreateDate"      SourceField="Forms.Date" /><!-- from Forms -->
    <Picture Name="PartnerLogo"  SourceField="PartnerLogo" /><!-- from Fields -->
    <!-- Data in footer -->
    <Text Name="Page"            SourceField="Page" /><!-- from Fields -->
    <Text Name="Footer"          SourceField="Profile.Org.Footer" /><!-- from Benutzerprofil -->
  </Mappings>
</PlaceholderMappingConfiguration>

...