Grid Component

{ “type”: “GRID.SET_FILTER”, “options”: { “targetKey”: “grid”,"global": "true", “value”: “Auto”, “column”: “type”, “mode”: “toggle”, “type”: “includesString” } }

{ "type": "GRID.SET_COLUMN_VISIBILITY", "options": { "targetKey": "grid", "column": "status", "value": "TOGGLE" } }

{ "type": "GRID.SET_SORT", "options": { "inputs": [ { "targetKey": "sortBy", "alias": "A" } ], "targetKey": "grid", "column": "=A", "direction": "asc" } }

{ "type": "GRID.SET_TRANSPOSED", "options": { "targetKey": "grid", "value": "TOGGLE" } }

{ "type": "GRID.SET_VIEW_TYPE", "options": { "targetKey": "grid", "value": "TOGGLE" } }

{ "type": "GRID.ADD_COLUMN", "options": { "inputs": [ { "targetKey": "columnKey", "alias": "B" } ], "targetKey": "grid", "columnDefinition": "=CONCATENATE('{\"type\":\"textfield\", \"key\": \"', B, '\"}')" } }

"options": { "targetKey": "gridComponentPropertyId" }

“options”: { "targetKey": "grid", "alias": "B" }

“options”: { "inputs": [ { "targetKey": "enter target propertyID", "alias": "enter alias numeral" } ] }

“options”: { “targetKey”: “grid”, "global": "true" }

“options”: {  “targetKey”: “grid”, “value”: “Auto”, “column”: “type” }

“options”: {  “targetKey”: “grid”, “value”: “Auto”, “column”: “type”, “mode”: “toggle”, “type”: “includesString”  }

"options": { "targetKey": "grid", "value": "TOGGLE" } }

"options": { "targetKey": "grid", "column": "=A", "direction": "asc" } }

"options": { "targetKey": "grid", "columnDefinition": "=CONCATENATE('{\"type\":\"textfield\", \"key\": \"', B, '\"}')" }

"options": { "targetKey": "grid", "position": "0" }

A Property ID 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 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. calls.

Property IDs must use camel case A naming convention for computer programming. Use camelCase for Property IDs, for example: newUser, lastName, & rdoButton. (stylized as camelCase) without spaces or punctuation.

Select this tab to display the component's Notes area. You can use notes to keep your teammates informed.

The Notes editor offers a semi-WYSIWYG (What You See is What You Get) content editor. Built to look like a word processor, this editor lets you create, edit, and format your notes. Notes save when saving the component.

Select this tab to manage your component's display settings.

Select this tab to manage your component's data settings.

Select this tab to manage your component's validation settings.

Select this tab to manage your component's advanced settings.

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. (role-based access control) settings of the component.

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 Panels. 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.

Select this tab to open the list of supported keyboard shortcuts you can use in the component settings modal. Keyboard shortcuts include:

• Cmd + S (Mac) / Ctrl + S (PC): Save and close the component settings modal.

• Cmd + G (Mac) / Ctrl + G (PC): Opens a search window to find specific fields and settings in the component settings modal.

• Tab: Tab to the next field or setting in the component settings modal. This keyboard shortcut tabs left to right and top to bottom.

• Shift + Tab: Tab to the previous field or setting in the component settings modal. The keyboard shortcut tabs from right to left and bottom to top.

• Enter (Return): When tabbing to a  (tooltip), press Enter (Return) to display the field or setting tooltip. Press Enter (Return) again to hide the tooltip.

Additional keyboard shortcuts:

• Drop-down menus: When you Tab to a settings drop-down, use the keyboard's  (up)/  (down) arrows to make a selection. Then, press Enter (Return) to confirm the selection.

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

Hover over the column header and select the  (ellipsis) to open the Table Column Settings drop-down menu.

From the column settings drop-down menu, select one of the following options:

• Copy column

• Cut column

• Paste column

• Clear Data

• Delete column

Hover over the column header and select the  (ellipsis) to open the Table Column Settings drop-down menu.

From the row settings drop-down menu, select one of the following options:

• Copy row

• Cut row

• Paste row

• Insert row above

• Insert row below

• Clear Data 

• Delete column

Add a new row to all Grid column fields.

NOTE  Rows that contain no data in any column field do not display in Express View.

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.

NOTE  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.

TIP  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.

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).