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

Question

Question

Ways to Split form pages in Business Process in LF Cloud

Forms Laserfiche Cloud How To Business Processes
Updated November 3
asked on October 30

I have a scenario to email the form's first page to the email provided in the form. 

LF (Form contains 2 pages) -> route to email service task (email will contain only the first page of the form) any thoughts on how to split the form's pages? 

 

0 0

Replies

replied on October 30

You can add a Field Rule to hide Page 2 when the Step Name is not the name of your starting step (and not any assigned tasks /archives that may exist between). This way when it reaches the Email Activity the second page will be hidden.

2 0
replied on October 30 • Show version history

I see an option in the field rule to hide page 2 but not the step name populates in the condition section 

0 0
View 2 previous replies
replied on October 30

Oh this is the Classic Designer. You have to transfer the current step into a field so you can reference it as a field value.

Add an HTML field and put the following syntax

{/dataset/_current_step_name}

Give it a class name of "step"

Create a Single Line with a name of Step and class name of stepOutput

Then add the following JS

$(document).ready(function(){
   let step = $('.step').text();
   $('.stepOutput input').val(step).change();
});


Now create a rule to show Page 2 when Step is Start or whatever your starting object name might be if changed from default.

If you switch to the modern designer you can reference the step directly in the rules, but you lose many code features. I usually recommend the Classic for coders and the Modern for non-coders.

1 0
replied on October 30

thank you, I will try this out.

0 0
replied on November 3

The way this works is: User task (A) has page 1 and page 2 with field rule set as hide page 2 when step is email and email is not blank 

once email task is complete it outflows to save to repository task where only page 1 is retained, and page 2 is lost!  

Task (a) has page 1 and page 2 -> if email is provided then send email with only page (1) and save repo with page 1 and page 2, and if email is not provided then default path is save to repo task with page 1 and page 2. 

0 0
replied on November 3

Try putting the archive before the email. There is no way to see what the step is going to be when it hits the archive, it could still be stuck on Email.

0 0
replied on November 3

This is my field rule set in user task, 

user task flow is as 

 still, it doesn't show Page 2 in the repository

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

Sign in to reply to this post.

Details
Related Posts
Loading ...