Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

Version 1 Current »

Difficulty: novice

Content

Learning Objectives

After reading this article, you will be able to:

  • Create and delete fields.

  • Change access rights on fields.

  • Adjust all settings on fields.

  • Link information between two objects using fields.


What are fields in Workplace

Fields on a page are database information displaying channels. Adding or deleting a field merely adds or removes the opportunity to view the data stored in these data tables. This is contrary to altering the information within a field, which will change the data stored in Workplace’s data tables in real time.

  • In Workplace we know object fields and page fields.

  • In addition, a field can be either a baseline field or a client-specific field.

Object fields

Object fields are fields on an object level, are pre-configured in the baseline and are non-editable (with the exception of client-specific object fields). These fields determine what type of data is possible to display for each and every object.

  • Some of the fields, like reference and create time are available all objects.

  • Most fields however, are specifically designed to display data for one a specific object, e.g. number of persons for a reservation.

When a field is not available for an object as a baseline object field, it might be necessary to create a client-specific field. These fields are created on object level. And can then be added to a specific page (thus becoming page fields). To read more about how to create a client-specific field, see the article about /wiki/spaces/KB/pages/93913144.

Page fields

Page fields are object fields that are assigned to and displayed on a specific page.

A lot of the settings available on objectField level are also available on pageField level.

  • The settings on pageField level override the objectField setting.

  • The access rights are an exception on this. If a user does not have access to the objectField, the user will never be able to get acces to the pageField.

Create and manage page fields

Reminder: baseline pageFields and objectFields cannot be edited.

Open pageField settings

After a field has been created and added to the page, it is still possible to fully customize all settings on a field. To access the settings of a pageField:

  1. Navigate to the page-definition

  2. Fields tab

  3. Click the Magnifying glass of the specific field.


Add a new page field

In order to add a new field to an instance page:

  1. Make sure you are on the instance page you want to edit.

  2. Navigate to the page definition.

  3. Select the Fields tab .

  4. Press Add field.

  5. On the new page that opens, set the object of which you want to add a field.

  6. Set the field. Choose a field by either searching in the search box, or access all available fields using the three dots. Here you will find all the fields that are available for the object.

  7. Optionally you can set a ‘Display type’.
    Usually you can leave this setting empty, in which case the default display type of the objectField is used. You can view this default by pressing the magnifying glass behind ‘Field’.

It is possible to add fields to a baseline page. The options you have for configuring the page layout are however very limited as all baseline fields cannot be configured (for example to change to order).

Delete field from page

To remove a field from a page

  1. Navigate to back-end of the page

  2. Fields tab

  3. Select the field via the checkbox in front of the row

  4. Selection

  5. Delete selected objects

  6. Alternatively you can open the pagefield using the magnifying glass and press the delete button ('x' ) on the top right of the page.

Tip: If you think the page might be used again in the future it advised to just hide the pageField instead of deleting it.

Settings for page fields

 The pageField settings are explained in the tables below.

General

Explanation

Use case

Page

When adding a field to a page, there is an automatically linked between the page and the field. By changing this page, the field will no longer be available on this page.

Mandatory

Object

When adding a field to a page, the object will automatically be filled in. It is possible to change the object to link filels accross objects. (See below).

Mandatory

Field

When an object is linked, it is possible to select which specific field to display. By accessing the three dots on the side, the user gets access to all available fields for the selected object.

Mandatory

Display type

This setting alters the display view of the field. If not otherwise specified, the defualt display type for the field is used automatically. It is possible to override the default setting by choosing a display type from the drop-down menu.

Seldom

Caption

The caption setting is used when creating headers on a page. A header is an overarching label for the following fields or content on the page. The field itself becomes non-functional bold text that can be displayed on the page. It is possible to use translation strings for headers.

Frequent

Text

The text setting is used when creating text on a page. The field itself becomes non-functional normal text that can be displayed on the page. It is possible to use translation strings for text.

Frequent

Tooltip

The tooltip is shown when the user hovers over the hyperlink. The tooltip can include an expression with field such as “{$name} - { $description}.

Instance display

If the field is linked to another object. The pattern defines the view of the related object.

Page field type

The type of page field is automatically determined based on the name of the page. It is possible to override the default by specifying the display type from the drop-down menu.

Barcode scannable

Adds a scanning icon behind an ID field (only!) making it possible to link objects using the QR-code functionality.

Works in conjunction with the QR-code field.

Seldom

Label

Explanation

Use case

Show label 

