Process Studio Connectors: Filevine

  • Updated

When admins select Filevine in the App field, the Project Type, Event, and Section fields will appear. Configure them using the following steps:

1. Select the Filevine Project Type where the process-triggering event happens. This ensures the event runs only in Filevine projects with that template.
2. Select the Event that determines what will start the automated process.
3. Select a Section based on the event and project type.

Filevine Connector: Available Trigger Events 

Here there is a list of available events list in Filevine.

Available Events The process is triggered when the following occurs in a Filevine project
Form Updated A form is updated.
Collection Updated A collection is updated.
Collection Created A new collection is added.
Collection Created or Updated A collection is created OR updated.
Collection Deleted A collection is deleted.
Taskflow Executed A taskflow is started.
Taskflow Reset

A Reset button is used in a Taskflow.
Contact Created A new contact is added.
Contact Updated An existing contact is edited.

For example:

  • Taskflow Executed event:

  • Taskflow Reset event:

 

  • Taskflow Executed, and Taskflow Reset events are related with elements in Filevine projects configured as follows: Widget Type: Action Button, and Action Button Type: Taskflow Trigger Button.

  • Taskflow Executed and Taskflow Reset events are not related to Neodeluxe Flow Tasks or Advanced Task Management tasks.

Filevine Connector: Trigger Event Sections

The available options in the Section dropdown will vary based on the selected Project Type and Event.

  • Collection-related events
    Displays the sections of the collection that exist in the selected Project Type.
  • Form-related events
    Displays the static form sections that exist in the selected Project Type.
  • Taskflow-related events
    Displays the sections with taskflow-related items that exist in the selected Project Type.
  • Contact-related events
    Displays the sections with contact items that exist in the selected Project Type.

 

  • The created trigger can now be used when building a process.
  • Users can reuse a trigger across multiple processes, meaning that when the trigger is fired, all the processes in which it has been used will be executed.

For example:  For Filevine Projects with Project Type Immigration 2, the Trigger Filters section is configured as follows:

 

 

IF

The Child Over or Under 21 field in the section Family Information is Equals to Yes

OR

The Does Child have United States Status field in the section Family Information is Equals to No.

 

When in a Filevine Project with Project Type Immigration 2 the user enters in the Child Over or Under 21 field, the value Yes,

OR

When in a Filevine Project with Project Type Immigration 2 the user enters in the Does Child have United States Status field, the value No.

The criteria is met and when the associated action to the event is performed in projects with the configured Project Type, the process(es) that use(s) this trigger will be triggered.

For more information about criteria in Neodeluxe, please visit: Understanding Criteria in Neodeluxe.

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.