CONTACT USBack to MinistryPlatform Site
Your Knowledge Base is moving on 3/25/24! Our new Help Center provides all the articles you know and love (plus so much more) in a one-stop shop. Ask your SPoC for details!

Process Fields

 

A Process is a planned course of action that is called upon when certain conditions are met in relation to one record on one page. We've included some default processes, but you can create your own processes to help you do YOUR church YOUR way. The sky's the limit, so don't be afraid to get creative!

  • Process Name: A short descriptive title for the workflow (for example, Event Approval).  Keep the name as short as possible. 
  • Process Manager: The MinistryPlatform user who is responsible for this Process. This is also the User who will receive a Task if it cannot be properly routed to another User.
  • Active: Must be True for this workflow to fire.
  • Description: A longer explanation of the workflow’s purpose (for example, "When future events are added to the system they need to be approved.  If the event dates are changed OR the visibility level of the event is changed this workflow is invoked again").
  • On Submit: An SQL statement that will be part of the SET clause of an UPDATE statement that runs when the workflow is submitted (for example, _Approved = 0). Because this is used in the SET clause, the Table Lookup Convention is not supported. This should always be <Field_Name> = <value> and the field name must be one in the table associated with the Process.
  • On Complete: An SQL statement that is part of the SET clause of an UPDATE statement that runs when the final step of the workflow completes successfully (e.g., _Approved =1). Because this is used in the SET clause, the Table Lookup Convention is not supported. This should always be <Field_Name> = <value> and the field name must be one in the table associated with the Process.
  • Trigger Fields: A list of fields on the target record which will trigger the Process when updated. Only field names should be listed. The field does not support names qualified with table names or brackets. Leave this blank to trigger the Process for changes to any field. Separate multiple fields with commas. Any field in the list triggers the Process (for example, Event_Start_Date, Event_End_Date, Visibility_Level_ID). 
  • Dependent Condition: An SQL statement that is used in a WHERE clause to determine if the record that was edited should trigger workflow. This can be as simple as Milestone_ID = 90 or a more complicated SQL statement (for example, Event_Start_Date >= GetDate() or Milestone_ID IN (2,6,7)).
Table Lookup convention is not supported for this field (the Advanced Search Tool generates code using this convention). If you are concerned about your code, review the Table Lookup Convention.
  • On Create: A True/False field. If True, this Process evaluates the trigger field and dependent condition when a new record in the defined Table Name is created. 
  • On Update: A True/False field. If True, this Process evaluates the trigger field and dependent condition when an existing record in the defined Table Name is updated. 
  • Table Name: The table to which this workflow applies. This is the table where the record is added or edited that causes the workflow to trigger (for example, Events). Previously, this was the Record Type (Page Name) field. Any existing values were automatically updated to the Page's Table as appropriate as part of the Platform Winter 2019 update.