The following topics describe the different configuration options for application actions:
- Field, Row, and List Form Actions
Configure field, row, and list form actions to create buttons and action menus in an application to open application links or run logic blocks.
- Control Actions
Control actions hide or disable fields buttons. This includes standard system buttons like Save or Cancel , as well as custom buttons created by an application developer.
- Event Actions
Event actions run logic blocks automatically when users perform actions, such as select a field or delete a row, in the application. Logic blocks that run as event actions are built over the same table as the application they are run from.
- Application links
Use application links to open other applications, interactive reports, or dashboard pages from inside an application. Application links used to navigate outside of the application can appear as buttons or row actions, or they can change the application that users see when they create or edit a record.
- Search actions and search applications
Search applications enable users to view, select, or create records in other tables. Search applications are linked to other applications by a Table Lookup field, also referred to as a search field or typeahead field.
- Copy actions
Copy actions run logic blocks when the user selects the Save and Add Another or Create a Copy button. Use copy actions to clear or set field values in records created from other records.
- Logic Block Prompts
Use logic block prompts to run a logic block from a list form action with information entered by a user at run time that isn't already saved in a table. Logic block prompts open a mini app which prompts users to enter information before running a logic block.
- Application overrides
Use overrides to change the application that opens when the user clicks the Create button, the Edit button, or double-clicks top open a record in a list.
Field, Row, and List Form Actions
Configure field, row, and list form actions to create buttons and action menus in an application to open application links or run logic blocks.
There are several buttons and action menus you can configure, such as:
- Field actions—Creates a button for a field.
- Row actions—Creates a row action menu in the detail list and subtables, and a form action menu in the detail form.
- List form actions—Creates a form action menu in the list form.
How you configure the action determines if the action opens an application link or runs a logic block.
Field actions
To configure Field Actions, in the Application Builder navigate to the Field Actions section in the Configuration panel. There are several types of field actions, such as:
- Standard—A button appears under the specified field on the Detail and Header Detail forms of applications. If there are multiple actions configured on the same field, a dropdown option appears. Alternately, you can configure a field action on an expansion row. Leave the Options field empty to create a standard field action.
- Subtable—A button icon appears next to the specified field in a subtable. Leave the Options field empty and enter the subtable name in the Field Subtable field to create a subtable field action.
- Button Only—A button appears in the Detail form. The label and field itself are hidden. If there are multiple actions configured on the same field, a dropdown option appears.
- Button and Field Label—A button appears in the Detail form with the label. The field itself is hidden. If there are multiple actions configured on the same field, a dropdown option appears.
- List View Action—A clickable link appears on the list form of an application. Only one action is allowed per field.
- Calendar Event Action—Displays the button in the calendar event. This option can only be used with calendar data item fields.
Actions that open application links
To configure an application link as an action in the Application Builder application, you must:
- Configure an application link in the Application Links section.
- Add the application link as an action in either the Field Actions, Row Actions or List Form Actions section.
- For List Form Actions and Row Actions, use the Link Type field to control if the user must save the record before the application link opens.
Actions that run logic blocks
To configure a logic block as an action in the Application Builder application, you must:
- Configure the logic block using either the Field Actions, Row Actions, or List Form Actions subtable.
- For List Form Actions and Row Actions, the selection in the Link Type fields controls how the action works when a user has saved a record. This field also controls if a logic block runs within the transaction boundary. The options include:
Application (Extend Trans Boundary)—Extends the NATE container to the application you are opening with the application link. For more information, see the Nested NATE containers topic.Application (Save Not Required)—Does not require the user to save the record before the application link opens the new application. Runs outside of the transaction boundary. Often, changes are still available when the user navigates back to the first application.Application (Save Required)—Requires the user to save any unsaved changes to the record before the logic block runs. Runs outside of the transaction boundary.Logic Block - Not in Trans Boundary—Does not require the user to save the record before the logic block runs. Runs outside of the transaction boundary, which means if this logic block updates a record, the change is applied whether or not the current record is saved.Logic Block - Not in Trans Boundary (Save Required)—Requires the user to save the record before the logic block runs. Runs outside of the transaction boundary.Logic Block In Trans Boundary—Does not require the user to save the record before the logic block runs. Runs within the transaction boundary and any changes from the logic block are part of the same NATE container. This means that if the record is not saved, any changes to the record made by the logic block are discarded.
For actions configured on subtables, you must:
In the Logic Block Builder, in the Loop Subtable Action action, select the Select Current Subtable Row checkbox to ensure the logic block runs on the subtable row which the action was performed on. Logic block support of the Select Current Subtable Row can only be used for subtable mains, not for subtable subs.
In the Application Builder, in the Row Actions section, you must:
- Configure the logic block as an action using either the Field Actions, Row Actions, or List Form Actions subtable.
- For row actions, select the subtable row where you want the row action configured.
- In the Event Actions section, you can also optionally configure a row action event to hide and show row actions on your subtable. Like list forms, this event action should not be used for data manipulation.
Control Actions
Control actions hide or disable fields buttons. This includes standard system buttons like Save or Cancel, as well as custom buttons created by an application developer.
There are several control actions you can configure, such as:
- System actions—Automatically available on all applications. For example, Get Sharable Link or Save and Exit.
- Custom actions—List form, row, or field actions added to the application by an application developer. Learn more in Field, Row, and List Form Actions.
- Subtable actions—Available in a subtable. These include custom row actions, and system actions such as the Add and Delete buttons.
To configure control actions in the Application Builder application, open the Control Actions section in the Configuration panel. There are several considerations, such as:
- The value in the Form field controls the options available in the Control Action field.
- Whether you want to hide or disable the action.
- If the action is a custom action or in a subtable, you must enter the name of the action or the name of the subtable.
For example, if you want to hide all of the row actions in an application, you can select All Form Actions in the Control Action field.
The table below shows what fields to use to configure control actions for a single system or custom action, a subtable system or custom action, or all system or custom actions:
| Control Action | Display Name | Table Name | ||
|---|---|---|---|---|
| System | All system actions | X | ||
| Single system action | X | |||
| Subtable system action | X | X | X | |
| Custom | All custom actions | X | ||
| Single custom action | X | X | ||
| Subtable custom action | X | X | X |
Enable column controls for checkboxes
Enable columns to have Select All and Clear All checkboxes with the Datatable True/False Click (with multiple selection) event action.
This event action is available on the detail lines of Header Detail applications, the detail list of Relationship applications, and on subtables used in any application type. Once configured, the Select All and Clear All actions are available in the action menu of the selected field.
Event Actions
Event actions run logic blocks automatically when users perform actions, such as select a field or delete a row, in the application. Logic blocks that run as event actions are built over the same table as the application they are run from.
Configure event actions in Application Builder, in the Configuration panel in the Event Actions section. For all event actions, you specify:
- Event—The event to run the logic block from
- Action—The name of the logic block to run
If the event is configured for an action on a:
- Specific field—Enter the name of the data item in the Field Name field.
- Specific subtable field—Enter the name of the subtable in the Event Subtable field. You also need to enter the name of the data item in the Field Name field.
Learn more about the different event actions in Logic blocks and event actions.
Application links
Use application links to open other applications, interactive reports, or dashboard pages from inside an application. Application links used to navigate outside of the application can appear as buttons or row actions, or they can change the application that users see when they create or edit a record.
Configure your application link
In the Application Builder, in the Application Links section, you must specify:
- A unique name for the application link.
- A Destination Type for the link. In this case, either
DashboardorApplication. To link to an interactive report, selectApplication. - The name of the application or dashboard page you want to link to in the Link Destination field. If you're linking to an interactive report, enter
InteractiveReportsViewer. - Optionally, application settings or data mappings for application links of type
Application.
For application links to an interactive report, data mappings require additional configuration steps. To configure, you must create the publisher mappings in the Common Context section of the application record. Then, navigate to the Interactive Report Builder and open the interactive report record, where you must:
- Configure the subscriber mappings in the Common Context section.
- In the appropriate report version, select the name of the common context configuration in the Common Context field.
See the Common Context configuration topic for more information.
Then, navigate to the Application Setting Definitions application and open or create the record for the application setting applied to your report. The application setting must have the:
- Setting Type field set to
Interactive Report. - Name of your interactive report record entered in the Interactive Report Record field.
- Name of the appropriate report version entered in the Interactive Report Version field.
Configure your action or dynamic application link
Application links with a Destination Type of Dashboard Page or Application do not appear in an application until the link is associated with an action or dynamic application link.
After application links are defined in the Application Links subtable, they can be added as different types of actions, such as:
- Field Actions—A button below a field.
- Row Actions—A button in the row action menu of the list form, or the form action menu in the detail form.
- List Form Actions—A button in the list form action menu.
- Create Override—Changes the application that opens when a user selects the Create button in an application.
- Edit Override—Changes the application that opens when a user edits an application record.
If you want to open different application links depending on a field value, use a dynamic application link. Dynamic application links require application links to be configured with specific naming formats. Learn more in Dynamic application links.
Inline Applications
Application links can also be used to embed an inline application into the detail form of an application. See the Configure inline applications topic for more information.
Filtering in application links
Advanced filter mappings, field mappings, and frozen filters can be applied to application links through application and application setting configurations. There are several considerations for how filters are prioritized on fields, such as:
- If an advanced or frozen filter exists, field mappings are ignored.
- If both an advanced and frozen filter exist, both are applied, but any fields included in both filters are only filtered by the frozen filter.
- If the same type of filter is configured in both the application and application setting, both are applied, and any shared fields are filtered by both. This can cause limited or no queries to be returned.
Navigate to applications on save
Use application links with the Save and Continue action so that when a user saves a record, they open a different application or record in the same window.
The Save and Continue button does not appear in an application unless you associate it with an application link. To configure the Save and Continue button, you must:
- Configure an application link. Learn more in Application links.
- Enter the application link you configured in the Save and Continue Application Link field.
In the generated application, the Save and Continue button becomes the default save action. Select this button to save the current record and then open the application link.
Dynamic application links
Use dynamic applications links to connect multiple application links to a single button or action. The application link which opens when the link is selected is determined by the value entered within a specified field.
Before you can configure a dynamic application link, you must configure the application links you want included. Only application links with a Dashboard of Application or Dashboard can be used.
Learn more about configuring application links in Application links.
Every application link included in a dynamic link must use the same prefix in their link name. That prefix should be the link name of the dynamic link. After the prefix, add the field value you want associated with the application link. This is how the system can find the appropriate application link when a value is entered in the source field.
For example, the Payments application could have a dynamic application link where the value selected in the Transaction Type field determines which link should be followed. To configure, you would create your application links with the following information:
| Link Name | Link Destination |
|---|---|
ViewPayManual Check | Manual Checks |
ViewPayAP Payment | Payments |
ViewPaySupplier Credit | ApplySupplierCredits |
ViewPayCustomer Refund | ManualChecks |
Then, in the Dynamic Application Links section of the Application Builder, you would create a dynamic application link with the following values:
| Link Name | Source Field | Value | Destination Link Name |
|---|---|---|---|
ViewPay | SubTransactionType | * | ViewPay* |
Then, you would associate that dynamic link with a button or action. When a user enters a value in the Transaction Type field, the value selected would tell the system which application link that button or action should lead to. If a user selected Manual Check in the Transaction Type field, the application link to the Manual Checks application would be used.
Connect to other visualizations with application links
Use application links to attach additional visualizations to an application. When a user interacts with components of an application's visualization, they can navigate to other visualizations with related data.
For example, if you are in the list form of the Supplier Invoices application which has a visualization for the company totals. A component of the company totals are the company credits. You can configure a visualization link so when a user selects the company credits part of the visualization, it navigates them to the general ledger record that shows a different visualization built over the company credits.
Prerequisites
You must set up the visualizations and application link before you can configure the visualization link. To configure, in the Configuration panel of the Application Builder you must:
- Navigate to the Field Dependencies section and configure the visualizations you want for the application. Learn more in Visualization Builder.
- Navigate to the Application Links section and configure an application link. Learn more in Application links.
Visualization Link
In the Visualization section, you must:
- Enter a display name for the visualization.
- Enter the name of a visualization you configured and want attached to the application.
- Enter the application link you configured in the Link Name field.
Copy actions
Copy actions run logic blocks when the user selects the Save and Add Another or Create a Copy button. Use copy actions to clear or set field values in records created from other records.
Copy actions can run logic blocks that set field values or logic blocks that would normally run as event actions that validate field values. For example, if a logic block runs as a Row Exited event action that updates another table, you could configure a logic block as a copy action that performs a similar update or calls an action block.
Configure copy actions in Application Builder in the Configuration panel, in the Copy/Recurring Template Actions section. To configure a copy action, enter the name of the logic block to run.
Logic Block Prompts
Use logic block prompts to run a logic block from a list form action with information entered by a user at run time that isn't already saved in a table. Logic block prompts open a mini app which prompts users to enter information before running a logic block.
Configure your mini app
In the Application Builder application, create a new mini app. The mini app must be built over the same table that initiates the list form action. This is generally a table of type Main, but for Header Detail applications it is the Header table.
Configure your logic block prompt
Configure logic block prompts in Application Builder in the Configuration panel, in the List Form Actions section. Once you select your Link Type, the following Logic Block Prompt fields become available for configuration:
| Display Name | The name that displays at the top of the mini app that opens. |
|---|---|
| Application Setting Name | The name of the application setting to apply when opening the mini app from the list form action. |
| Prompt Name | The unique name of this logic block prompt. This field is used to identify the prompt when adding it as a list form action. |
| Prompt Mini App | The name of the mini app to use as the logic block prompt. This application must be built over the same table as the logic block, unless it is a Header Detail application. Logic block prompts are only supported on the list form of Header Detail applications. In this case, the logic block must be built over the Header Detail table, and the mini app must be built over the Header table. |
Once you've created your prompt, configure your action in the following fields:
| Logic Block | The name of the logic block to run from the prompt. |
|---|---|
| Display Name | The name that displays on the list form action button. |
| Prompt Name | The name of the prompt, defined in the Prompt Name field of the Logic Block Prompts subtable. |
Application overrides
Use overrides to change the application that opens when the user clicks the Create button, the Edit button, or double-clicks top open a record in a list.
Use overrides to change the application that opens when users open or create a record. Overrides result in application links being opened instead of the application the action is on.
In Application Builder in the Application Properties panel, expand the Application Link Overrides section and configure the override using the Row Double Click/Edit Override and Create Override fields.
Application actions best practices
These best practices ensure that application actions are configured consistently throught Nextworld.
Build action events in the Logic Builder in the Logic Block Builder application, and then apply them in the Actions page of the Application Builder application.
Logic blocks run in the order they appear in the Event Actions subtable on the Actions page in Application Builder. Multiple logic blocks can be associated with the same events and are bundled to make only one call to the server.
If you need to fetch all detail rows, do not have two logic blocks on Row Exited fetching all detail rows. To prevent the logic block from fetching and refetching all detail rows whenever you exit or change a row, use the current row option to fetch the details instead.
On Form is Initialized logic blocks, defaulting field values should be conditioned to only default if the value is blank, so it does not override the value that was entered or overridden.
Logic blocks ran on Field Value Changed, Field Entered or Field Exited need to consider if the value is likely to be defaulted via an application setting. In this case, the logic must also reside on Form is Initialized .
Use a Row Changed event and Field Value Changed events instead of Row Exited and Field Exited. Field Exited and Row Exited always call a logic block on the event in which the logic block always runs regardless if the value has changed or not. Using Row Changed and Field Value Changed events instead prevents the logic block from running when a value didn't change. For these events to trigger, a user must enter and exit the row or field and the value must be different from when the user entered the row or field. If a logic block changes the value, this does not trigger a change event.
Application links
For application links with data mappings, map the nwId as the Source Related Field for table lookup fields. This enhances performance, while using the table Primary Search Field field hinders performance. The nwId value does not display in the column header when mapping nwId.
To reduce the number of records fetched, use Exact Match as the Filter Prefix when possible.
If Form or Row action are hidden via a logic block. Run the Logic block in both the detail form and list form for consistency.