Qdabra FormsViewer

Re: FormsViewer to replace our InfoPath 2007

Wheels — Thu, 08 Jun 2017 19:31:35 GMT

Hi Patrick. When will the beta version of FormsViewer be available, and how do get download it? My company is looking for a replacement for InfoPath, and this was one of my recommendations. WHEELS

Re: FormsViewer to replace our InfoPath 2007

Wheels — Tue, 30 May 2017 22:15:11 GMT

Good afternoon Patrick. I would definitely be interested in being a beta tester for the new "Designer" features we are adding to FormsViewer. WHEELS

Re: FormsViewer to replace our InfoPath 2007

Patrick Halstead — Tue, 30 May 2017 20:51:46 GMT

Hi again,

I hope all is well.

Are you interested in being a beta tester for the new "Designer" features we are adding to FormsViewer?

Best,

Re: FormsViewer to replace our InfoPath 2007

Wheels — Wed, 07 Dec 2016 12:22:01 GMT

Thank you for the information Patrick, and great job on the webinars. WHEELS

Re: FormsViewer to replace our InfoPath 2007

Patrick Halstead — Wed, 07 Dec 2016 05:25:39 GMT

Hi Again,

We are starting development of the FormsViewer Designer in Q1 and hope to have a prototype integrated into the FormsViewer app by end of Q2. It should become available to you without any installation if you are using FormsViewer online (O365), Our major focus for the first release will be the *edit* scenario. If you have an XSN, in addition to supporting view layout changes, FormsViewer Designer will support editing and adding fields, rules, and data connections. The initial beta release will probably not support creation of new forms from scratch. I.e., you'll have to start from an existing one.

Publishing to FormsViewer is much simpler than publishing to SharePoint - just save the XSN and drag and drop to your FormsViewer page.

FormsViewer Designer has been on our "back burner" up until now because Microsoft extended support for InfoPath Designer 2013 through the end of 2025, but we plan to start development soon.

Please let me know if you'd like to be on our Q1 early adopters list.

Thank you for your interest!

Patrick

Re: FormsViewer to replace our InfoPath 2007

Wheels — Tue, 06 Dec 2016 15:58:30 GMT

It is my understanding that IT does not want to install the InfoPath 2013 when we upgrade to O365, and would not want to keep it on a few select machines for development.

Re: FormsViewer to replace our InfoPath 2007

Hilary Stoupa — Tue, 06 Dec 2016 15:50:48 GMT

I don't believe we have a release date yet. Is it not possible to keep InfoPath on a machine or two for form designers to use for making any changes?

Re: FormsViewer to replace our InfoPath 2007

Wheels — Tue, 06 Dec 2016 15:47:00 GMT

Hi Hilary. We currently have Office 2007, but will be upgrading to O365/O2016 next year. What we are trying to figure out is how to do form design (new or edit existing InfoPath forms) with FormsViewer and after removing InfoPath. It is my understanding that Qdabra is currently developing a browser-based designer to replace InfoPath, but no word of when it will be released.

Re: FormsViewer to replace our InfoPath 2007

Hilary Stoupa — Tue, 06 Dec 2016 15:35:24 GMT

To your first question, all your forms will end up in the browser - so, the XSN will need to be published to SharePoint and the XML will be stored in SharePoint for your currently LAN based forms. And yes, InfoPath Designer is still going to be needed for form design. What version of Office do your users currently have? InfoPath can be removed if desired - you just need to go through Office configuration and remove it, unless you are using Office 2016 and still have InfoPath installed separately from Office 2013 - then you should be able to just remove it from Programs.

Re: FormsViewer to replace our InfoPath 2007

Wheels — Tue, 06 Dec 2016 14:53:17 GMT

Hi Patrick. I am currently watching the You Tube videos, and on the one you are hosting (Future Proof Your Forms Investment). In the last video, Patrick mentioned that Qdabra is creating a browser-based designer to replace InfoPath, but in the interim folks will need to use InfoPath as the form editor. How can InfoPath be removed from the user's client machines? WHEELS

Re: FormsViewer to replace our InfoPath 2007

Wheels — Tue, 06 Dec 2016 12:35:37 GMT

Thank you for the information Patrick. Can you help me better understand the SharePoint integration piece? Some of our InfoPath forms have been published to a SharePoint library, but the majority are published and accessed on the LAN. Are you stating that all of the forms with need to be published to SharePoint, and then configured to open in FormsViewer? WHEELS

Re: FormsViewer to replace our InfoPath 2007

Patrick Halstead — Tue, 06 Dec 2016 07:27:38 GMT

Hi WHEELS,

Thank you for your interest in FormsViewer.

You don't have to do anything with the XSN. FormsViewer allows you to use the InfoPath form template "as is" without changes. It does require the browser and SharePoint 2013/ 2016 or SharePoint Online / Office 365.

Once you move your forms to a SharePoint library and configure it to open the forms in FormsViewer, there is no need to have InfoPath on the user's client machine.

I hope that answered your question.

Please email me if you'd like a short chat later this week.

Thanks!

FormsViewer to replace our InfoPath 2007

Wheels — Mon, 05 Dec 2016 20:53:26 GMT

Good afternoon.

My company is looking into alternatives to InfoPath 2007, and we have 100s of forms that will require conversion. I came across FormsViewer, and I was very impressed with the functionality which I have read about and saw demoed. My question is, does FormsViewer have a wizard to import InfoPath forms (.xsn), and can these forms being converted if InfoPath was removed from a user's machine?

Thank you,

WHEELS