@Ember KrumwiedI think what you are describing is achievable. However, in order to allow users to record a response without logging in to Quickbase you'll have to make a choice:
Both have their own risks to consider and will depend on your tolerance.
Because this will be an anonymous response, you also won't be able to leverage native user data about who approved or denied the request. So you'll either need to have the approver fill that data or make the URL unique enough to only apply to the recipient of the notification.Let's assume our risk tolerance aligns with the first option. Here is how I would do it.
URLRoot() & "db/" & [_DBID_RESPONSES]
& "&_fid_6=" & URLEncode([Record ID#])
& "&_fid_7=" & URLEncode("Approve")
& "&z=" & Rurl()
In this example, fid 6 is Invoice Record ID and fid 7 is the Approval Choice.Once the User saves their response, the workflow should kick off.I recommend consulting with a QuickBase expert or a developer to help you determine the right level of risk for your application.#EOTI #urlformula #Pipelines #rolesandpermissions #Notifications/Email