You are viewing limited content. For full access, please sign in.

Question

Question

Forms: Dynamically Load "Next" Form in a Set

asked on May 22, 2017

Hi All,

I'm working on a project that replaces part of a client's new hire process with a LF Forms solution.

Currently, the client's new hires are expected to sign and submit a variable number of Job Hazard Analysis paper forms (number of forms depends on what department they will work within). It's the same form each time, only populated with different information relevant to each individual task.

Optimally, I'd like to setup the business process's Message Start Event to redirect the user to the "next" form after they submit the current one. This seems straightforward enough using the "Redirect to website" option under the "Thank You Message" tab of the Message Start Event. However, I'm not sure how to setup the redirect URL to load the next form. I imagine this might be possible using tokens derived from a lookup table. Please see the image below for reference:

Is it possible to use the [JHAID] values as tokens in the redirect? For example, say a new hire receives an email notification (from Workflow, probably) that they have a "packet" of JHA forms to sign. They click the link in the email and are brought to the above form (sans the "Hidden Fields" section, which would be hidden smiley). They review all the info for Task 3, provide a signature, and click "Submit". Is there a way to then use the [JHAID] or [Task] value for Task 4, to load the "next" form, pre-populated with all the relevant info for Task 4?

Any information about this problem generally, and specifically about Forms URLs, will be greatly appreciated. 

Please let me know if I can clarify any of the above, and thanks for taking time to read my question!

~Rob

0 0

Replies

replied on May 22, 2017

A couple of questions on this. What version of Forms are they using and does each form follow the same process flow?

0 0
replied on May 22, 2017

Hi Blake,

Thanks for the timely reply!

I believe the are using (or will be at time of deployment) Forms 10.2. The process flow will be the same for every form submitted (essentially, "hand variables off to Workflow and end after last form is submitted").

I think I've been making progress. Here's a screenshot of the form currently:

My thought is to populate the "Hidden Fields" section via a lookup to a "JHAPacket" table, with relevant associated values for each department and each department's tasks. Then, I'll use the values to populate this redirect link:

.../Forms/JHAAdminProcess?New_or_Revised=Revised&Department_Dropdown=Fleet&Task_Dropdown={/dataset/Next_Task}

***UPDATE: Got distracted but ended up testing what I explained immediately above--it works! Now to figure out the "Thank You" page...

Thanks!

Rob

0 0
replied on May 22, 2017

If all of the forms will use the same process flow, why not just show or hide sections of that consist of the additional forms based on the values populated instead of creating an entirely different process for them?

0 0
replied on May 22, 2017 Show version history

The problem is that the number of forms requiring a signature is variable depending on the department--each department has its own "packet" of JHA forms (each of which corresponds to a single task/job to be performed by members of that department).

So, the Fleet department might only need signatures for Tasks A - C, but the Parks department may need signatures for Tasks D - P, while Utilities needs signatures for Tasks A - B and F - I. Everything needs to be dynamic as well since this process functions alongside two others--one that allows relevant administrators to individually create new/update existing JHAs (eg, add the JHA for Task A to the Parks Department's "packet") and another process for doing an "Annual Review" of the JHAs, although in theory the review process could be run at any time (it's essentially a batch update/delete for the various JHAs).

I like your approach but unfortunately I do not think it will work for our client since they need the ability to add/change/remove JHAs on the fly.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.