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

Discussion

Discussion

Feature Request: Stored path definitions for "Save to Repository" in Forms

posted on September 21, 2017

I know this might be hard to implement, because each form might have different field names, but I thought I'd throw this out there, since if the fields aren't defined the same across forms, forms will at least flag the bad fieldnames.

Recently, I ran into a situation where there were about a dozen different Forms processes, each with a 'Save to Repository' activity that sent the forms to \subfolder\subsubfolder\[lnamefield], [fnamefield] [IDfield]

Except for one, which omitted the space between [fnamefield] and [IDfield], which then created a new folder with different information. 

It would be a real time saver if instead of filling in the destination path for each of a dozen different forms, there could be paths set up in Administration like database connections, and then a particular path can be selected for the save to repository activity, or if the destination path needs to be changed across dozens of Save to Repository processes, it only has to be altered in one place.

0 0
replied on September 26, 2017

I think what I'd be looking for is a path separate from anything else. Though now that I think on it, it's not really all that needed. It's a situation that could be handled in a way that the problem should never come up. 

0 0
replied on September 21, 2017 Show version history

Hi Glen,

Let's make this more clear:

Now in Forms, to save file to repository you need to setup a profile, which is stored in individual processes. The same path might not exist in different profiles.

If you would like the path definition to be saved, are you expecting all the processes are using the same profile? If so, together with path definition, the repository profile need to be saved and can be used in all processes?

This would be like the Forms on Cloud where there is only one profile which is shared among all processes.

0 0
replied on February 16, 2018 Show version history

I think you understand me perfectly Rui.

Now that I think on it, what I'd like is a shared 'Save to Repository Service Task' that can be shared among several similar forms processes. 

A use case would be forms for vendors to submit invoices to Accounts Payable. There would be different forms processes for invoices sent from different vendors, but would all use the same fields and naming convention for creating the repository entry, and all save to \REPOSITORY\AP\Incoming

If a change needed to be made, or a new form needs to be created, it would save a lot of time and prevent human error if a single shared Save to Repository Task was updated, instead of individually updating or changing each task in each of two dozen or more different forms processes. 

0 0
replied on February 21, 2018

Thanks for the feature request, I have added this to our backlog.

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

Sign in to reply to this post.