BaseCamp – February 2014 – Post-mortem Strategy for InfoPath

BaseCamp February 2014

 

DEVELOPING A NEW FORMS STRATEGY

We are sure that the recent announcement about InfoPath’s retirement is pushing you and your organization to evaluate your investment into forms technology moving forward.
Moving forward, it is important that your investment in Forms and Workflow be flexible, and adaptable not only to technology but also the needs of the business.
A few recurring themes that every Forms and Workflow Strategy need to address are:
  • Are your existing forms mobile enabled?
  • What processes are your forms supporting?
  • Do you require offline access to your forms?
Additionally, our partner Nintex, has provided four key steps to build your plan.

 

STEP 1. Take an Inventory
Inventory your forms-based applications. Identify forms that may be using complex scripting or Visual Studio add-ins that may be hard to manage going forward.

 

STEP 2. Talk to Business Users about How they Use Forms
It’s likely that you have legacy forms that are not meeting the needs of the users.   Talk to your end users about the need for intuitive, mobile friendly forms.  Look at change requests and support tickets that users have submitted.  Add this information to the inventory spreadsheet.

 

STEP 3. Identify Candidate Forms
Classify forms into the following categories based on business needs:
  1. Forms that need to be replaced immediately
  2. Forms that need to be replace within the year
  3. Forms that need not be touched for the next 2 years

 

STEP 4. Re-think Forms and Workflow
While you are planning to update your forms, it is also the perfect time to re-think your approach to forms and workflow. Modern forms cannot exist in isolation. Businesses often need them to integrate with workflows and business users and IT professionals are looking for intuitive, mobile friendly, and cloud ready solutions.
To learn more about how Summit 7 Systems has worked towards addressing the needs for lightweight forms solutions check out our Forms7 codeplex solution: http://forms7.codeplex.com/

MEET SUMMIT 7 SYSTEMS AT BOOTH 439 DURING SHAREPOINT CONFERENCE 2014!

The SharePoint Conference is right around the corner and we hope to see you during the show. Between sessions visit the Summit 7 Systems Booth (439) to learn more about Migrating to Office 365, Strategies for InfoPath replacement, and much more.
Solutions Architect, Mark Rackley will deliver a fun and fast paced presentation that will help you quickly migrate your Cloud based Applications.
Don’t fear SharePoint…Fear leads to anger, anger leads to hate, hate…to suffering….We at Summit 7 can help prevent unwanted SharePoint Suffering. Together we can be a positive FORCE.

WHAT IS A SQL ALIAS AND WHY USE ONE?

A SQL alias is an alternative name given to a SQL server that is more familiar to the user. It is like a nickname for a person, except it is for a server. Sometimes server names can be complex and hard to remember, this is where an alias would come in handy. Instead of having “Prod _SRV_SP_SQL_1” as the server name, you can use “SQL1” or any variation of that for simplification. Creating an alias for a SQL server is recommended when building a new production SharePoint server farm for many reasons.

SHAREPOINT 2013 ACCIDENTAL ACTIVE DIRECTORY ACCOUNT CREATION MODE (AADACM)

Have you ever had a case of AADACM? Well I have. It all started a few weeks ago when I began an installation of SharePoint 2013 utilizing PowerShell. I decided to use PowerShell to install SharePoint to help me to customize the database names on the SQL servers, and go through the installation process quickly and efficiently. When SharePoint is installed through the application, it creates databases that contain a long GUID at the end of them.
 

 

March 3
SharePoint Conference 2014
Mark Rackley
April 13
DevIntersection
Mark Rackley
April 22
SPTechCon
Mark Rackley & Ben Curry
June 23
Cloud DevCon
Mark Rackley, Ben Curry & Jason Miller
Full Event List and Details