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

Question

Question

Is There a Way to Not Break Action History to New Page?

asked on March 5, 2014

When you check the box to Include Action History when using the Save to Repository task, is there a way to not have it break to a new page and instead just add to the bottom of the form?

0 0

Replies

replied on March 20, 2014

Is this an option that could be added in a future version of Forms?

0 0
replied on March 20, 2014

I would also like to see this as an option, but did my suggestion work?

0 0
replied on April 23, 2014

Hi Blake,

 

Action History has similar concept as a document's revision history.

 

So it's always the first page.

0 0
replied on April 24, 2014

Would it be possible to add a feature that allowed someone to say whether they wanted it on it's own page or on the page with the form? We have a case where our Special Education department currently has to print out a form and it's one extra page that has to be printed with hardly any information on it.

0 0
replied on November 11, 2014

I am gonna try playing with this, but I was thinking if we make a new form, one that's empty, and use that in a save to repository before we save the actual form we want, we should be able to have the action history by itself that we can then use Workflow to move in front of the other pages.

replied on March 6, 2014

I am not that familiar with this option, but are you saying the action history is just adding the history box from the form on the next page instead of at the bottom of the page that contains the end of the expected page?

0 1
replied on March 6, 2014 Show version history

I wouldn't say the expected page, but yes it puts on the next page instead of at the bottom of the page that contains the form.

0 0
replied on March 6, 2014

This might be to do with the expected use case for this feature. They likely do this so one can separate out that page. 

 

Is it a big deal that you do not have that information on the same page? Is it not possible to use the full-text from that last page with the history to be put into a multi-value history field in a template? Would that solve the problem?

0 0
replied on March 6, 2014

It solves a concern for our special services department. We have physician referrals that even though they are processed electronically they need to be printed out to be put into a child's paper file for auditing reasons until we can make the rest of the audit file electronic as well.

 

By putting the action history on the same page as the form instead of breaking to a new page, it saves paper and the likelihood of losing the second page.

0 0
replied on March 6, 2014

Also, You might want to take note of the prospect of using the "Save to Laserfiche" functionality which will save the form exactly as it appears on the screen when submitted. That should keep the history information in the same page (and go over to the next page if it takes up too much space)

0 0
replied on March 6, 2014

Kenneth, it is when using the "Save to Laserfiche" function that you enable including the action history.

0 0
replied on March 6, 2014

So have you tried the "Save to Repository" service task?

0 0
replied on March 6, 2014

Yes

0 0
replied on March 6, 2014

So I have an interesting Idea.

 

What if you use javascript to hide the built in Forms history box on the form, but then have that exact code be rendered in a Custom HTML field. 

 

Then you turn off the saving the history information option since it should already be a part of the form since it was a part of the form fields itself when it was submitted.

0 0
replied on March 7, 2014

based on my suggestion above, Try using this information: http://www.w3schools.com/jquery/html_clone.asp

 

you should be able to clone the history box to a custom HTML field and then hide the history field afterwards and be all set. This way the history would be forced into the saved image of the form.

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

Sign in to reply to this post.