![]() ![]() My hope is to create a series of videos detailing the various features. The video only scratches the surface of what’s possible though. I also created following YouTube video to help you guys get started as quickly and easily as possible. I recommend going through some of the examples before you create your first form from scratch, and even then when you create your first form from scratch grab the JavaScript for the minimal form example to get started. Add a Content Editor Web Part to any page in SharePoint and link it to your form.Upload your form to a document library in SharePoint.Create your form using HTML, CSS, and JavaScript and connect your form to StratusForms using the Initialize function.Create a field in this list that is a PLAIN TEXT multiline field called “StratusFormsData”.Download the source code from and copy it into your Site Assets library (you can use any document library, but the examples assume you put everything in Site Assets). ![]() The basic steps to get started with StratusForms are as follows: With StratusForms we’ve been able to migrate clients off of old legacy systems, meet stringent form design requirements, handle strict printing needs, create mobile friendly forms with multilingual support and do it all in less time than it would take building these forms from scratch. Just this week I released version 1.5 and it hit me, I’ve never actually blogged about StratusForms. Over the years, I’ve started using StratusForms more and more for projects and making incremental enhancements to it as I go. Literally, the limits of creating forms in SharePoint is your limits as a client side developer. They can have complicated business logic and be mobile friendly. You can now create extremely complicated (or very simple) forms that can look exactly how you want them to look. Using this concept, I created StratusForms. Doing this really opened the world of form creation. I like this concept, so what I did with StratusForms is store all your form data in one field in a SharePoint list as a JSON object. This is much easier to maintain in SharePoint and allows you to create different forms on the same list while only promoting common fields. I really like this because you can create complex forms with dozens (hundreds?) of fields but only promote those field to a SharePoint list that you need in your list views. InfoPath stores your form and data in XML and you can promote your fields in your form to a field in a SharePoint list if you want to. It’s free, business users can create forms, and you can do some cool stuff with it… but… it’s… InfoPath…Īnyway, I decided to take the good parts about InfoPath from a technology standpoint and move them into the Client Side Development world. The client didn’t have a budget to purchase a forms solution and they didn’t want to use InfoPath (which is fine, because I really loathe InfoPath). I created StratusForms because I had a client that wanted to migrate off Lotus Notes and into SharePoint, but all their migrated applications had to look the same in SharePoint so that it would be easier on the users. The goal of StratusForms was to remove limitations of form creation in SharePoint and to get developers off of InfoPath. StratusForms allows you to create forms in SharePoint using HTML, JavaScript, and CSS and works for SharePoint 2007, 2010, 2013, 2016, and Office 365. To help address this need, I created a forms solution for SharePoint several years ago called StratusForms. In all my years of working in SharePoint, there has been one consistent need from users: Forms… Better looking forms… more powerful forms… mobile friendly forms… There has ALWAYS been a need for a better forms experience in SharePoint. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |