1 / 5

Design Option #1 – Use OOB Features

Design Option #1 – Use OOB Features. SharePoint OOB features InfoPath form for UI Lists to store data SharePoint WF Pros: Cheaper (since it is OOB) Cons: OOB features limit what can be done WF cannot be customized UI limitations (no metro UI) Etc.

eman
Télécharger la présentation

Design Option #1 – Use OOB Features

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Design Option #1 – Use OOB Features • SharePoint OOB features • InfoPath form for UI • Lists to store data • SharePoint WF • Pros: • Cheaper (since it is OOB) • Cons: • OOB features limit what can be done • WF cannot be customized • UI limitations (no metro UI) • Etc.

  2. Design Option #2 – Custom Development On SharePoint • SharePoint Custom Web Pages • Custom UI • Lists to store data • Custom WF • Pros: • Integrated in SharePoint • Deployment/maintenance tools available OOB • Cons: • UI development requires lot of Java Scripting • Will need custom web parts, java scripting etc. for supporting some of the UI requirements (expensive) • Server side code not supported • Getting data from external sources is harder (BCS to some extent) • Custom workflow development is expensive • Workflow limited to SharePoint (can’t use full windows WF stack)

  3. Design Option #3 – App for SharePoint 2013 • Develop Custom Web App • Custom UI • SharePoint Lists to store data (or any other backend) • Custom WF • Pros: • It will be a regular web app integrated with SharePoint • Full windows web app development stack can be utilized • App deployed/maintained outside SharePoint • Cons: • Extra resources needed for app hosting (ideally)

  4. We chose #3 because…. • Custom UI development easier • Team already had good web developers • No UI limitation • Can use HTML5 or any other latest UI technology • Integrating with external sources is easy • Given all of windows web app dev stack is available • Custom code for a specific data source can be written and called by the app • App is hosted separately • No resource sharing with SharePoint server • Reduces SharePoint support cost

More Related