If you have a comment on this topic, contact Aptify Documentation. If you want to return to the Aptify Community Site, please click here.

Linking Sample Process Flow Steps Together

This topic describes how the developer linked the four individual steps into a single process flow. The four steps include the following possible result codes:

  • Step 1 (Check Rental Agreement Return Condition): These result codes are defined by the rule's VBScript:
    • END: Result when vehicle not being returned in this save operation.
    • DAMAGED: Result when vehicle is returned damaged.
    • NEXT: Result when vehicle is being returned but is not damaged.
    • FAILED: Result when step fails.
       
  • Steps 2 and 4 (Create Service Ticket for Damage/Create Service Ticket for Service): These result codes flow down from the Create Service Tickets Record process component:
    • Success: Result when new record created successfully.
    • Failed: Result when step fails.
       
  • Step 3 (Check Rental Agreement Return Mileage): These result codes are defined by the rule's VBScript:
    • SERVICE: Result when vehicle requires scheduled maintenance: oil change and/or major tune-up.
    • END: Result when vehicle does not require scheduled maintenance.
    • FAILED: Result when step fails.

The developer followed these steps to link the steps into a process flow:

  1. Create a Result Code Link between Step 1 (Check Rental Agreement Return Condition) and Step 2 (Create Service Ticket for Damage) for the DAMAGED result code.
    • If a vehicle is being returned damaged, proceed to the step to create a Damage Service Ticket.
    • See Linking Process Flow Steps Together for information on creating result code links.

      Create Step Result Code Link
  2. Create a Result Code Link between Step 1 (Check Rental Agreement Return Condition) and Step 3 (Check Rental Agreement Return Mileage) for the NEXT result code.
    • If a vehicle is being returned but is not damaged, skip the step to create a Damage Service Ticket and proceed to the step that determines if Scheduled Maintenance is required.
       
  3. Select Step 1 to load its Properties and click the Action Map tab.
  4. Add the FAILED result code for Step 1 with an Action of End Process.
    1. Click the Add Map button and enter FAILED (do not check the Success box).
    2. Set the Action to End Process.
    3. Enter FAILED for the Process Flow Result Code to tie this result to the Process Flow's results.
       
  5. Add the END result code for Step 1 with an Action of End Process.
    1. Click the Add Map button and enter END (also check the Success box, which this is a successful outcome).
    2. Set the Action to End Process.
    3. Enter SUCCESS for the Process Flow Result Code to tie this result to the Process Flow's results.

      Step 1's Action Map
  6. Create a Result Code Link between Step 2 (Create Service Ticket for Damage) and Step 3 (Check Rental Agreement Return Mileage) for the Success result code.
    • If the step to create a Damage Service Ticket is successful, proceed to Step 3 to determine if the vehicle also required Scheduled Maintenance.
       
  7. Select Step 2 to load its Properties and click the Action Map tab.
  8. Configure the Failed result code for Step 2 with an Action of End Process and enter FAILED for the Process Flow Result Code to tie this result to the Process Flow's results.
  9. Create a Result Code Link between Step 3 (Check Rental Agreement Return Mileage) and Step 4 (Create Service Ticket for Service) for the SERVICE result code.
    • If a vehicle being returned requires scheduled maintenance, proceed to the step that creates the scheduled maintenance Service Ticket.
       
  10. Select Step 3 to load its Properties and click the Action Map tab.
  11. Add the END result code for Step 3 with an Action of End Process.
    1. Click the Add Map button and enter END (also check the Success box, which this is a successful outcome).
    2. Set the Action to End Process.
       
  12. Add the FAILED result code for Step 3 with an Action of End Process.
    1. Click the Add Map button and enter FAILED (do not check the Success box).
    2. Set the Action to End Process.
    3. Enter FAILED for the Process Flow Result Code to tie this result to the Process Flow's results.
       
  13. Select Step 4 to load its Properties and click the Action Map tab.
  14. Configure the Success result code for Step 4 with an Action of End Process and enter FAILED for the Process Flow Result Code to tie this result to the Process Flow's results.
  15. Configure the Failed result code for Step 4 with an Action of End Process and enter FAILED for the Process Flow Result Code to tie this result to the Process Flow's results.
  16. Save the Process Flow record.
    • When finished, the four steps are linked together, as shown below.

       Linked Process Flow Steps
  17. Create the Event Handler to fire this Process Flow for the BeforeCommitTransaction event when a Rental Agreements record is saved. See Creating Event Handler and Testing Process Pipeline.
    • At this point, you generally can also test a process flow using the Process Flow Debugger Tool. See Testing Process Flows. However, since this process flow includes a GE object input property that the debugger does not accommodate, the debugger can not be used in this case.

Copyright © 2014-2019 Aptify - Confidential and Proprietary