Forum Discussion

kheatley's avatar
kheatley
Qrew Member
2 months ago

Why doesn't pipeline trigger

I went in and updated my records to make sure the field # of REQUEST DECISIONS APPROVED = 7 to try to trigger this pipeline but it didn't and I'm not sure why.  Can anyone see what I'm missing?  If there's other info needed to help understand, let me know.

Kim

------------------------------------------------------------------------------

# NOTIFICATION REQUEST FULLY APPROVED
#

# Account slugs:
#  - quickbase[qAyK4n7]: PIPELINES <None>
---
- META:
    name: NOTIFICATION REQUEST FULLY APPROVED
    enabled: true
- TRIGGER quickbase[qAyK4n7] record on_update -> a:
    FILTERS:
    - AND:
      - of_request_decisions_approved equals 7
    inputs-meta:
      export_fields: '"# LEAVE REQUESTS TOTAL, # of  PENDING REQUESTS AA, # of  PENDING
        REQUESTS ASSOC HEAD, # of  PENDING REQUESTS DEPT HEAD, # of  PENDING REQUESTS
        DIRECTOR, # of  PENDING REQUESTS DIV ABCMP, # of  PENDING REQUESTS DIV ASTRO,
        # of  PENDING REQUESTS DIV NUPAT, # of  PENDING REQUESTS DIV NUPAX, # of  PENDING
        REQUESTS FCR, # of  PENDING REQUESTS HR, # of REQUEST DECISIONS APPROVED,
        # of REQUEST DECISIONS DENIED, # of REQUEST DECISIONS PENDING, % APPROVED,
        APPROVAL PROCESS, APPROVAL PROCESS_copy, Add DECISIONS LOG, Add NOTIFICATIONS
        LOG, Add REQUEST DECISION, CB NOTIFICATION FINAL APPROVAL, CONVERTED LIST
        APPROVER EMAILS APPROVED, CONVERTED LIST APPROVER EMAILS DENIED, CONVERTED
        LIST APPROVER EMAILS PENDING, CT APPROVED BY ROLE, CT DECISION SUMMARY REF,
        CT DENIED BY ROLE, CT LIST APPROVER EMAILS APPROVED, CT LIST APPROVER EMAILS
        DENIED, CT LIST APPROVER EMAILS PENDING, CT PENDING BY ROLE, DC Approved CB,
        FACULTY - Last Modified By, FACULTY - Record ID#, FACULTY ACTIVE, FACULTY
        DIVISION, FACULTY EMAIL, FACULTY MIT ID, FACULTY NAME, FACULTY NAME LF, FACULTY
        TITLE, FACULTY TITLE - TITLES, FACULTY USERNAME REF, FINAL APPROVAL CB, LEAVE
        DATE END, LEAVE DATE START, LEAVE FUNDING, LEAVE FUNDING MORE, LEAVE FUNDING
        SHORT, LEAVE PLANS, LEAVE PLANS MORE, LEAVE PLANS SHORT, LEAVE SEMESTER, LEAVE
        STATUS, LEAVE STATUS_copy, LEAVE SUMMARY, LEAVE TYPE, LEAVE TYPE - LEAVE TYPES,
        LEAVE YEAR, LEAVE YEAR PREVIOUS, PROGRESS BAR TO APPROVAL, REQUEST DECISION
        - APP DECISION COMMENTS, REQUEST DECISION - APP DECISION STATUS, REQUEST DECISION
        - APP DECISION TIMESTAMP, REQUEST DECISION - APPROVER EMAIL, REQUEST DECISION
        - APPROVER FIRSTNAME, REQUEST DECISION - APPROVER ROLE+DIV, REQUEST DECISION
        - APPROVER USERNAME REF, REQUEST DECISION - Approved CB, REQUEST DECISION
        - DECISION SUMMARY, REQUEST DECISION - Date Created, REQUEST DECISION - Date
        Modified, REQUEST DECISION - FACULTY NAME LF, REQUEST DECISION - LEAVE REQUEST
        - FACULTY NAME LF, REQUEST DECISION - Related FACULTY, REQUEST DECISION -
        Related LEAVE REQUEST, Related FACULTY, Related LEAVE TYPE, Related REQUEST
        DECISION, SAVE AND DISPLAY, SAVE AND KEEP WORKING, SAVE REQUEST, STATUS FILTER"
        <78, 46, 43, 42, 44, 48, 49, 50, 51, 47, 45, 41, 40, 39, 56, 71, 75, 23, 38,
        19, 107, 100, 106, 104, 53, 92, 55, 99, 102, 101, 54, 52, 35, 36, 31, 32,
        33, 16, 29, 30, 81, 80, 34, 94, 11, 10, 13, 60, 73, 12, 59, 72, 9, 14, 76,
        58, 6, 21, 7, 8, 57, 88, 86, 87, 91, 95, 85, 84, 93, 89, 27, 28, 70, 68, 69,
        26, 15, 20, 25, 64, 67, 83, 82>'
      table: '"FACULTY LEAVES APP: LEAVE REQUESTS" <buph3g78d>'
      trigger_fields: '"# of REQUEST DECISIONS APPROVED" <41>'
      trigger_on_all_fields: 'false'
- a<>ACTION quickbase record update -> b <=> a:
    inputs:
      cb_notification_final_approval: 'true'
- IF:
  - AND:
    - a<>of_request_decisions_approved !equals 7
  - THEN:
    - ACTION quickbase[qAyK4n7] record create -> c <=> a:
        inputs-meta:
          export_fields: '"NOTIFICATION EMAIL, NOTIFICATION TYPE, NOTIFICATION USERNAME
            REF, NOTIFICATION NAME APPROVER, NOTIFICATION NAME REQUESTOR, Related
            LEAVE REQUEST, Related LIST NOTIFICATION, Related REQUEST DECISION" <8,
            6, 7, 70, 69, 18, 10, 39>'
          table: '"FACULTY LEAVES APP: NOTIFICATIONS LOG" <buph3g8gm>'
        inputs:
          notification_email: xxx@mit.edu
          notification_type: ERROR - PIPELINE (NOTIFICATION REQUEST FULLY APPROVED)
          notification_username_ref: xxx@mit.edu
          related_leave_request: '{{a.request_decision_related_leave_request}}'
          related_list_notification: ERROR - PIPELINE (NOTIFICATION REQUEST FULLY
            APPROVED)
          related_request_decision: '{{a.id}}'
  - ELSE:
    - ACTION quickbase[qAyK4n7] record create -> d <=> a:
        inputs-meta:
          export_fields: '"NOTIFICATION EMAIL, NOTIFICATION TYPE, NOTIFICATION USERNAME
            REF, NOTIFICATION NAME APPROVER, NOTIFICATION NAME REQUESTOR, Related
            LEAVE REQUEST, Related LIST NOTIFICATION, Related REQUEST DECISION" <8,
            6, 7, 70, 69, 18, 10, 39>'
          table: '"FACULTY LEAVES APP: NOTIFICATIONS LOG" <buph3g8gm>'
        inputs:
          notification_email: xxx@mit.edu
          notification_type: LEAVE REQUEST GRANTED  FINAL APPROVAL
          notification_username_ref: xxx@mit.edu
          related_leave_request: '{{a.request_decision_related_leave_request}}'
          related_list_notification: '5'
          related_request_decision: '{{a.id}}'
...

No RepliesBe the first to reply