Neptune DXP Documentation
Neptune DXP - Open Edition · 25.0 MTS

Build an end-to-end process flow

This guide builds one process flow from start to finish. Each step adds one part of the process flow and hands the data on to the next, so that by the end you have used most of what Process Flows offers in a single, coherent example.

The scenario is a candidate application review. A candidate submits an internal job-application form, which triggers the process flow with their application as input. A script scores it, a decision routes it by score band, an acknowledgment email on the strong path fans out into two checks that run in parallel, a hiring manager approves or rejects the result, and the outcome is emailed to the candidate.

Overview

The process flow you build exercises these building blocks in order:

  • An interface input that carries the application data into the run.

  • A Run Script node that scores the application and exposes the score as output.

  • A Decision node that routes the candidate by score band.

  • A Send Email node that emails an application acknowledgement email to the candidate.

  • A parallel split with a Wait for Branches node that runs two checks at once and waits for both.

  • A User Task that a hiring manager completes, looping back on rejection.

  • A Send Email node that emails the outcome to the candidate.

Direct application of process flow scenario

Before you build the process flow, it helps to picture how it runs once it is live. This example models the review of an internal job application, from the moment a candidate applies to the email that tells them the outcome of their original application.

  1. A candidate opens the internal job-application form, for example, an app within a user launchpad experience made in the App Designer, and submits their application. Selecting the Submit button triggers the process flow and passes the candidate’s details to it as interface data.

  2. The process flow scores the application, and a Decision node routes the candidate by score band: strong, borderline, or refer to junior role.

  3. A strong candidate receives an acknowledgment email, which fans out into two checks, a reference check and a qualification check, that run at the same time and join before the process flow continues.

  4. A hiring manager reviews the result in the Process Flow Inbox app and selects Approve or Reject. A rejected task loops back for another review.

  5. The candidate receives an email with the outcome, and the run ends.

Throughout, you follow every run in the Process Flows Overview.

You build and test this process flow in the Process Flow Designer first, using a payload you enter by hand. You wire the real trigger, the form button Submit, last, because it needs the finished flow’s identifier from the General tab. See Trigger a process flow from an app or a script.

For the concepts behind these building blocks, see Process Flows and Gateways and branching reference.

Before you begin

Build the process flow

Complete the following tasks in order. Each one continues from the process flow left by the previous task.

  1. Create the process flow

  2. Define the interface

  3. Add a script and expose its output

  4. Add a decision

  5. Acknowledge the application

  6. Run the checks in parallel

  7. Add the hiring-manager task

  8. Email the outcome

Run and monitor

  1. Test the process flow from inside the Process Flow Designer.

  2. Trigger it from a script or app to run it with real data.

  3. Monitor the run in Process Flows Overview.

Reference

Related topics