These data items use only one component to display and store data.
| Use type... | If you want to... | Sort and filter in list form |
|---|---|---|
| Date | Display a date. You can configure:
The date is stored as a string in the ISO 8601 UTC format. For more information on how these fields work with time zones, see the Date and time considerations topic. | Yes* |
| DateTime | Display a date and time. You can configure:
The date and time are stored in the ISO 8601 UTC format. For more information on how these fields work with time zones, see the Date and time considerations topic. | Yes* |
Display an email address as a link that can be clicked to compose mail to the address. This data item validates that the values contain all components of a well-formed email address. You can configure:
| Yes* | |
| Label | Display a label for form and row actions used to initiate manual transitions. Once the data item has been created, reference it in the Action Label field to change the default button text. | Yes* |
| Message | Create a message for the user. This data item is used exclusively in logic blocks to give an error, warning, or success message to the user. | No |
| Number | Display a number. You can configure:
| Yes* |
| Phone | Display a phone number with a phone icon that brings up a menu with Call and Message options. You can use those options if your browser and operating system supports them. | Yes* |
| Static Text | Create non-editable text that displays directly on the form without being bound to a text box or text area. The synonym label and help text bubble for the data item does not show in the application. The text entered in the help text field is what displays. You can configure:
Learn more in the Static Text data item configuration topic. | No |
| Text | Create a text field with a single line. You can configure:
| Yes* |
| Text Area | Create a text box. This data item is similar to the text field, but with more space. You can configure:
Text area fields have a limit of 3,000 characters. | Yes |
| Text Editor | Create text box for rich text. This text editor provides full text formatting. You can format:
Text editor fields have a limit of 1,000,000 characters. | No |
| Time | Display a time in a desired format. You can configure a time type data item to capture either:
For more information on how these fields work with time zones, see the Date and time considerations topic. | Yes |
| Translatable Text [Limited Use] | Create a text field with a single line that can be translated into other languages. You can configure:
Logic Block support for Translatable Text data item type is limited. | Yes |
| Translatable Text Area [Limited Use] | Create a text box that can be translated into other languages. This data item is similar to the text field,
Logic Block support for Translatable Text Area data item type is limited. | Yes |
| Translatable Text Editor [Limited Use] | Create text box for rich text that can be translated into other languages. This text editor provides
Logic Block support for Translatable Text Editor data item type is limited. | No |
| True False | Create a checkbox. The checkbox evaluates to
| Yes* |
| Web Link | Display a web address as a link that can be clicked to open the page. You can configure:
| Yes |
These data items use multiple components to display and store data.
| Use type... | If you want to... | Filterable in list form |
|---|---|---|
Address | Address fields are complex data items which enable users to enter multiple lines of information that are stored as a single value. Address fields have one, or many, format definitions available for users to select from. Each format definition is delivered with component lines that prompt users for the information needed to complete the address. For example, one format definition may have component lines for City, State, and Postal Code while another may have lines for Street Number, Street Name, and City. How the field was configured controls whether a format definition is defaulted into the field or if users can select from a dropdown list of available formats. Learn more in Configure format definitions. | Yes* |
| Color | Use a color as a supplementary aid or an aspect of brand identity. This data item type is currently used exclusively for themes. You can configure:
| No |
| Currency | Display money of any currency. This data item combines a number with a set decimal precision and currency code. The currencies available are controlled for the zone by the currency manager application. You can configure:
You can learn more about currency rules in the Currency math topic. | Yes |
| Expression [Limited Use] | Store a FEEL expression which can be used to define metadata, such as decisions. This data item type is for internal use only. | No |
| Inline Filter | Add a data item to your application that stores filter criteria. Inline filters are configured with fields, operators, and values, just like filters on list forms. When a user creates a record and configures the inline filter field with the desired operators and values, those selections are saved as part of the record. Learn more in Advanced Filter. Inline filters enable you to pass a record to a logic block and use the filter criteria saved in the record to filter fetched data. Learn more in Inline Filter data item configuration. For example, when working with inventory in a warehouse, workers pick inventory in groupings called waves. Waves optimize the warehouse pickers movements by grouping items from multiple orders which need to be shipped. In an application which manages waves, an inline filter data item could be configured that enables users to define the filter criteria for what should be included in each wave record. One wave record could define filter criteria that states all priority mail shipments due to be shipped today should be picked in a wave, while another could specify any standard mail shipments due to be mailed in the next three days should be picked as a wave. | No |
| Name | Name fields are complex data items which enable users to enter multiple lines of information that are stored as a single value. Name fields have one, or many, format definitions available for users to select from. Each format definition is delivered with component lines that prompt users for the information needed to complete the name. For example, one format definition may have component lines for First Name and Surname, while another may have lines for Title Before Name and Surname. How the field was configured controls whether a format definition is defaulted into the field or if users can select from a dropdown list of available formats. Learn more in Configure format definitions. | Yes* |
| Picture | Display a picture, or create a signature field for your records. Pictures have a size limit of 350 KB. You can configure:
For example, you can use Picture data items to add a logo to a company record in the directory. These logos can then be used in reports. Learn more in Report Builder configuration options. Or, you can create a signature field with, or without, a timestamp. Learn more in Signature field configuration. | No |
These data items refer to other data to display and store data.
| Type | If you want to... | Filterable in list form |
|---|---|---|
| Calendar | Display a calendar in an application. You can configure:
Calendar size for inline calendars is determined by the width of the column it is placed in. For example, if there is only one column in the row, the calendar fills the whole row. If there are two columns in the row, the calendar fills half the row. Popup calendars fill the window. Configure the calendar in the Calendar Definitions application and reference the calendar data item. This data item holds the calendar once data mappings, application settings, logic blocks, or the Form Dependencies in the application tell the calendar data item which calendar to display. Learn more in the Calendar configuration topic. | No |
| Data Item Group | Create a collection of data items that can be included as a set in more than one table. Use this data item type if you have a group of data items that need to be collectively added in a number of tables or applications. This data item type is used to create multi-segmented data items. A multi-segment data item is a group of data items whose values are combined into a single formatted text field. The individual fields that the format uses to combine these values are referred to as segments, and the field that stores the combined values is referred to as the concatenated field. Multi-Segments are displayed as s single field but can be filtered by the individual segment fields that were used to create the concatenated value. | No |
| Object | Referential. An object is a single field that is comprised of a collection of data items in a table. You can configure:
| No |
| Subtable | Use this data item type to include a small subset of data as a table in your applications. This data item allows you do include an Add button so that users can add entries to the subtable from the current application. Subtables only display in the detail form of an application. They cannot be used in the list form. | No |
| Table Lookup | Create a reference to a data item in another table so that the resulting application field always displays the current value of the referenced data item. The Table Lookup data item stores the Nextworld internal ID (nwId) of the item it looks up, and evaluates to a display value at runtime. You can configure:
| Yes* |
Date and time considerations
DateTime data items store values differently than Date and Time data item types. Logic blocks can be used to manipulate the display values, such as setting the time zone based on the tenant time zone. Locales are used to designate the format for how dates and times are viewed.
System
There are several considerations for DateTime, Date and Time data items, including:
- Values in
DateTimedata items are stored by the system as Coordinated Universal Time (UTC). Everything is compared to one standard clock reference, and is stored as a point in time. When the values are retrieved for display purposes, by default they are converted to the appropriate time based on the user's time zone, which is controlled by browser settings, environment settings, or user profile settings. Learn more in Time zones. - Values in
Timedata items with a system value ofNoware stored as hard values. They are not time zone aware or stored as UTC. - Values in
Datedata items with a system value ofTodayrequire a time zone to be entered in the logic block action's properties. - If you decompose a DateTime field, you must select a time zone. For example, if you have a DateTime field value of 12:00am 1/1/2025 GMT and decompose it into a Date and Time, you could select GMT-6. This would give you a Time value of 6:00pm and the date of 12/31/2024.
- Values in
DateTimeandTimedata items can be configured with a Time Format. Time format controls the display and precision for time values. For example, you can specify only hours display in the field, or you could specify that hours, minutes, seconds, and milliseconds should display. The maximum precision for time is three digits (milliseconds).
Learn about date and time calculations in Date and Date Time calculations and Exclude dates in Date Time calculations.
Logic Blocks
Logic blocks can be used to convert Date and Time data item values to the appropriate time zone based on either a System value, like the tenant time zone, or a dynamically mapped value. The mapped value must be fetched, or pulled in as an input record.
There are several logic block actions that can assign the Date from a DateTime. Some examples are:
- Date Time Decomposition action—Allows you to decompose, or break down, a
DateTimevalue into its individual components. The outputDateandTimeare pulled from the inputDateTimeafter it is converted to the time zone specified. If no time zone is specified, the tenant's default time zone is used. Optionally, you can also use the time zone as the output.
- Set Values action—Allows you to use a
Dateas the output, and different types of inputs, such as aDateTimefield, a System value ofToday, or a Text or Number data item with a lookup on time zones.- You can also use this action to designate a different time zone than the tenant. For example, if the time zone is fetched from the Org Unit, that time zone would be used when converting the
Date.
- You can also use this action to designate a different time zone than the tenant. For example, if the time zone is fetched from the Org Unit, that time zone would be used when converting the
Defaulting date and time values
When defaulting date and time values using the data mapper, application settings, or the Now or Today buttons within an application, the system chooses which time zone to use. The system determines what time zone to select based on the Display Preferred Time Zone checkbox on the Tenant Environment Setup record for that environment. Options include:
- Display Preferred Time Zone selected—The system looks for a Custom Time Zone in the User Profile. If no Custom Time Zone exists, it uses the Tenant Environment Setup application record's Default Time Zone. If no time zone is selected for this environment, the system uses the default time zone configured by the platform.
- Display Preferred Time Zone cleared—The system looks for a Custom Time Zone in the User Profile. If no Custom Time Zone exists, it uses the user's browser's time zone.
Interfacing with platform APIs
Endpoint integrations into Nextworld support any ISO-8601 valid format for DateTime values. It is preferred to use the format which the platform stores, but UTC DateTime formats may include a time zone offset for integrations. For example, the following UTC formats represent the same timestamp and are both accepted by the system:
2024-02-28T07:00:00.000Z (preferred)
2024-02-28T14:00:00.000+07:00
Locale
Locale is set in the User Menu and designates how date and time are formatted in the system. For example, English (United States) locale formats the date of November 01, 2022 as 11/1/2022, but French (France) locale formats that date as 01/11/2022.
Date and Date Time calculations
Use the Date Math, DateTime Math, DateTime Decomposition, DateTime Composition, Set Values, and other math actions to calculate dates, durations, time, and timezones.
The Date Math action is designed to handle the complexities of adding and subtracting dates. You can add a modifier, which determines the units of measure for the output.
The following actions are available to perform date math:
| Action | Description | Input | Output | Use to |
|---|---|---|---|---|
| Date Math | Perform math with a date value. | DateApply a modifier, such as a number, duration, or system value. | Date | Add a week to a date. |
| Perform math with a DateTime value. | DateTimeApply a modifier, such as a number, duration, or system value. | DateTime | ||
| Subtract | Calculate the difference between date values. | Date - Date | Duration or Number | Find the number of days between two dates. |
| Calculate the difference between two DateTime values. | DateTime - DateTime | Duration | Find the time difference between two DateTime values. | |
| Calculate the difference between time values. | Time - Time | Duration | ||
| Add/Subtract | Add or subtract a duration to get a new time. | Time - or + Duration | Time | |
| Add or subtract two durations. | Duration - or + Duration | Duration | ||
| Set Values | Convert a number to duration, or duration to number. | |||
| DateTime Math | Perform math with a DateTime value. | DateTimeApply a modifier, such as a number, duration, or system value. | DateTime | |
| DateTime Decomposition | Decompose, or break down, a DateTime value into its individual components. | DateTime | DateTimeTimezone | Change the timezone of a DateTime value. |
| DateTime Composition | Create a DateTime value. For example, you can change a date and time value into a DateTime value. | DateTimeTimezone (optional) | DateTime | Change the timezone of a decomposed DateTime value. |
Multi-Segment data item configuration
Configure Multi-Segment data items using the Data Item Definitions, Table Definitions, Application Builder, and Format Definitions applications to concatenate data item values into a single text field.
Data Item Definitions
You must create all of the data items that make up your multi-segment.
In the Data Item Definitions application, you must:
- Create a data item of type
Textthat stores the concatenated value - Create a data item of type
Textthat stores the name of the format that is used to create your concatenated value - Create a data item for each of the individual segments that make up the concatenated value. This data item must be of type
Text,Number, aList Lookupof typeText, aList Lookupof typeNumber, aTable Lookupof typeText, or aTable Lookupof typeText. - Create a data item of type
Data Item Group. On the Settings page, select the Treat as Multi-Segment checkbox and add the data items you created for your concatenated and format fields in the Multi-Segment Format Field and Multi-Segment Concatenated Field.
Table Definitions
In the Table Definitions application, you must:
- Create a table of type
Subwith the same internal name as theData Item Groupdata item created above. The table must share the exact same name of the data item, including capitalization. This is how the two objects are linked. If the names don't match, the data item group configuration won't work. - Add all of the segment data items that you want to use in your concatenated value into the subtable, as well as the two text fields that were configured to store the format and concatenated fields.
- Do not add the Data Item Group data item to this table.
- Add the Data Item Group data item to the table that the application you want to use the multi-segment in is built over. This automatically pulls all of the fields from the corresponding subtable into the application.
Application Builder
Once you've added the data item to the application's table, you must configure it in the application.
In the Application Builder application in the Configuration panel, you must:
- In the List form section, set the display property of all the fields, including the Data Item Group, to the same value. The fields must have the same Display Value in order for the multi-segment to work.
- In the Detail form setion, add your multi-segment to the detail view. The Data Item Group and all of your segments must be added to the same row and column.
See the Application Builder topic for information on field dependencies that can be use with multi-segment data items.
Format Definitions
In order to use the multi-segment in the application, you must create a new format.
In the Format Definitions application, there are several configuration options to consider, such as:
- The Format Name is the identifier that is stored in your Multi-Segment Format field. It is also used when entering data into the controlling field of a format field dependency.
- The Format Type must be
Multi-Segment Format. - The Format Description is the displayed name when you select a format from the dropdown in the multi-segment panel.
- The data items you created must be added to the Individual Segments subtable. The order in which they are added to the subtable is how they appear in the list.
- The Format Delimiter is the single character that is used to combine your segment values into your concatenated value.