Is it feasible to generate PDF, display, ask for signature and save

[Griff]

I need to enable workers to create a Job Safety Analysis (JSA) on each job they do. The format required is too complex and data intense to use traditional fields going down the page since every line item on the JSA comprises multiple long and short text fields.

Therefore I propose creating an app where the user can select just the specific elements they need to build into the form. I then want the app to generate a form, using a Google Doc template, displaying all the relevant data in a table and display the form for the user to study, and thereafter sign in the app confirming he has read and agreed to the document. From there, the PDF needs to be re-created with the worker’s signature and emailed and/or saved.

Before I start on the project, is this feasible, or is it beyond the scope of AppSheet? Is there a sample app that does something similar?

Rob

[Aleksi]

Hi, yes this is possible to do with Appsheet… though it’s not simple one, but doable. You can’t choose elements but you can generate the form with correct questions through the app and then start to use it. That’s a tricky part.

The rest of the app is quite basic like adding Workflow/Emails features. Unfortunately we don’t have such a sample app at this moment that could cover all of this. Workflow sample apps you can find from www.appsheet.com/sampleapps

[Griff]

Thanks. I think I am going to have to work out the max number of selections and have a form with that many drop downs. Then use those answers to generate the pdf etc. Using parent/child tables to enable unlimited numbers of selections will make the app messy to use.

[Russell_Smith]

Griff. I am new to appsheet and came across your post about generating JSAs. This is exactly the next app im attempting to tackle. Have you had success?

[Griff]

Hi Russell,

It looks like you’re new to the community - welcome.

Yes I now have a model that works for us in most instances using two variants of a method that Aleksi put me on to.

For more complex tasks, where we have specifically developed JSA’s, I have an ENUM LIST field called JSAs Required. The user can select from the half a dozen or so listed JSA’s and then I use a Word Documents with sections like the following:

<<IF:In(”EWP/ Boom Lift/Sissors Lift” ,[JSAs Required]) >>
In here I have the JSA with appropriate mappings to fields like customer name, address, etc
<< END>>

For more routine tasks I have a field called Tasks that is likewise based on an ENUM List. In this case the ENUM List is based on a table called Tasks with fields called Task Step; Existing; Before Risk; Controls; Responsible; After Risk; Reviewed by: Reviewed When.
The user can select multiple Tasks like “boom lift operation”, “Cleaning concrete slurry off tank”, “Mixing SIKA HH”, “Using Angle Grinder” etc.
The same Word document referred to above has a seciton as follows

<<IF: IsNotBlank([Tasks]) >>
In here I have a standard header and footer and in between is a table with information from my Tasks table for the selected tasks
<< END>>

Using another field, the user enters the email address of the site supervisor and a workflow generates an email to the site supervisor with a message asking them to print off the PDF attachment and give to our workers.

Some of the site supervisors have suggested that our management should prepare, supply and print them, but they usually respond favourably when we tell them that it’s the worker who is meant to prepare the JSA, not management, and the fact that it goes to them to print means they have a record that it was done and signed off by our staff.

Hope that gives you some ideas