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

Question

Question

Merging two processes into one.

Forms Workflow
Updated February 23, 2018
asked on February 21, 2018

Good afternoon,

We are in the brainstorming stage of doing something new with two of our business processes. Let's call them B1 and B2

B1 has three forms, and each form has one textbox called first name.

B2 has 1 form, and one field called last name

we are looking for a way so that when we are in second form of B1, with a radio button we can say, I need B2.

Clicking on the button would either embed B2 in an iframe or start the process separately. Completing B2 will resume B1, but only if it was started by B1 in the first place.

If B2 was started manually, then B2 would end on submit.

Any ideas, suggestions?

Thank you,

Raul Gonzalez

0 0

Replies

replied on February 21, 2018

Hi Raul,

It would be easy to embed B2 in an iframe or start the process separately when clicking a button, but it might be hard to "resume B1" after B2 is completed.

For "second form of B1", is it a start event or a user task? When you turn to B2, would you like to save B1 as a draft so filled values can be saved, or is it ok to not save draft and resume B1 fresh new?

And if embed B2 in an iframe, is it acceptable not to save/resume B1 as they are on the same page?

0 0
replied on February 22, 2018

Thanks Rui,

Second form of B1 (Let's call it F2) would be a user task. Saving B2 does not have to save B1 as a draft. It could be fresh new.

If B2 in an iframe is saved, and you walk away from the form, essentially not saving B1F2, then it's ok.

However, now with your break down I foresee more challenges when using iframe.

Somehow we would have to match B1 to B2 once B1F2 has opened B2. First challenge would be to be able to pass a value inside B2 from B1F2.

Then we get into the issue that, what if you walk away from B1F2 after submitting B2. When you come back, you would have to know that you have already submitted B2, otherwise, you will get a duplicate.

I feel that we might need to rethink this strategy.

_____________________________________________________________________________________________________

Our real scenario is that we have a business process with different forms. This business process is shared with a few different customers. We have been tasked to build a form that will be part of "their" process. Some customers want it as part of the existing business process, essentially just incorporating a form in between, and others want it as a separate business process. 

We are trying to find a way to minimize duplication of goods end efforts.

0 0
replied on February 22, 2018

For passing value to B2 from B1F2, you can set it in the embed script like this:

$(document).ready(function(){
  $('#Field2-0').click(function(){
    $('#B2').css('height','500px');
    $.getScript( "http://SERVER/Forms/js/forms-embed.js?v=10.2", function() {
      lfembed = new LaserficheForms.Form(document.getElementById('B2'),{bpid: '2031', host:'http://SERVER/Forms', params: 'Single_Line=value from B1F2',}).getFrm();
    });
  });
  $('#Field2-1').click(function(){
    $('#B2').css('height','10px');
    $('#B2').html('');
  });
});

I have a radio button with id=2 for show/hide B2 and a custom HTML field with the following content on B1F2:

<div id="B2"></div>

For connecting B1F2 and B2, I suggest that you keep an external database for the record. Like you have a unique id for B1F2 which is saved in a db table, and there is a column to indicate if the related B2 has been submitted or not. Pass this unique id to B2 when open it, and after after submitting B2, update the external database (with Workflow). Then on B1F2, use lookup rule to check the external database, and hide the radio button/iframe if B2 has been submitted.

1 0
replied on February 23, 2018

Thanks Rui, this seems promessing and will defensively give it a try.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...