Address (v1) Component

Selecting this tab shows all Address component configuration settings.

Selecting this tab shows the Required Error setting. Use this setting to enter a custom error message to appear if your end-user End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. does not complete this field.

The Required Error message will only display if you mark the component as Required under the Display Tab.

Select this tab to see the RBAC RBAC (Role-Based Access Control) is a method to control system access for authorized users. The role in RBAC refers to the levels of access employees have to a network. settings of the component.

Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field.

User-friendly labels make your module more accessible. Keep labels short and descriptive (a word or two) using title case. For longer entries, use sentence case.

A Property ID (also called Property Name) is the unique field ID used by Unqork to track and link components in your module.

The Property ID is how the software identifies your component. Using Property IDs lets you link components, creating logic-based configurations and API calls.

Property IDs must use camel case (stylized as camelCase) without spaces or punctuation.

Click this button to undo any unsaved configuration changes and return to the Module Builder canvas.

A short prompt telling end-users the expected value of an input field. For example: Enter your Social Security Number. Placeholder Text displays inside the input field until the end-user begins an entry.

Enter the coordinates of a region. The coordinates tell the Google Places API what regional results to suggest first. For example, entering 56.1304, 106.3468 tells the API to suggest Canadian addresses first.

Enter a Google Maps API key.

For testing purposes, the Address component will work without completing this field. However, for security purposes, always acquire and enter your own key.

Enable to influence or restrict the values the Google Places API will return.

To restrict suggested results based on country, use the following format: country:[2-letter ISO 3166 country code]. For example, entering country:US|country:CA would restrict results to the United States and Canada. To see a complete list of ISO 3166 country codes, visit the following link: en.wikipedia.org/wiki/List_of_ISO_3166_country_codes.
You can also influence suggested results based on state, city, or other values.

Enter a Custom CSS Cascading Style Sheets (CSS) is a style sheet language used for presenting how a HTML or XML document looks to end-users. Class to apply to your component. Custom CSS lets you maintain a consistent look and feel when the field or element is part of a template or multiple modules.

Updated CSS styling applies to all components that reference this custom class name.

A short hint that displays when an end-user positions their cursor over the (Tooltip) icon. Tooltips can display across more than one line.

Set to  (ON) to display the secondary street address field in Express View. Secondary street address information might include building floor and office space values.After your end-user selects a suggested address, this field auto-fills from the address data returned by the map service API.

Set to  (ON) to display the address field in Express View. Street Address includes building number and street address values. After your end-user selects a suggested address, this field auto-fills from the address data returned by the map service API.

Set to  (ON) to display the City field in Express View. After your end-user selects a suggested address, this field auto-fills from the address data returned by the map service API.

Set to  (ON) to display the Zip code field in Express View.. After your end-user selects a suggested address, this field auto-fills from the address data returned by the map service API.

Set to  (ON) to display the State field in Express View. State information might include individual U.S. state locations, territories, or sub-regions of a country.

Set to  (ON) to display the Country field in Express View. After your end-user selects a suggested address, this field auto-fills from the address data returned by the map service API.

Set to  (ON) to hide the address search function. The Address Search component will not communicate with the Address Service API and perform an address lookup. Instead, the address fields you select display in Express View. Your end-user can then manually type in their address details.

By default, this setting is (OFF).

Where the component is set to hidden, setting this toggle to (ON) clears the field’s stored value from the database. Setting the toggle to (OFF) stops the application from removing the stored value.

The Store Data in Database setting affects how data persists through your application. When set to  (ON), Unqork stores values entered into the field to the database (server-side submission). This occurs in three scenarios:

• Navigating between Panels in a Navigation component. On navigation between pages (Panels), the component’s value saves to the database.

• Triggering a module save event using a Button component with an Action Type of Save.

• Navigating between screens of a workflow. On navigation between screens, the component’s value saves to the database.

Set the toggle to (OFF) when you don’t want to store the values from this field in the database.

When using a Plug-In to remote execute a module, ensure data moving between modules is persistent. You can optionally enable Store Data in Database for components in the source module. But any components in the API module whose values are included in an API response must have Store Data in Database enabled. When a component’s data is not persistent, the data isn't included in an API call's response. So, Plug-Ins or external services requesting data from the API module can't receive non-persistent data in the response. To learn more about Store Data in Database in the context of API modules, see the panelResponse Panel section of the API Specification Snippet article in our In-Product Help.

Store Data in Database also affects what data is tracked using Unqork’s built-in tracker. When the Enable Tracker and Track Value toggles are set to  (ON) in Module Settings, only values from fields with Store Data in Database enabled are tracked.

Hides the component from displaying in Express View.By default, this setting is (OFF).

When checked, end-users can’t interact with or edit the Express View's input field or element. When end-users hover over the field, their cursor will change to alert them to the status change.

When set to ON, end-users can’t interact with or edit the Express View's input field or element. When end-users hover over the field, their cursor changes to alert them to the status change.

By default, the Disable User Input toggle is set to (OFF).

When set to  (ON), the end-user must enter a value in the component's visible fields. Set the toggle to (OFF) when an entry is optional.

By default, the Required toggle is set to (OFF).

Assign components one-word labels to help organize, identify, and group the components in your application.

Consider an example from the API Specification Snippet: Field Tags are applied to Hidden components in the panelRequest and panelResponse Panel components. The Field Tags identify the data type of parameters included in the API APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services. request and response. The API Docs Dashboard tool populates with information about each parameter’s data type, identified by the Field Tag.

Field Tags act as a type of Property ID A Property ID is the unique field ID used by Unqork to track and link components in your module. group and let you group components for configuration purposes. Field Tags let you target two or more components using a simple logic component.

For example, add the Field Tag tagForDecision to multiple components in your module. Open the Inputs table of a Decisions component and reference the tagForDecision Field Tag as the input of the Decisions component. The output of the Decisions component then affects all components with the tagForDecision Field Tag.

Save your Field Tags by pressing Enter (Return) or adding a comma after each entry.