SHAREPOINT MANAGED PATHS EXPLAINED

UI Customization Recommendation:

    Don’t alter SharePoint master pages and basic structure of aspx pages
    Don’t modify default CSS file but user can attach new custom CSS and make changes accordingly
    Users can create html pages as special landing pages. Example for special drives
    Modification can perform at CSS file, not at source code
    Users can change design Theme, Color, Font style, Background etc.


Other SharePoint Development customization Recommendation:

    Code Customization shall be done using Sandbox solutions
    Platform Don’t prefer to have Business Data Connection based solutions, however support will be provided on need basis
    Performance Point solutions are not supported
    Infopath forms can be used but KM team support will not be available for Customization and maintenance/migrations
    Default form size will not be changed
    List and Libraries shall not have more than 5000 records in single view. Alternatively, create logical folders in such a way that they don’t have more than 5000 records or split records int multiple Libraries/Lists
    A Typical page shall not have more than 5 connected web parts (SharePoint hard limit is 20 web parts) for example: List views, content editor, chart parts, picture gallery web parts, etc
    List shall not have more than 8 Lookup columns including people fields


Access management Recommendations:

    Permission are not broken beyond web level in any given solutions/pages. Preferrably use DLs for group permissions
    Document Level permissions:
        New group and subsite shall be created if only few users needs to have access to certain documents for a specific project. This group access enabled permission to those users in subsites and required documents can be uploaded to this subsite.


SharePoint 2013 Apps Recommendations:

    Users are encouraged to create SharePoint 2013 Apps. Such apps shall be of Provider Hosted Apps type or SharePoint Hosted Apps. Users are required to develop and test these on their development environment. KM team will facilitate UAT environment for integration testing. KM team will push apps to productions.
    Povider hosted Apps have accompanying website hosted by App provider. Team developing them will need to host such websites themselves and will be responsible for Infosec clearance for these sites.
    Third party apps can be considered to be deployed to platform provided the requesting team has Infosec clearance on such apps and appropriate licensing controls have been put in place.

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Excel Service SharePoint

Image
This article explains about Excel related issue in our SharePoint 2013 Environment. Whenever user tries to open excel files uploaded in document library, it launches browser to open the file and then displays below error- " We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Also see below screenshot- As part of issue analysis, following checks were performed- 1.) Check if Excel Services is running. ( This was running in our case. ) Open Central Administration -> System Settings -> Manage Services on Server -> Excel Calculation Service -> Started 2.) Check if Excel Service Application is associated to Web Application in question. ( This was configured in our case. ) Open Central Administration -> Application Management -> Manage Web Applications -> Select Web Application -> Select Configure Service Associations 3.) Check if Trusted File Location is configured for Excel Service...
Continue Read

Deployment error "The web.config is invalid on this IIS Web Site"

I've developed a webpart that deploys and works properly in my DEV environment. When I attempt to deploy to PROD I get the following error: SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER1 : http://acme.com/ : SharePoint - 23994 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\23994\web.config. None of these virtual directories exist. Any ideas how to resolve? Solution : In Central Administration-> Operation-> Services on Server, please stop the Windows SharePoint Services Web Application service , SharePoint will remove the sites in IIS. And then start the Windows SharePoint Services Web Application service agai...
Continue Read