I have a Forms process that requires that a document be uploaded on the first page (starting task). The document that is to be uploaded will be on the LF Repository. What I'd really like to do is start a Business Process on the repository that will bring the selected document into the first page of the Forms Process. Is that even possible?
Question
Question
How to pass a document from the Repository to start a Forms process.
Replies
You have a few options for this.
• Option A: You can have a Workflow (the business process) kick off a Forms process using Invoke Business Process, and pass the entry ID as a parameter. In the Forms process, you can insert a hidden field to hold the entry ID (use field rules to always hide) . Then, use the custom HTML to write something like:
<iframe src="https://ServerName/laserfiche/DocView.aspx?db=RepositoryName&docid=EntryID#?mode=embed" width="100%" height="800px"><p>Message displayed when the browser does not support iframes.</p></iframe>
In the above URL, change the ServerName and RepositoryName to the ones you are using. The Entry ID should use the variable you passed in from Workflow and will look something like: {/dataset/Entry_ID_for_Document}, depending on how you named your variable in Forms. If you want to make the embedded document collapsible (show/hide), put it into a collapsible Section.
• Option B: Embed the Forms process as a custom tab in the repository. You may still want to create a hidden field in Forms and pass the entry ID of the document to it. To embed a custom tab in the Web Client, log in as a Windows account with administrative privilege. Go to Options, then select Display. The section Tabs should let you configure a custom URL such as a Forms process. You can pass parameters to the form by appending a question mark and a variable name. For example, to pass "123" to a variable named "Entry_ID": https://servername/Forms/ProcessAddress?Entry_ID=123
The ability to create custom tabs in the Web Client, and the ability to restrict them to specific folders and templates, is fairly new. Depending on your needs and your software version, you may wish to use option A.
Hope that helps!
To expand on Karina's post, we are currently in the middle of a project that is very similar. What we do is generate the Web Access URL in workflow based on the document entry ID and bring that document back in the next step of the process in an iFrame and displaying it side by side with fields. That allows us to use import Agent to generate the pages of the document to display in an iFrame.
This is another option if you want to display the uploaded document alongside your next steps in the process.