Reuse process in another table

Hello.

I have a process set up to create a PDF when a record in the Jobs table is changed.  The template contains a Start expression that references a Related Parts column.  It's working beautifully.

However, it's possible the user will update a Part record from the inline Related Parts table located in Jobs Detail View.  In this way the process is not triggered since it's only updating the Part record not the Job record.

So I set the process to be reusable and added to a Parts table update event.  It's requiring either Add or Lookup when I want neither.  I just want the same PDF task ran whether the Job record or Part record is updated.

Is this possible? 

AIFL_0-1721485217432.png

 

 

Solved Solved
2 7 356
1 ACCEPTED SOLUTION


@AI-FL wrote:

Is this possible? 

AIFL_0-1721485217432.png


You absolutely can do what you're wanting, and you're on the right track.

When you select "Lookup" the system is being told to "lookup a record somewhere and run the process on that record" - so you need to provide the ID of the record you want to run the process on.

The alert in the image is letting you know the specific piece of data that's required in order for the process to run:  the Job ID

  • In the Part record, they have a ref connection to the Job - this is the value that you need to provide.

Here's how you can do it:

  1. Click the "Add" button in the task that's calling the process (from your image above)
      - This will create an entry for you to configure
    MultiTech_0-1721570848001.png
  2. The dropdown contains the columns from the table of your process
      - Select the column that's the ID for that table
      - The system is trying to figure out what record to use, this is part of that process (we're telling it what column to look into in order for it to identify the correct record)
  3. The formula space is from the context of where the automation is running (Parts, in your case)
      - Select the column that contains the ref to the Job, as this contains the ID value for the Job record we need to find
      - This is telling the system what ID to use when looking the column you selected in step 2

By giving the system the column to look in, and the ID to look for, the system is able to find the individual record you want... and it will then run the process on that record. 💪

This is how you open a door to incredible modularity and power through automation inside your app. 

View solution in original post

7 REPLIES 7
Top Labels in this Space