Submit Your Suggestions For Field View

Hello. The updated form PDF names are only available with VFP integration. It can be difficult to get consensus on how the form name should change, given the 100 character limit of a PDF and the variability of Form Title questions. My hope is to make the information that is contained in the form distribution email more meaningful. https://fieldview.ideas.aha.io/ideas/FV-I-360 And to see if something similar can be done for Task emails. Thank you

About time they cracked on with this one

Glad this has shipped, is this functionality in FieldView without V4P integration?

Any update on this? Been in development for a long time now!

Hi Denise,

we still need to be able to allocate custom names to forms even if they are not being sent to VFP. If we need to email a form it needs to have at least the location in the name to uniquely identify it. Integration with VFP is no the only issue here. If we could customise the names then then they would be sent to VFP correctly as it is now. 

Hi Martina - I can't give dates, but we are working on this. It ended up taking longer than I thought it would because we need to get hardware in place to handle the new "behind the scenes" integration. As you know, the VFP/FV form integration currently depends on email. The new integration will not.

Thank you,

Denise

Hi Denise,

is there any update on this issue? Is there an ETA for implementation?

The Field View and VfP engineering teams are currently working together to solve this issue. Given that we have no control over the length of a form question that has been designated as the form title, we are working towards a better solution. Our goal is to send form PDF, plus all its metadata, to VfP "behind the scenes" rather than in email. Using geek speak, the VfP team has already created an endpoint for FV to use and we are about to begin reviewing to verify it meets your needs. The goal is to have customers use VfP Naming Convention to configure their preferred form name format for these FV form PDFs. We are super excited about solving this longstanding issue! Stay tuned. 

Thank you, Denise Olsen - Field View Product

This would be very helpful! - so difficult to determine your document content with the automated titling.

This really does needs sorting out now . We are using VFP to store these forms but there naming is awful. This must be configurable ( by form or dropbox container) so that we can choose project / sub project / location / author / date / form name / etc etc

This was on my list to raise. It is too hard to decipher between the forms when there are many.

Denise - can't reply to the same suggestion (FV-I-360) you asked for responses on because the suggestion has been merged...

When you have a form template that's raised regularly, then the Form Type, Form Name, Date Created and Project don't necessarily give you all the information to enable you to identify what that form relates to. For example you might have many 'Permits' raised on 05/03/19 within Project XYZ. As a result the Form Title question within the form often gives the additional unique information to make that form identifiable.

When using a tablet the Form Title is displayed (where available) when looking at a list of forms, and its available as a column when viewing Forms on FV web. Therefore it would be useful if the distribution feature which emails Form Reports (pdfs) adds the Form Title (where available) in the File Name of the pdf and/or in the body or title of the email.

This would make it easier to understand exactly what a form relates to when it's received via email (without having to open it first), it would ensure that the document name contains the key information if it's automatically uploaded to a Document Storage system and would mean you could search through your email inbox for a specific Form Title.

There are a number of requests all asking for similar things over the past three years. Glad to see the status has changed to 'In Review' and really hope it does go through as for us, this is really the only form of integration between FV and VFP that we are using currently.

I've been asking for this for over a year now. At the last conference in London we were told this was going to happen but still nothing. We too spend a huge amount of time renaming documents.