| There is a thin line between design and development, and as we move into a new decade, this line is becoming extremely blurry. Is it enough to draw beautiful mock ups in Photoshop? Maybe 5 years ago. These days, the average internet user requires more. All beauty, with no substance, gets boring after a while. 2011 is not about beauty, it’s about function. The trends for this new year and emerging decade are responsive design, constant connection and virtual reality.
How will you stay relevant as a designer in 2011? The ultimate goal of a designer is not to dazzle but to entangle. Best practices evolve and change over time, technology we use, client needs, and user’s needs change too. Any designer can get ‘oohs’ and ‘ahhs’ that are easily forgotten. The supreme designer is able to create an environment which charms and captivates the user to the point where he does not want to find the ‘Back’ button. Several elements come together to forge such a wonderland: harmonious color scheme, intuitive design, easily accessible information and fast response. Additionally, one can never under-estimate the power of simplicity. Of course, this has always been the case, but in 2011, you are no longer at the forgiving discretion of the desktop, or even laptop, computer. Now, your design must contend with smart phones, iPads, netbooks, tablets and the like. What designers and developers do is complex ball juggling, so it makes sense that we are reticent to accept the hypervelocity of technology change. Are you ready? We are because not everyone gets to sketch, brainstorm ideas, and play with colours all day.
1. More CSS3 + HTML5
What a gratifying sigh of relief! CSS3 and HTML5 have been on the distant horizon of web design for the past couple of years, but now, in 2011, we see an explosion of it.
2. Simple Color Schemes
Simplicity. There’s nothing quite as impacting as an honest message on a quiet backdrop.
3. Mobile Ready
This means your web design must be responsive to multiple viewports,
4. Parallax Scrolling
It’s not just for old school video games. The hot web design trend for 2011 is creating a sense of depth.
5. Designing for Touch Screens, Not Mice
How much of your design is mouse-oriented? As designers, we worship mice. Our links light up when the mouse hovers over. However, there’s no hovering in touchscreen. How will your design indicate links to your visitors? What about drop-down menus?
6. Depth Perception in Web Design
Depth perception is about creating dimension in your web design, so that parts of your site looks nearer than others. It conjures a faux 3D effect when done masterfully.
7. Large Photographic Backgrounds
Large scale backdrops will surge in 2011. Large photos are an instant way to grab your audience. The background photo must be content-appropriate.
8. Adventurous Domain Names & Integration
Although not in the strictest sense a web design issue, look forward to seeing more creative domain names.
9. QR: Quick Response
If you have noticed those square barcodes popping on business cards, magazines or elsewhere, you may already know that they are a hot trend for 2011. How exactly does it translate into web design? Amazingly well, in fact.
10. Thumbnail Design
The ever-enterprising folks at Google have introduced the average user to thumbnail browsing. Gone are the days of clicking through to see the content of a website.
11. Constant Connection/Life Stream
Expect to see more intimacy through the form of life streaming. Personal blogs and portfolios in 2011 will prominently feature live Twitter feeds. In fact, expect to see a dedicated life stream for all of one’s online activity.
Louise Dunn - Creative Team Lead, Creative SharePoint |
| Running a large SharePoint farm? Multiple site collections? Need to create your global navigation to span across all site collections?
With PowerShell you can script the creation of your navigation to add / modify / and delete nodes. If you’re running multiple site collections you can loop through each site collection within a web application to update the navigation. In the example below we’ll create 1 standard top navigation node, and another node with 1 dropdown element.
//Name of the web application
//Loop through each site collection within the web application
foreach ($SPSite in $webapp.sites)
{
//Open the web
$OpenWeb = $SpSite.OpenWeb()
//Select the top navigation bar
$TP = $OpenWeb.Navigation.TopNavigationBar
//Create a new object, this will be your navigation element
$Node = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode "Link 1", "http://link1",1
//Add the navigation element to the top navigation bar, this will be added as the last item
$TP.AddAsLast($node)
//Create a new navigation element with 1 dropdown node
$Node = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode "Resource", "http://resource",1
$Node1 = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode "Dropdown", "http://Dropdown",1
//Add the ‘Resources’ node to the top navigation
$TP.AddAsLast($Node)
//Add the ‘Dropdown’ node to the Resources tab
$Node.Children.AddAsLast($Node1)
//Cleanup
$SPSite.Dispose()
$OpenWeb.Dispose()
}
David Hendry - Lead Consultant Creative SharePoint |
|
| Where ever you work in today’s business environment you will find yourself governed by office processes. These processes are generally designed for the paper age with no thought of autonomy or optimization even given today’s technology and resources.
The concept of Business Process Management consists of two major suites, an eForms suite and a workflow suite. The eForms suite is used to map and optimize the current paper based forms, integrating digital signatures, web services to automatically retrieve data and act as the interface to the end user. The workflow suite drives the form or forms through the governed business process. The workflow sets whom the form is assigned to, when, how, and what tasks are involved in the process. By using both of these suites the business analyst can truly redesign all business processes to integrate with LOB sources, minimize all manual interaction tasks and offer business reporting on these processes to offer information for CIP and LEAN processes BPR.
Implementing a BPM solution can be a cumbersome task. To make it work for your organization you not only need to invest in the technology but you'll also need to redefine the way your business analysts think about processes; both current and new. Business Process redefinement is the process of deconstructing the current inefficient process, plotting the target and the key achievements of the process and reconstructing it automating whatever tasks can be automated. Once your process is redefined, a full form and workflow can be created from this new process specification
Advantages of upgrading your business processes
- Automation of certain stages in the process
- Full audit trails can be given for business processes
- Automatic escalation can be built in to processes to ensure timely delivery
- Business reporting can be implemented to allow identification of bottlenecks and report on process metrics.
- Automatic authentication of the form creator and approvers can be built in
- Location is not so much of an issue with BPM solutions, when creating or approving processes this can be done in most places as long as you have an Internet connection and a VPN to your companies network
So what’s stopping you?
The stopping point for an organisation could be the initial onset of cost for implementing the software and architecture to have and maintain the BPM solution platform, and yes the costs of implementing a BPM solution and training your team in using it efficiently.
Thoughts of negative ROI run riot with this. Obviously implementing a BPM solution requires a large number of current manual processes and generally a CIP or LEAN team able to drive improvement.
Rest assured with a well implemented BPM system you can make your processes efficient saving your business time and ultimately money!
So, what can i do with SharePoint?
SharePoint as a platform offers a fantastic starting point for implementing a BPM solution. It is the starting platform from which your organisation can implement forms workflow and reporting, all tightly integrated into SharePoint.
Forms - Microsoft InfoPath is a fully functional eForms Suite that integrates with SharePoint via either form library with template set up or a forms service form which uses SharePoint. This Suite has support for PKI and is very flexible in terms of what and how you want to define in your forms.
Workflow - SharePoint offers the platform for implementing two types of workflow. SharePoint Designer Workflows offer a simple GUI approach to creating workflows. The software comes with a number of tasks out of the box and allows creation of basic to advanced workflows in minutes. There are times when a more complex workflow is required, or one that can be easily redeployed to separate environments. In that case SharePoint Visual Studio Workflows offer a programmatic approach to creating workflows, this approach is a more flexible way to creating workflows as you can create your own tasks.
Reporting - The SharePoint platform comes with Performance Point (FREE if you hold a MOSS enterprise licence) PerformancePoint is the Microsoft Business Intelligence solution. Allowing creation of KPI's, gauges, charts and graphs based on your custom data cubes.
Ben Dean - SharePoint Developer, Creative SharePoint |
| There are loads of solutions out there on the Internet for tackling IE6 PNG transparency bugs. Throughout my search, I found these three solutions to be the most effective, and (perhaps just as importantly) easiest to implement.
I was able to use all of these solutions collaboratively to solve the IE6 PNG transparency issues that I was facing.
1) IMG tag transparency issues
Any PNG files used as the src for IMG tags that have transparency in them, will require you to refer to the pngfix.js file. This file, and instructions for its use can be found here.
Basically, add the pngfix.js file to your scripts folder, and reference it as follows (don't forget to modify the src attribute in the script tag) from your master page:
<!--[if IE 6]>
<script defer type="text/javascript" src="/Style Library/McCain/Scripts/pngfix.js"></script>
<![endif]-->
Simple as that.
2) background-image css property transparency issue
If you have any background-image css properties that refer to PNG images with transparency, then you will need the DD_belatedPNG.js file from here , as well as the latest JQuery library from here
This solution is slighly more involved than solution 1, and may even crash your browser if there are multiple overlapping background images (see solution 3 for help with this).
Anyhoo, when it does work, it does the trick nicely, so here is how to use it.
Firstly, acquire DD_belatedPNG.js and jquery.js, and place them both in your scripts folder. Secondly, refer to them both within your master page as follows (don't forget to modify the src attributes in the script tags)
<script type="text/javascript" src="/Style Library/Scripts/jquery.js"></script> <!--[if IE 6]>
<script defer type="text/javascript" src="/Style Library/Scripts/DD_belatedPNG.js"></script>
<![endif]-->
Now, you will need to create a new js file that calls the functionality within DD_belatedPNG.js, and refer to that within your page as well (put the script reference just under the reference to DD_belatedPNG.js above, and all should be good).
This new js script should contain code that resembles the example below
$(document).ready(function()
{
DD_belatedPNG.fix( '#elementId);
DD_belatedPNG.fix( '.css-class' );
}
where #elementId and .css-class are example selectors that will get you the elements that are having the issues with their background-image. You can make as many such calls as you want, but you must make a call for each of the elements that needs addressing.
If this isn't clear, please let me know (james.ellins@creative-sharepoint.com). Failing that, refer to the website for DD_belatedPNG.js here.
3) Give up and use GIF files instead
PNG files produce much smoother transparency effects than GIF files, but GIF files don't seem to encounter the same problems in ie6 that PNG files do. So, if no other solution will do, try this.
For starters, create and link to a separate style sheet just for IE6, and have elements within that style sheet that use GIF images for the background-image property instead of PNG images.
Example code taken from a project of ours is shown below.
This bit is from the master page, referring to an IE6-only style sheet.
<!--[if IE 6]>
<link rel="stylesheet" type="text/css" href="/Style Library/CSS/CSP-IE6.css" />
<![endif]-->
This next bit is from within an IE6-only style sheet. The example shown below refers to GIF images for the background-image properties, whereas in the main stylesheet PNG images were used. This example is for tabbed navigation in SharePoint. Trying to use solution 2 for this particular scenario caused IE6 to crash.
#mcn-SiteBar .mcn-TopNavItem td
{
background-image:url("/Style%20Library/Images/right_btn_corner.gif");
}
table.mcn-TopNavItem
{
background-image:url("/Style%20Library/Images/left_btn_corner.gif");
}
And that's it. Hopefully, armed with these three different approaches, IE6-induced transparency effect misery will be a thing of the past.
Good Luck
James Ellins - Consultant, Creative SharePoint |
| We are a small company with big clients. Many of our clients commission multiple projects ranging from small, single person projects taking less than a week to large, team-based projects lasting months. Clients have supoort issues that need to be dealt with fast and they request quotes for enhancements or new projects which also take time. Work is developed using Visual Studio, tested internally and released for client testing and then deployed to production environments hosted by clients.
As a company we need to be aware of what our capacity is in order to schedule work. The clients we work with require and deserve a dynamic approach to scheduling: our priorities have to be able to change week to week and day to day whilst we still deliver all of the work that we have committed to. We use elements of Scrum where they are appropriate and a more structured approach to allow us to set client expectations.
Our objective is to implement SharePoint 2010, Project Server 2010 and Team Foundation Server 2010 (TFS) in order to manage the work and the development. Our intranet, external website and client extranet will all be hosted on SharePoint 2010. On top of SharePoint 2010 we will have Project Server 2010 to manage the work that needs to be done. The development tasks will be managed using TFS, as will version control, testing and builds.
This is the perfect scenario for our business. There are, however, issues that are standing in our way:
- How do we integrate Project Server 2010 and TFS 2010 so that management of projects are governed through Project server 2010 and development and testing tasks are managed through TFS 2010?
- How do we associate multiple projects, quote requests and support issues in Project Server 2010 and TFS 2010 with clients?
- How can we expose selected information in both Project Server 2010 and TFS 2010 to clients via an extranet for each client?
These are the initial objectives and issues that we are facing. We have the people with the capable skills and they have the hunger to update their skils and learn about all of these technologies. We also have the thirst, as a company, to deliver this solution for three reasons:
- Our lives will be easier
- Our clients will be happier
- We will be able to work more efficiently
We will be pursuing these objectives and will, no doubt, encounter many more challenges. Bring 'em on - we'll get there.
Alan Eardley - Project Manager, Creative SharePoint |
| It's about at this time in a product lifecycle that organisations look at the options available when upgrading and migration to new versions of their software applications and platforms. Many IT departments will be looking at upgrading their SharePoint environment from either 2003 or 2007 to SharePoint 2010.
The important bit to note is that there’s no upgrade route from SharePoint 2003 to 2010! The only way to upgrade would be to upgrade the farm to 2007, then to 2010. Alternatively a content migration exercise should be assessed, 3rd party tools are available to assist with the migration of content.
To upgrade your environment the following is required:
• SQL 2005 with SP3 supported but not recommended, SQL 2008 is recommended
• SharePoint 2007 SP2 with October Cumulative update
• 64 bit hardware
• Windows Server 2008 with SP2 / R2
• Minimum 8GB RAM, development environment will run on less RAM
• SharePoint WCF hotfix required, this isn’t installed by the pre-requisites tool (http://support.microsoft.com/kb/976462)
There are 2 upgrade methods available, and 2 hybrid options:
In place upgrade:
• Uses existing hardware
• The configuration and content databases are upgraded
• Server offline during upgrade
• Farm wide settings preserved
• Customisations should be available after upgrade
• Recommended for small or non-production environments
Database attach upgrade:
• New hardware (farm) required
• Upgrade multiple databases at a time
• Server farm settings not kept (Audiences, InfoPath configuration etc...)
• Customisations must be transferred / redeployed
• Opportunity to consolidate multiple farms into one
• Recommended if farm configurations are minimal
Hybrid 1:
• Read only databases
• Use database attach upgrade to preserve existing farm settings
• Existing farm is put in read only mode
• Create a new farm and attach all content databases
• Recommended for small / medium / with minimal customisations
Hybrid 2:
• Detach content databases from the farm
• Use in-place upgrade to preserve farm settings
• Central Admin and SSP databases upgraded
• Once upgrade is complete, reattach DBs and upgrade content databases
• Farm level settings are maintained
• Content databases could be upgraded in a temporary farm, then ported over
• Recommended for medium / large farms
Avoiding Upgrade Issues
• Run the pre-upgrade check
• Upgraded to SharePoint 2010 won’t fix a broken farm
• Coalesce the farm, make sure no users are using the farm while the upgrade takes place
• Perform a trial upgrade on a test farm first, important!
• Use STSADM / Powershell scripts to attach database
• Remember to backup all content, and ensure backups are working!
Technet supporting information:
http://technet.microsoft.com/en-us/sharepoint/ee517214.aspx
Upgrade Planning:
http://www.microsoft.com/downloads/details.aspx?FamilyID=e8b66eb3-27c7-4a39-a2e1-3e7d18b12ee1&displaylang=en
David Hendry - Lead Consultant Creative SharePoint
|
| The biggest advantages to moving from a third party RIA framework to Silverlight is that it is a fully supported framework. It is a technology Microsoft are pushing at full force to achieve market supremacy and that it has full integration with .NET
Silverlight is based on the .NET framework meaning that integration with .NET applications is a simple matter. With a web service on the backend to feed the Silverlight control, extraordinary feats of usability and functionality can be developed to meet any and all business requirements.
For the people afraid of the user base of Silverlight not being high enough to implement a solution in it, firstly the technology is rapidly growing every week, the number of users adopting the technology is also greatly on the rise. Silverlight offers a very fluid “graceful degredation” to another technology of the developer or companies choice for those who don’t have the Silverlight plugin installed.
Silverlight is aimed at two groups for development, firstly the creative teams add the animation, graphics and effects using “Microsoft Blend” as a creative tool and the backend developers create the functionality and integrations using “Visual Studio”, Microsoft have created blend with the idea that the Silverlight solutions can be loaded in blend or VS independently and can share the same solutions so both developers and creatives can work on the same solutions.
SharePoint and Silverlight.
With the release of the new versions of SharePoint 2010 and Silverlight 4, it is now possible in Silverlight to display and manipulate SharePoint information and functionality without relying on external connections to webservices so much. New advances have been made to Silverlight with the inclusion of a “Silverlight Client OM assembly” this effectively allows developers to directly integrate their applications into SharePoint.
SharePoint development in the years to come will be very Silverlight oriented and solutions based on SP2010 will increasingly provide Silverlight interfaces as users want the slickest integration they can get and gold partners are willing to provide it!
Benjamin Dean - Developer - Creative SharePoint
|
| Since working for CSP, lots of my projects have included branding SharePoint solutions. Branding SharePoint primarily consists of Master Pages, Page Layouts and the web parts. However the purpose of this particular blog article is to look more closely at Page Layouts.
So what are page layouts? I would describe a page layout as something that sits within a SharePoint web part page, which makes its appearance slightly different. For example lots of pages have similar layouts. As opposed to creating a new page from scratch, A Master Page coupled with a Page Layout will provide the building blocks required to populate a stylised page with relative ease. Within SharePoint you can build as many layouts as you wish, but best practice would dictate that you promote reusability by making layouts flexible and thus keeping layouts to a minimum. For example as opposed to making one layout to serve one purpose, make a layout to serve two or three purposes.
What are the challenges with creating page layouts? I’ve generally found as long as the guidelines are adhered too, for example layouts are published, approved and tested, there are no major issues. My biggest personal challenge was trying to manipulate something displayed within the Master Page depending upon which page you’re on, (this could only be controlled by the Page Layout). However this was at a point when I wasn’t familiar with the good old asp content place holder tags. I soon realised how easy it actually was! Are there any major differences between MOSS and 2010? From personal experience I haven’t found any major differences between page layouts on MOSS and 2010, but I would look out for sporadic issues such as check boxes randomly appearing in IE6!
So in summary, page layouts promote reusability, flexibility and generally facilitate the building blocks required to peace pages together.
Adam Dale - Consultant - Creative SharePoint
|
| It was the start of my epic voyage into what was supposed to be the most exciting thing to happen to collaboration “ever” and “a new way for teams to work together”. It only seems like yesterday when I first took the Team Services and SharePoint Portal Server 2001 CD from the brown jiffy bag and put it into my brand new Windows Server 2000 Drive.
WOW, how things have changed! Not just in the way we use SharePoint as an end user, but also how we, as a SharePoint specialist, take for granted features such as workflow and content management.
As a product, SharePoint has become enormous from where it was nearly 10 years ago. It really became usable in 2003 when suddenly you could build an Intranet and people could search for things and get “some” meaningful results. The day I installed the BETA of MOSS 2007 was when I realised that persevering with this technology had all been worth it.
Suddenly it sold itself on features alone and it started to become a hot topic; even my family members started to use it at their work places. No one could have predetermined the success that this version has bought about. Now with the latest version of SharePoint being released in May (SharePoint 2010) we are in for some exciting times ahead.
So, “Why do we all use SharePoint”? Does it help us all become more organised? Does it stop us from saving files directly on to our Desktops? Will it prevent IT departments from buying more and more storage?
Perhaps, I think the question you ought to ask is “Where next for SharePoint”?
Oli Stickley - MD Creative SharePoint
|
View in Web Browser /_layouts/VisioWebAccess/VisioWebAccess.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType vdw 255 Manage Subscriptions /_layouts/images/ReportServer/Manage_Subscription.gif /_layouts/ReportServer/ManageSubscriptions.aspx?list={ListId}&ID={ItemId} 0x80 0x0 FileType rdl 350 Manage Data Sources /_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rdl 351 Manage Shared Datasets /_layouts/ReportServer/DatasetList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rdl 352 Manage Parameters /_layouts/ReportServer/ParameterList.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 353 Manage Processing Options /_layouts/ReportServer/ReportExecution.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 354 Manage Cache Refresh Plans /_layouts/ReportServer/CacheRefreshPlanList.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 355 View Report History /_layouts/ReportServer/ReportHistory.aspx?list={ListId}&ID={ItemId} 0x0 0x40 FileType rdl 356 View Dependent Items /_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsds 350 Edit Data Source Definition /_layouts/ReportServer/SharedDataSource.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsds 351 View Dependent Items /_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 350 Manage Clickthrough Reports /_layouts/ReportServer/ModelClickThrough.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 352 Manage Model Item Security /_layouts/ReportServer/ModelItemSecurity.aspx?list={ListId}&ID={ItemId} 0x0 0x2000000 FileType smdl 353 Regenerate Model /_layouts/ReportServer/GenerateModel.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 354 Manage Data Sources /_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType smdl 351 Load in Report Builder /_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderModelContext&list={ListId}&ID={ItemId} 0x0 0x2 FileType smdl 250 Edit in Report Builder /_layouts/images/ReportServer/EditReport.gif /_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderReportContext&list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 250 Edit in Report Builder /_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderDatasetContext&list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 250 Manage Caching Options /_layouts/ReportServer/DatasetCachingOptions.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 350 Manage Cache Refresh Plans /_layouts/ReportServer/CacheRefreshPlanList.aspx?list={ListId}&ID={ItemId}&IsDataset=true 0x0 0x4 FileType rsd 351 Manage Data Sources /_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rsd 352 View Dependent Items /_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 353 Compliance Details javascript:commonShowModalDialog('{SiteUrl}/_layouts/itemexpiration.aspx?ID={ItemId}&List={ListId}', 'center:1;dialogHeight:500px;dialogWidth:500px;resizable:yes;status:no;location:no;menubar:no;help:no', function GotoPageAfterClose(pageid){if(pageid == 'hold') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/hold.aspx?ID={ItemId}&List={ListId}'); return false;} if(pageid == 'audit') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/Reporting.aspx?Category=Auditing&backtype=item&ID={ItemId}&List={ListId}'); return false;} if(pageid == 'config') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/expirationconfig.aspx?ID={ItemId}&List={ListId}'); return false;}}, null); return false; 0x0 0x1 ContentType 0x01 898 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 FileType xsn 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.2 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.3 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.4 255 View in Browser /_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsx 255 View in Browser /_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsm 255 View in Browser /_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsb 255 |
|
|
View in Web Browser /_layouts/VisioWebAccess/VisioWebAccess.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType vdw 255 Manage Subscriptions /_layouts/images/ReportServer/Manage_Subscription.gif /_layouts/ReportServer/ManageSubscriptions.aspx?list={ListId}&ID={ItemId} 0x80 0x0 FileType rdl 350 Manage Data Sources /_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rdl 351 Manage Shared Datasets /_layouts/ReportServer/DatasetList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rdl 352 Manage Parameters /_layouts/ReportServer/ParameterList.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 353 Manage Processing Options /_layouts/ReportServer/ReportExecution.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 354 Manage Cache Refresh Plans /_layouts/ReportServer/CacheRefreshPlanList.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 355 View Report History /_layouts/ReportServer/ReportHistory.aspx?list={ListId}&ID={ItemId} 0x0 0x40 FileType rdl 356 View Dependent Items /_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsds 350 Edit Data Source Definition /_layouts/ReportServer/SharedDataSource.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsds 351 View Dependent Items /_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 350 Manage Clickthrough Reports /_layouts/ReportServer/ModelClickThrough.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 352 Manage Model Item Security /_layouts/ReportServer/ModelItemSecurity.aspx?list={ListId}&ID={ItemId} 0x0 0x2000000 FileType smdl 353 Regenerate Model /_layouts/ReportServer/GenerateModel.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType smdl 354 Manage Data Sources /_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType smdl 351 Load in Report Builder /_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderModelContext&list={ListId}&ID={ItemId} 0x0 0x2 FileType smdl 250 Edit in Report Builder /_layouts/images/ReportServer/EditReport.gif /_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderReportContext&list={ListId}&ID={ItemId} 0x0 0x4 FileType rdl 250 Edit in Report Builder /_layouts/ReportServer/RSAction.aspx?RSAction=ReportBuilderDatasetContext&list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 250 Manage Caching Options /_layouts/ReportServer/DatasetCachingOptions.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 350 Manage Cache Refresh Plans /_layouts/ReportServer/CacheRefreshPlanList.aspx?list={ListId}&ID={ItemId}&IsDataset=true 0x0 0x4 FileType rsd 351 Manage Data Sources /_layouts/ReportServer/DataSourceList.aspx?list={ListId}&ID={ItemId} 0x0 0x20 FileType rsd 352 View Dependent Items /_layouts/ReportServer/DependentItems.aspx?list={ListId}&ID={ItemId} 0x0 0x4 FileType rsd 353 Compliance Details javascript:commonShowModalDialog('{SiteUrl}/_layouts/itemexpiration.aspx?ID={ItemId}&List={ListId}', 'center:1;dialogHeight:500px;dialogWidth:500px;resizable:yes;status:no;location:no;menubar:no;help:no', function GotoPageAfterClose(pageid){if(pageid == 'hold') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/hold.aspx?ID={ItemId}&List={ListId}'); return false;} if(pageid == 'audit') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/Reporting.aspx?Category=Auditing&backtype=item&ID={ItemId}&List={ListId}'); return false;} if(pageid == 'config') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/expirationconfig.aspx?ID={ItemId}&List={ListId}'); return false;}}, null); return false; 0x0 0x1 ContentType 0x01 898 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 FileType xsn 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.2 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.3 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.4 255 View in Browser /_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsx 255 View in Browser /_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsm 255 View in Browser /_layouts/xlviewer.aspx?id={ItemUrl}&DefaultItemOpen=1 0x0 0x1 FileType xlsb 255 |
|
|