Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


Purpose and use

This document function can be used to link content in order to integrate it into the document. Assuming you use the Forms function to retrieve a date and a title and want to place this data together in a footer, you can use this function to combine the two text fields into a separate text field.


Basic structure

<FieldsConfiguration>
  <Fields>
    <!-- Insert form elements and groups here -->
  </Fields>
</FieldsConfiguration>

Elements

Attributes that are offered for all elements:

Attribute name

Description

Name
(required)

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

Text

<FieldsConfiguration>
  <Fields>
    <Text Name="Page" translate-Value="Content.Page" />
  </Fields>
</FieldsConfiguration>

Attributes for Text

Attribute name

Description

Value
(optional)

Predefined text that the user can edit.


Date

<FieldsConfiguration>
  <Fields>
    <Date Name="CreateDate" />
  </Fields>
</FieldsConfiguration>

Attributes for Date

No further attributes


YesNo

<FieldsConfiguration>
  <Fields>
    <YesNo Name="InsertPartnerLogo" Value="true" />
  </Fields>
</FieldsConfiguration>

Attributes for YesNo

Attribute name

Description

Value
(optional)

Predefined value of the entry that the user can edit.


Picture

<FieldsConfiguration>
  <Fields>
    <Picture Name="PartnerLogo" Asset="\\fileshare\PartnerLogo.png" />
  </Fields>
</FieldsConfiguration>

Attributes for Picture

Attribute name

Description

Asset
(optional)

Specification of the drive path to the image. It must be ensured that every user machine can access the image.

Alternatively, an image can be filled with user information via the Code tag:

<Picture Name="SignerImage"><Code>$("Profile.User.Sign")</Code></Picture>


GlobalFields

The GlobalFields element can be used to retrieve a globally stored Field.

<FieldsConfiguration>
  <Fields>
    <GlobalFields Key="Fields.Report" />
  </Fields>
</FieldsConfiguration>

More information about the global configurations can be found here: https://primesoft-group.atlassian.net/wiki/spaces/PDTEN/pages/61407710/Global+Configurations#Working-with-typed-fields.

A concrete example for recognizing the connection between the global entry and the reference to a global entry can be found here: https://primesoft-group.atlassian.net/wiki/spaces/PDTEN/pages/61407710/Global+Configurations#Referencing-global-entries-in-the-templates.

Attributes for GlobalFields

The reference to a global entry is made using the Key attribute. If you select it, a list of all available global entries is automatically displayed.

Attribute name

Description

Key
(required)

The ID of the global entry to be referenced.


Example

<FieldsConfiguration>
  <Fields>
    <!-- Fill placeholders from layout -->
    <Picture Name="PartnerLogo" Asset="\\e123\User\Doe\ExampleLogo.PNG" />
    <Text Name="Page" Value="Page" />
    <!-- Data only in content template -->
    <Text Name="Greeting" translate-Value="Greetings.KindRegards1" />
    <!-- Reference global entry -->
    <GlobalFields Key="Letters.Subject" />
  </Fields>
</FieldsConfiguration>

  • No labels