In today’s cloud-based world, Microsoft is moving its software models online as fast as it can.
But, what does this shift mean for SharePoint?
The truth is, it has a profound impact, as customization options historically available are decreased due to the nature of hosted environments.
To meet the market need for customization, Microsoft has introduced a way to allow customers to build their own solutions in SharePoint called the SharePoint App Model, which contains no server side code.
Even with the addition of this model, workflow in SharePoint 2013 remains limited in many scenarios. Removing server side code required the introduction of a new workflow engine, and with that comes additional challenges. Organizations need sophisticated and reliable workflow apps with functionality like:
- Rich and flexible forms that support mobile devices
- Flexible workflow outcomes other than simple approve/reject
- Easy integration with SharePoint data on other sites and farms
- Easy integration with line-of-business (LOB) data sources such as SAP and Oracle
- More advanced error reporting and recovery
Unfortunately, SharePoint does not offer this functionality out-of-the-box, which forces organizations to spend time and money on customization, but without server side code, the level of customization is limited.
Need to customize your SharePoint deployment?
This paper details the most important challenges to consider when building SharePoint workflow apps. It also explains K2 Appit, a solution that enables organizations to create reliable SharePoint workflow applications without the challenges of customization.