mklybor
commented
1 year ago Whoa. Lots of potential uses for this. Awesome!
Sent from my iPhone
On Apr 12, 2023, at 3:14 PM, Alex Sirota @.***> wrote:
Now that Make has a Forms app (designed by Tiberiu Socaci from wemakefuture), it is possible to build a front end for operationalizing the QBWA scenarios. You can install the app with this private Make app invite.https://www.make.com/en/hq/app-invitation/7b9bf0059342ecd8adbecd06f4270afd
Note that the Form app currently only allows prefilling of text fields but eventually it will support all other UI components like radio/checkboxes, date and numeric fields and drop downs.
The forms app allows you to configure a and deliver a form via webhook:
This scenariohttps://us1.make.com/163133/scenarios/865567/edit serves a sample form as well as allows you to retrieve data from a data store to prepopulate the text fields of the form. It is running on the NPC Sandbox.
The scenario to render the form is invoked from a webhookhttps://hook.us1.make.com/8jn6txl1r91ykehmo5iscx2f44zh9fjf and allows one query param - key - which can preload a data store record by key into the form.
[image]https://user-images.githubusercontent.com/458134/231559392-b99c3f86-8289-48e0-9eb9-95eb134f8a28.png
In effect make is a forms server with ability to read/write data from a data store.
The Forms app has a curious feature to submit the posted data from the form to a webhook. Thus this scenario https://us1.make.com/163133/scenarios/865866/edit is the "Form Data Saver Updater"
[image]https://user-images.githubusercontent.com/458134/231559784-e2eee33d-746d-46fc-8c26-73b3cdd5163f.png
The webhook response in this scenario is returned back to the user after submitting the form so this can be customized in a variety of ways including rendering the form again in the response rather than the current UI.
With this technique, along side the Make API it is possible to build a customer-facing UI to do a variety of things for the scenario post installation:
- Configuration of the data store can be made easier by allowing the form to read QuickBooks Online data and render the option in the form.
- Collecting the various requirements for the config data store can be made in a form, submitted to write into the QBWA data store
- Updating the data store can be made by reading the data store and prepopulating the form for subsequent editing
- Manual rerun of scenarios, voiding of invoices and other utilities can be added here as well since this will be running along side the scenarios inside
An NPC only form can also be made to possibly install, upgrade scenarios remotely via the Make API although I think this is a secondary priority. We can also monitor our customers scenarios for errors in one dashboard as well as see the "health" of their Make instances.
Food for thought which is a fairly large project but I think can be incrementally developed to help us as QBWA adoption continues to grow, much better than anticipated.
— Reply to this email directly, view it on GitHubhttps://github.com/NewPath-Consulting/quickbooks-for-wildapricot/issues/110, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABZEZEICP6TVROW35CTF7J3XA35I3ANCNFSM6AAAAAAW4C7EEQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Now that Make has a Forms app (designed by Tiberiu Socaci from wemakefuture), it is possible to build a front end for operationalizing the QBWA scenarios. You can install the app with this private Make app invite.
Note that the Form app currently only allows prefilling of text fields but eventually it will support all other UI components like radio/checkboxes, date and numeric fields and drop downs.
The forms app allows you to configure a and deliver a form via webhook:
This scenario serves a sample form as well as allows you to retrieve data from a data store to prepopulate the text fields of the form. It is running on the NPC Sandbox.
The scenario to render the form is invoked from a webhook and allows one query param -
key- which can preload a data store record by key into the form.In effect make is a forms server with ability to read/write data from a data store.
The Forms app has a crucial feature to submit the posted data from the form to a webhook. Thus this scenario is the "Form Data Saver Updater"
The webhook module in this scenario is "connected" to the first scenario in the forms app config:
The webhook response in the Form Data Saver Updater scenario is returned back to the user after submitting the form, and this can be customized in a variety of ways including rendering the form again in the response rather than the current UI or even rendering a bit of a dashboard with links to other forms that can be executed.
With this technique, along side the Make API it is possible to build a customer-facing UI to do a variety of things for the scenario post installation:
An NPC only form can also be made to possibly install, upgrade scenarios remotely via the Make API although I think this is a secondary priority. We can also monitor our customers scenarios for errors in one dashboard as well as see the "health" of their Make instances.
Food for thought which is a fairly large project but I think can be incrementally developed to help us as QBWA adoption continues to grow, much better than anticipated.