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

Question

Question

How to Insert a value from child request form task to Parent request form task

Laserfiche Cloud Workflow
Updated May 28, 2024
asked on May 24, 2024 • Show version history

When user submits a new request form and this request form is a child request to previously submitted parent request form in-progress, we need a variable value from the child request task to be copied to the parent request task form.

Here Parent request and Child request have seperate instance ID, How can I copy a value from child request to Parent request?

How can I achieve this? Any Ideas?

0 0

Replies

replied on May 28, 2024

There isn't a direct way to connect between two different Forms instances.

On self-hosted, I would say to store the value to a database table that the other instance could access via Lookup.  In Cloud, with the lookup table functionality, this might be different.

1 0
replied on May 28, 2024

What defines the relationship of child request to parent request, exactly?

0 0
replied on May 28, 2024

In our process, when a request is submitted, we generate an ID for that request. So when user wants to submit a child request to relate to parent request, they refer the ID which was initially generated for the parent request.

It is possible to copy all files related to child request and move them to parent request folder in the reporsitory using this ID. But I need a way to add an identifier to parent request task form when a child request is submitted. 

As Matthew mentioned, currently we cannot connect or relate two different forms instances.

0 0
replied on May 28, 2024

I'd suggest adding metadata to the parent folder with that generated ID using a workflow when that initial parent request is initiated (or whenever the ID is generated).

When the child request is submitted and references that ID, it should be trivial to search the repository for a folder with that metadata field equivalent to the ID using the "Search Repository" activity, then get the full path of that folder and use that in a "Move Entry" activity.

To move all the files related to the child request, you'd have to do a "Find Entries" activity or "Search Repository" activity using whatever unique identifier you have for the child request, then use the "For Each Entry" activity combined with the previously mentioned "Move Entry" activity to move them all.

If you needed a way to have the submitter of the child request relate it to the parent request ID, you may want to create a SQL table and add a SQL "Insert Data" activity to that first workflow I mentioned (likely also adding some kind of name or descriptor). This SQL table will allow you to add a dropdown on the child request using a lookup rule, so that the submitter can choose which ID the child request is related to.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...