The label is shown by default. It is possible to hide the lable and only display the data entry.

Frequent

Field label 

Shows the default label of a field. To change the label, an override has to be configured in the “Override label” setting.

Frequent

Override label

To change the default label of a field, the override label setting is used. It is possible to use a translation string for the override.

Frequent

Display

Explanation

Use case

Width 

This setting changes the with of the specific field on this specific page.

Frequent

Height

This setting changes the height of the specific field on this specific page.

Frequent

PDF width 

If lists in PDF format should fit on a page, it is possible to specify a maximum width. The text is wrapped in case it does not fit the maximum width. Note: this functionality only applies for list pages.

Status field

If a field is marked as “status field”, the field defined as the “status field” in the workflow will be visible. The different fields are displayed in a single column.

Show id value

For integration purposes: show the exact database id instead of the name for a related object. Note: only applies for web services.

Pattern 

It is possible to format the field display. This setting works in conjunction with the display type setting under general.

  • For a date type field the Java SimpleDateFormat (yyyy=year, MMM=month, w=week, H=hour, m=minute) can be used.

  • For a number type field the Java DecimalFormat (#.## displays two decimals) (% multiplies by 100 and display percentages) can be used.

  • A special pattern ““ will format and return an empty string.

Frequent

Help 

Some fields come with a pre-defined help text that becomes visible when hovering over them. This setting allows for an override of this help text.

Frequent

CSS

A separate style sheet can be specified for this page.

Linking

Explanation

Use case

Linked to 

Use this setting to directly link the current object’s data table to to another object’s data table.

On a filter page, a linked id field will be matched with the id of the current field.

On a list or instance page, the linked page field gets the ID fields of the linked object.

Seldom

Linked to field

This setting is used in conjunction with the “Linked to” setting. Select the ID field of the linked object from this drop down menu.

Seldom

Back to main object

Link from the main object, instead of trying to resolve external links from the last accessed object.

Seldom

Auto link

Automatically links objects, instead of resolving objects from the last accessed object. NB! Use with caution.

Seldom

Positioning

Explanation

Use case

Row

The row numbering decides the field location on the page. The fields are sorted in an ascending manner. The common practice is to add fields with a row interval of 10. This ensures that it is enough room to add future fields.

Frequent

Column

The column decides the field location of the label. The data entry field will be visible in the following column.

Frequent

Colspan

The colspan decides the with of the field. A field can span 2 or more columns.

Frequent

Order

Multiple fields can be placed in one cell. The field with the lowest number will be shown first.

Frequent

Same cell

By default the label and the data entry field is shown in two separate columns. It is possible to override this and place them in the same cell. Note: These settings require some trial and error.

Frequent

Same table

If a field is placed in a new column, it is added to the top of the page. By turning the setting to “yes” this is avoided and the field is shown in the same table. You can use this setting to show a field next to another field on a page. Note: These settings require some trial and error.

Frequent

Access

Explanation

Use case

Access

It is possible to set the access rights on the field to Full (editable), view and none. When setting the access right to none, the field will no longer be visible on the page. However, it is still possible to use the hidden field to link with other fields.

Frequent

Required

When a field is set to “required”, the user must fill in this specific field in order for any further process on the specific page to be allowed to continue. A required field is represented the asterisk, *, symbol.

Frequent

Visible

It is possible to hide a field on the page, while still being able to use the data entries in formulas. NB! The access should not be set to “none” if it is desired to use this setting.

Frequent

Export

The export setting determines if a field is exportable when generating a PDF, Excel, or CSV file. The export setting is independent from the visible setting. Hidden fields will be visible on a PDF file in case the export is set “yes”.

Frequent

Mobile

It is possible to specify whether or not a field should be visible when using the mobile application of Workplace. It is set to “yes” by default.

Seldom

Viewing

Explanation

Use case

Hierarchy level

This setting only applies to objects that have a hierarchy structure (For instance problem types). The view of the field is sorted in an ascending manner. Hence, the field with the lower number, will be shown before the field with a higher number.

Seldom

Advanced

Show or hide fields on first load. This setting help to reduce clutter on the screen by only showing certain fields when the user wants to see them.

Seldom

Hyperlink

If hyperlink is set to yes, it will be possible to access the object in the list page.

Frequent

Related object view

Determines the visibility of the magnifying glass allowing the user access related objects.

-If set to Never: No users (except the system admin) can see the magnifying glass.

-If set to Always: All users can see the magnifying glass.

Select page

For a screen select you can define a page or a filter that should be invoked to select items.

For example. When selecting a contact in a supplier field, the filter can be configured to only show contacts in the category of suppliers. NB! Do not forget to configure autocomplete if used on fields with the display type “object selection screen”.

Reporting

Explanation

Use case

Parameter

It is possible to create a new parameter that can be used for reports and email messages. This is a free text field. When defining the parameter as “abc”, it can be referred to as {abc} in a report or a template.

Frequent

Formula

Formulas are dynamically evaluated expressions. To see which formulas that are supported, see Home > Help > Admin > Formulas.

Frequent

Settings for object fields

Objectfields also have settings. As the settings of fields are determined on our baselines, they will not be explained in detail. If you’re interested in the setting, you can navigate to the objectField as follows and hover over the setting to view the help text. To view the settings on an objectField:

  1. on your startBoard press the ‘objects’ button

  2. Search for an object

  3. In the result list press the magnifying glass for quick access to the objectFields

  4. Alternatively open the object by pressing the reference and navigate to the Fields tab

Set access to page fields for all users (on a client specific page i.o.w. with an override)

There is a relative simple way to change the access and hide field for all users.

  1. Navigate to back-end of the page

  2. Fields tab

  3. In the column ‘Access' you can change the field access to ;'View’, ‘Full’, or 'None’.

  4. In the column ‘Visible' you can hide the field when visible is set to ‘No’.
    Note: the settings ‘access = none’ and ‘Visible =no’ have the same effect.

Set access rights to page fields per user group (on a baseline page)

Access rights in Workplace can be set on the page field level for specific user groups. This allows Workplace to display the same page, with different content, to different users. To set access rights on a field:

  1. Navigate to the page-definition

  2. Fields tab

  3. press the ‘Field access’ of a pageField at the beginning of the row.

  4. To select which access a user group should have to a field, select one of the options from the drop down menu next to the specific user group.

    1. “None” means that the field will not be visible to users with the specific user group.

    2. “View” means that the field is view-only to users with the specific user group.

    3. “Full” means that the field is editable to users with the specific user group

Remember: a user only needs one user group that has access to a field. So if you want to use this way to hide a fields for user (or make it read-only), you need to make sure that this specific access is applied to all user groups that the user has.

We recommend very limited use of authorizing fields using this method.

Set access rights to object fields per user group (same for baseline and non-baseline pages)

The access on object field can be set in the same way as for page fields.

  1. Navigate to the page-definition

  2. Fields tab

  3. press the magnifying glass in the row ‘field’to open the object field setting

  4. To select which access a user group should have to a field, select one of the options from the drop down menu next to the specific user group.

    1. “None” means that the field will not be visible to users with the specific user group.

    2. “View” means that the field is view-only to users with the specific user group.

    3. “Full” means that the field is editable to users with the specific user group

Be careful setting access on this level. When changing access on this authorization level, you change the access on all pages that use this field. If you for example set the access to ‘None’ for the field request.reference is will be hidden on all pages that this field is used on.

Show information from other objects on your page

It is possible to link two objects via the {object}Id field with the goal of displaying information from a different object. Workplace always looks up when determining what information should displayed. This is easiest explained using an example.

In this example the phone number and email address from the requestor, should be displayed on the Request page . To achieve this:

  1. Add the request.requestorContactId to the page. Note: that the field name ends with contactId (meaning a contact is set in this field);

  2. Directly below this field, add the ‘contact.phone’ field from the Contact object;

  3. Below that the email is added;

  4. Workplace now automatically makes the link between the two field we added of the Contact object and the contactId field that is displayed above these two fields.

By using the fromContactId field, directly followed by the two Contact fields, Workplace knows to show the phone number and email address belonging to the requestor.

Explicitly link fields

As explained above, Workplace looks up to determine what information to show of other objects. However, sometimes you might want to display information from a field.

  • If your fields look as they do in the screenshot below, the phone number of the Property Manager (property.managerContactId) wil be shown on the page.

  • If you want to display the phone number of the Owner instead there are two option:

    • You could switch the order of the Owner and property manager fields;

    • If you do not want to switch the order of the fields, follow the steps describe in steps below.

Steps to explicitly link fields:

  1. Open the settings of the property.phone field by pressing magnifying glass at the beginning of the row in the list with page fields;

  2. Set the ownerContactId in the ‘Linked to’ field

  3. Now select ‘id’ in the ‘Linked to field’.

Summary

  • No labels