Queue App Link action

Use the Queue App Link action to automatically navigate users to different applications or composite application steps using logic blocks. The action opens an application link defined in the underlying application once the executing logic block has completed. 

For example, a composite application could use the Queue App Link action to automatically navigate users to the appropriate application step based on the value they select in a field. This is useful for mobile application users who may be navigating through multiple application steps while creating a record. 

Or, an application could have a row action which executes a logic block to create a new business record. When a user selects the row action, the logic block could use the Queue App Link action to open the application where the new record was created. 

Configuration

To configure, add the Queue App Link action to your logic block, then:

  • Specify the name of the application the user would interact with. This could be a different application, or an application step within a composite application. This allows the action to see what application links are available. 
  • If your application is a composite, select your Composite Link Type. For guided composite application, see the subheading below. For standard composite applications, options include:
    • Composite App Link—Queues an application link defined in the composite application link subtable of the Application definition
    • Composite Step—Queue an application link to a specific step within the composite application. 
  • Select your Link Type. 

Guided composite app links

For guided composite applications, your Composite Link Type options include:

  • Complete Current Step—Executes the Navigation logic block defined on the current composite step. If the logic block queues an application link, the user is navigated to the specified application. Otherwise, the user is navigated to the next step defined in the composite pattern. 
  • Composite Cancel and Add New—Enables you to perform a Cancel and Add New action dynamically with your queue app link. For example, based on the quantity a user entered in a field, the logic block could cancel the save action and navigate the user back to a previous step of the flow with specific information copied to the new record. 
  • Composite Save and Add Another—Executes any action block or trigger on the table definition that the composite is built over, and takes the user back to the first step of the composite pattern. For example, based on the quantity a user entered in a field, the logic block could conditionally save the record and navigate the user back to a previous step of the flow with specific information copied to the new record. 
  • Composite Save and Add New—Enables you to perform a Save and Add Another action dynamically with your queue app link. Optionally, add field mappings to create default values on the record that gets created.
  • Composite Save and Exit—Executes any action block or trigger on the table definition that the composite is built over, and exits the user out of the composite application. 
  • Select Steps—Select which application step to navigate the user to next. The available steps are from the configured application steps within the composite application. 

Queue Dialog action

Use the Queue Dialog action to open a dialog box when event actions, such as field value change or selection of a button, occur. For example, when a user selects the Generate All form action in the Application Builder, a dialog box opens which asks them to confirm or cancel the action. 

To configure, select the Queue Dialog action then:

  • Select if the dialog box is an Error, Warning, Info, or Success message. 
  • Create the message to be displayed in the dialog box. 
  • Select the button options you want displayed, such as Ok and Cancel, or Yes, No, and Cancel. 
  • Select what action occurs when a user selects a button. For example, calling a logic block or closing the dialog box. Any called logic blocks must be built over the table of your underlying application.

Queue Event action

Use the Queue Event action in a logic block to create a business event emitter.

In the Logic Block Builder application, create a post run logic block and:

  • Select the Queue Event action.
  • In the Details panel, in the Event Action Type field, select either User-Defined Event or Message Event .
    • User-defined events are configured in the Event Definitions application. Learn more in Event configuration.
    • Message events are configured in the Message Definitions application. Learn more in Message configuration.
  • Enter the name of the event.
  • For message events, if the event must be executed in a certain order in relation to other events, use the Sequential Execution Key field to specify a key.
  • Use the Payload Entries fields to map in values from a data source to the payload entry. 

Queue Report action

Use the Queue Report action in a logic block to run a designated report version application in the background and to send the report output to a desired location.

Users can navigate to other parts of Nextworld while the report is running, and will receive status related notifications after report execution. If the report is successful, the notification contains a link to the report output. 

Configuration

Choose the report by specifying a report version application with the desired report’s details in the application definition. Report version applications can be customized to point to a different report record. If the report version application is customized, the report from the customized application will be run.

There are multiple mappings and options within the Queue report action.

Configuration OptionUse
Post-Processing Data SourceUse for cases where the report triggers a workflow report transition. The post-processing data source is the record undergoing workflow.
Field Mappings for Selected Report Version ApplicationUse to select the inputs for the report. 
Add Attachment
Use to name, format, and copy the output of the report to a business data record that you specify.

Use the Regenerate Report if an attachment already exists on the source record. For example, if there is a generated sales invoice, you can use the one that is already generated, even though the logic block is telling the system to generate one.

Queue Message Event on Report SuccessUse to specify post run actions for after the report finishes, such as emailing the report to a customer.

Queue Parallel Processing action

Application developers use the Queue Parallel Processing action to efficiently batch process a large number of business records. This occurs by dividing the records into multiple buckets, then processing the buckets with the same logic block concurrently. 

Create a logic block of type Background Task, then add the Queue Parallel Processing action. In the actions details, you must specify: 

  • Logic Block—Select the logic block which processes the buckets concurrently. 
  • Table—Select the table which holds the records you want to process. 
  • Expression—Select the criteria for filtering which rows from the table you want included in the batch job.
  • Distinct Fields—Optionally, select distinct fields to define any variables that extend outside of a single row in a query. This allows you to aggregate multiple rows into single rows based on unique values of the selected fields. For example, selecting Order Number as a distinct field would aggregate all records that fall into the same Order Number into a single row. This means the processing logic block is only called for one record per sales order and processes all of the records with the same order number at the same time. 
  • Bucket Field—Optionally, select bucket fields which indicate how the records should be sorted into buckets. You should only specify bucket fields if records must be sorted into specific buckets to avoid contention. For example, you could bucket records based on the Customer ID. This would sort records into buckets based on distinct customer ID numbers. If no bucket field is specified, the system divides the records equally into buckets based on their nwId.
    • Sort—Optionally, specify a sort to organize the records based on a row value. For example, you could sort based on the Submission Date. This is helpful if there is a business rule for a customer that specifies orders must be processed in the order they are submitted. 
  • Post Run Logic Block—Optionally, select a logic block to run after the processing logic block has completed. 

The only required configuration is the filter criteria in the Expression section. 

Once you configure your logic block with the Queue Parallel Processing action, you must attach the logic block to an event which processes a large number of records. For example, a form action or scheduled job which processes a large number of business records. Once the event occurs, the action submits the batch job to run, fetches the records which meet your filter criteria, sorts the records into buckets, then processes the buckets with the processing logic block concurrently. 

This action eliminates the need for a fetch loop, since that process is done in the background task which is initiated.