Docusign Pipeline Assign Signer
I need to use the Docusign action through Pipelines to upload a document for signature and have the actual signature tag auto-assign to the right spot in the document for each applicable signer but haven't been able to do so. I've tried every iteration of anchor tags that I can find in public forums and docs - but nothing gets picked up like I expect. When the document is upload - I can assign the actual signer but then they are prompted to drag the signature block onto the form and sign then. For the purpose of this question - I cannot use Templates so neither pipeline action for templates will suffice. I've triedTemplate Matching in Docusign but I'm not overly confident on the foolproof nature even if I could get it to work so likely not an option either. Essentially what are the options to upload an arbitrary document to Docusign and have the signers already mapped in the document?1st Google Calendar Integration - how to update / delete
I have a Pipeline "Pipeline Create" which adds an "Event" to a Google Calendar, when an entry is made in a QuickBase "Events" table. Yay. But I can't figure out how to update that Google Calendar entry when the Quickbase record is edited. The update step seems to want me to lookup an entry in the Google calendar and to specify an Event ID. But how to I set that Event ID in the "Pipeline Create" Pipeline which created the calendar entry? ------------------------------ Mark Shnier (YQC) Quick Base Solution Provider Your Quick Base Coach http://QuickBaseCoach.com mark.shnier@gmail.com ------------------------------
Pipeline Only Shows Default Data? Which Should Be Deleted?
So we are using the "Simple Project Manager" App to manage our projects now, and I've ran into a pipeline issue. I'm trying to link the status of one of my tables in a separate app to create a new task in a project for me. I feel like it should be set up correctly, however when I go to set a "Related Project", it only gives me options from the default data set in the project management app. Which at one point, the project management app prompted me to wipe? It doesn't show any of my projects, just the stock example ones. Any ideas for something I might be missing?
Pipeline not triggering
Can anyone see why this pipeline doesn't trigger when # of REQUEST DECISIONS APPROVED = 7. If any other info is needed to help me, please let me know. (some info has been xxx'ed for security reason) -------------------------------------------------- # NOTIFICATION REQUEST FULLY APPROVED # # Account slugs: # - quickbase[aaa]: PIPELINES <None> --- - META: name: NOTIFICATION REQUEST FULLY APPROVED enabled: true - TRIGGER quickbase[aaa] 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" <bbb>' 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[aaa] 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" <ccc>' 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[aaa] 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" <ccc>' 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}}' ...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}}' ...
Linking child records to parent inside pipeline
How can I link child table records to a parent table record in Quickbase using a pipeline? Each record in the parent table has multiple associated records in the child table. I want to automate this linking process within a Quickbase pipeline. Is this achievable, and if so, how?
Changing ownership of pipelines
We have created a service account to manage pipelines (as suggested by QB), which seems to be good way to handle multiple developers working on our account. However, we have dozens of pipelines that I need to change ownership of in order to take advantage. I'm really hoping someone has a better solution than what QB is suggesting because this is wild for changing ownership of an existing pipeline. https://helpv2.quickbase.com/hc/en-us/articles/10943861915284-Transferring-ownership-of-a-pipeline
