Gravityflow

Filters

• Limit
  • Entries by search criteria
  • Entries by form id
  • Entries displayed using the inbox short code
• Modify
  • Column content
  • Columns displayed
  • Field or column values
  • Pagination criteria
  • Sorting criteria
  • Submitter column value
  • URL to link to entry
  • URL text and attributes of the link to entry
• Admin view
  • Modify the field columns displayed in the inbox page in the admin UI

Default functionality

• If notifications can be sent from the website hosting gravityflow, you can use functions such as the form submission step to manage form submissions.

Different system eg CRM, sends notifications

If you need participants to submit forms as part of a workflow, and you need to send notifications from an independent system, do the following.

• The system sending notifications, for example a third part crm, must be able to send a link in an email that includes
  • URL to the child form page
  • append a query such as/?master={entry-id-master}
  • Create a workflow step in the master to hold the entry using the incoming webhook step.
• The child form must include
  • Hidden field that can be populated by a query string with the name used in the query, in this example, ‘master’
  • Use gravityperks autopopulate anything to populate other fields in the child form linking to the master form where the master form entry id is the same as the value stored in the hidden field.
  • Create a workflow in the child form
    • Step 1: update fields in the parent form on submission of the child form.
    • Step 2: Send outgoing webhook
      • Outgoing Webhook URL https://domain.com/wp-json/gf/v2/entries/{Entry ID: Master:1}/workflow-hooks
      • Raw Body
        • {
        • “workflow-api-key” : “Insert api key from incoming webhook step in master workflow”,
        • “workflow-api-secret” : “Insert api secret from incoming webhook step in master workflow”
        • }
  • These steps update the master form entry, then release the entry to continue the workflow.

The workflow_hash allows an anonymous user to submit a form entry in a Form Submission Step

The gflow_access_token allows the required behavior to occur.

• workflow_form_submission_link:
  • /?id=YY&workflow_parent_entry_id=XX&workflow_hash=

• workflow_entry_link:
  • /workflow-inbox/?page=gravityflow-inbox&view=entry&id=XX&lid=XX&gflow_access_token=

• workflow_entry_url:
  • /workflow-inbox/?page=gravityflow-inbox&view=entry&id=13&lid=62&gflow_access_token=
• workflow_inbox_link:
  • /workflow-inbox/?page=gravityflow-inbox&gflow_access_token=

• workflow_inbox_url:
  • /workflow-inbox/?page=gravityflow-inbox&gflow_access_token=

• workflow_cancel_link:
  • /workflow-inbox/?page=gravityflow-inbox&view=entry&id=XX&lid=XX&gflow_access_token=

• workflow_cancel_url:
  • /?page=gravityflow-inbox&view=entry&id=XX&lid=XX&gflow_access_token=

• workflow_note:
  • workflow_timeline:
    webg: January 29, 2023 at 1:31 pm
    Sent to step: ANON: Create Entry DEMO Gform 2: Anonymous User Submission
  • webg: January 29, 2023 at 1:23 pm
    Sent to step: HOLD STEPID 30

• Form Submission: January 29, 2023 at 1:22 pm
  • /workflow-inbox/?page=gravityflow-inbox&view=entry&id=XX&lid=XX&gflow_access_token=

• workflow_approve_token:
  • eyJpYXQiOjE2NzQ5OTkwODYsImV4cCI6MTY3NTE3MTg4Niwic3ViIjoiZW1haWx8YW5kcmVuZWxsaW5AZ21haWwuY29tIiwic2NvcGVzIjp7InBhZ2VzIjpbImluYm94Il0sInN0ZXBfaWQiOjI3LCJlbnRyeV90aW1lc3RhbXAiOiIxNjc0OTk2OTI1IiwiZW50cnlfaWQiOjYyLCJhY3Rpb24iOiJhcHByb3ZlIiwidXNlcl9pZCI6MX0sImp0aSI6IjYzZDY3NTJlYmRhNWQifQ%3D%3D.21ef1b76bd538cbe60d7f1015f3544484f42c492005dbe1534385e096aeee929

• workflow_reject_link:
  • /workflow-inbox/?page=gravityflow-inbox&view=entry&id=XX&lid=XX&gflow_access_token=

• workflow_reject_url:
  • /workflow-inbox/?page=gravityflow-inbox&view=entry&id=XX&lid=XX&gflow_access_token=

• workflow_reject_token:
  • eyJpYXQiOjE2NzQ5OTkwODYsImV4cCI6MTY3NTE3MTg4Niwic3ViIjoiZW1haWx8YW5kcmVuZWxsaW5AZ21haWwuY29tIiwic2NvcGVzIjp7InBhZ2VzIjpbImluYm94Il0sInN0ZXBfaWQiOjI3LCJlbnRyeV90aW1lc3RhbXAiOiIxNjc0OTk2OTI1IiwiZW50cnlfaWQiOjYyLCJhY3Rpb24iOiJyZWplY3QiLCJ1c2VyX2lkIjoxfSwianRpIjoiNjNkNjc1MmViZWE2MyJ9.cc46dace17275bf747597c4bb00f32d974a45a63af535f4d795c294ea26081a4

Advanced Shortcode Attributes

The shortcode supports the following attributes for the inbox and status pages:

id_column – show or hide the ID column in the inbox and status pages. For example, hide the ID column:

submitter_column – show or hide the submitter column in the inbox and status pages. For example, hide the submitter column:

step_column – show or hide the step column in the inbox and status pages. For example, hide the step column:

form – constrain the entries to the specified form ID. For example, constrain the entries to the form ID 1: 

title – specify a title that will appear on the both the inbox/status list and the entry detail page. For example:  

timeline – show or hide the timeline. Default = true. Example:

step_status – show or hide the step status on the entry detail page. Default = true. Example 

workflow_info – show or hide the workflow info. Default = true. Example: 

sidebar – Use two columns or one. Default = true. Use false to use just one column. Example 

actions_column – show or hide the approval actions column in the inbox page. For example:

due_date – show or hide the due date column. Default = false. Example:

back_link – show or hide the ‘Return to List’ link at top of main column of entry detail view. Example

back_link_text – Customize the text to display when the back_link parameter is set to true. Example

back_link_url – Customize the url to return users to from entry detail page when the back_link parameter is set to true. Example . Very useful if you have pages with Gravity Views included.