The records manager and the SharePoint administrator

When it comes to records managers and SharePoint administrators, the question is how the responsibilities should be divided. On the one hand, the records managers know the processes, the document flows and the laws and regulations, and they have had thorough training in everything that has to do with records management. On the other hand, records management is actually implemented with SharePoint, where the business is inclined to skip the records managers and do direct business with SharePoint administrators. The records managers also suffer from their image here: only a few decades ago they were primarily the ‘custodians’.

It is not keeping but sharing that is hip nowadays. Moreover, demands in terms of daily application, customers and legislation (such as  the Dutch act on openness of government, WOB) also require that the information should be easy to find and quickly reproducible. Fortunately, many records managers have long since kept up with developments, partly based on the spread of the records continuum philosophy. They recognized the importance of information technology and the changes involved for their area of work. In this so-called post-custodian discussion, it is argued that the professional domain of the records manager is shifting from the actual storage and physical processing of archives towards understanding and managing patterns of data flows and offering context and structure, so that the archives are useful.

What does all this say about the role division between records managers and the SharePoint administrator? First of all, records managers are records management professionals in terms of content. They are used to adopting a proactive approach along with the business in terms of the reflection of processes in documents, liability and laws and regulations. This knowledge is required at all levels of records management and should remain with them. On the other hand, there are social and technological developments with which the SharePoint administrator is more familiar. Microsoft introduced the 'Work like a Network' idea, for example, which ties in with Enterprise Social/Enterprise 2.0. It has an impact on all areas of information management and therefore on records management as well. Based on this, the records manager would have to be responsible for the formal side of records management. The SharePoint administrator is responsible for the implementation of records management, using SharePoint. In addition, the SharePoint administrator advises the records manager on new developments and requirements arising from the business. For the application of new technologies and the development of new and fun features, staff members from the business will much sooner visit the SharePoint administrator than the records manager. In many cases, records management plays a role in social features of SharePoint as well. Yammer, Office 365 Groups and Delve are examples of this.

If you want to know more about records management in SharePoint, you can find my book SharePoint records management and metadata on Amazon

You can also visit http://ift.tt/1P32Az7, to find additional information about the book, SharePoint records managment or enterprise architecture

by Alfred de Weerd via Everyone's Blog Posts - SharePoint Community

What is Office Web apps server and why do you need to care?

Office Web apps is an online office suite offered by Microsoft that can allow users to create and edit Office files using lightweight , web browser-based versions of Microsoft Office applications : Word ,Excel ,PowerPoint and One Note.

So as mentioned above Office Web apps ( currently knows as Office Online) is a product that was developed by Microsoft to interact with SharePoint Server 2013 ,Exchange Server 2013 and Lync Server 2013 which can help the users in viewing/editing and sharing office files .

Let’s take a look at how Office Web apps work with each of this product separately:

Office Web apps with SharePoint Server 2010:

So until SharePoint Server 2010, Office Web apps used to be a component of SharePoint and it was not a standalone product as it is currently. Deploying Office web apps for SharePoint 2010 includes the below mentioned steps.

1. Installing Office Web apps setup.exe
2. Activating the Office web apps services –>Starting the required service in CA , creating the service application and service application proxies
3. Activating the Office Web apps feature in the site collection.

Also in SharePoint Server 2010 there was no need to patch Office web apps separately as the SharePoint patches also included the Office Web apps patches. So any issue that happens to SharePoint as a product will have an impact on Office web apps as well.

Office Web apps with SharePoint Server 2013:

So with SharePoint Server 2013, Microsoft took a big step ahead and removed Office web apps from SharePoint .What this means is, the bits and binaries that install SharePoint Server 2013 will not have Office web apps as part of it. Its standalone product now and needs to handled and taken care separately.

Note: I’ve noticed a lot of customers who think that Office web apps can support Visio files as well. That’s never ever the case and SharePoint Server 2013 uses Visio service to do that .Please refer to my post on Visio Service to know more about it.

So in a nutshell, SharePoint Server 2013 when integrated with Office Web apps provides updated versions of Word Web App, Excel Web App, PowerPoint Web App, and OneNote Web App. Users can view and, in some cases, edit Office documents in SharePoint libraries by using a supported web browser on computers and on many mobile devices, such as Windows Phones, iPhones, iPads, Windows 8 tablets, and Android devices.

Later in this article I’ll be discussing more on Office webs apps and SharePoint Server 2013 ….

Office Web apps with Exchange Server 2013:

With Exchange 2007 and 2010, Outlook Web Access/App [OWA] users can preview documents attached to e-mails directly from their browser. This feature, known as “Web Ready Document Viewing”  which converts supported documents (Word, Excel, PowerPoint or PDF) to HTML and displays them in the web browser, allowing users to read Word documents, for example, without the need to have Word installed or first downloading the file.

Whenever a user receives an e-mail with a supported attachment, an “Open as Web Page” link appears next to the attachment:

All the user needs to do to preview the attachment is click on the link and the WebReady Viewing version of the document will open.

 

With Exchange Server 2013, there is another method of viewing Office docs. Here you can integrate your Exchange server 2013 with Office web apps .Once that’s done the attached Office document makes a WOPI [Web App Open Platform Interface] call to the Office webs app server to render the document.

Note: Office Web apps cannot open Office files which are IRM [Information Rights Management] enabled.

Office Web apps with Lync Server 2013:

In Lync Server 2010, PowerPoint presentations are viewed in one of two ways. For users who run Lync 2010, PowerPoint presentations are displayed by using the PowerPoint 97-2003 format and they are viewed by using an embedded copy of the PowerPoint viewer. For users who run Lync Web App, PowerPoint presentations are converted to dynamic HTML files then viewed by using a combination of the customized DHTML files and Silverlight. Although generally effective, this approach did have some limitations:

 

1. The embedded PowerPoint Viewer (which provided a more optimal viewing experience) is available only on the Windows platform.
2. Many mobile devices (including some of the more popular mobile telephones) do not support Silverlight.
3. Neither the PowerPoint Viewer nor the DHTML/Silverlight approach supports all the features (including slide transitions and embedded video) found in the more recent editions of PowerPoint.

To help address these issues, and to improve the overall experience of anyone who presents or views PowerPoint presentations, Lync Server 2013 uses Office Web Apps Server to handle PowerPoint presentations. Among other advantages, this new approach allows the following capabilities:

 

1. Higher-resolution displays and better support for PowerPoint capabilities such as animations, slide transitions, and embedded video.
2. Additional mobile devices can access these presentations. That’s because Lync Server 2013 uses standard DHTML and JavaScript to broadcast PowerPoint presentations instead of customized DHTML and Silverlight.
3. Users who have appropriate privileges can scroll through a PowerPoint presentation independent of the presentation itself. For example, while User A is presenting his slide show, User B can scroll through and view any slide she wishes, all without affecting User A’s presentation.

So with that being said, let’s take a look at the supported Office file formats for Office Web Apps

Supported file formats:

Word documents (doc, docx, dotx, dot, dotm extensions)

Excel documents (xls, xlsx, xlsm, xlm, xlsb extensions)

PowerPoint documents (ppt, pptx, pps, ppsx, potx, pot, pptm, potm, ppsm extensions)

*Also once again, please do remember that Office web apps doesn’t support IRM protected files.

More on Office web apps with SharePoint Server 2013 ……

Listed below are the features you get when you use Office web apps with SharePoint Server 2013:

The viewing and editing capabilities of Office webs apps on different devices is given below:

 

 

Now, being a SharePoint Farm Admin/Site collection admin you get to decide how your users can view office files in the document library. There are two ways to change the default behavior so that files open in the client applications (or the default PDF reader) instead:

For the entire SharePoint 2013 farm :  You ( The Farm admin) can adjust the default open behavior on a per-file-type basis for the SharePoint 2013 farm by using the New-SPWOPIBinding and Set-SPWOPIBinding Windows PowerShell cmdlets. These cmdlets can also be used to adjust the behavior of PDF documents.

In site collections or document libraries : Site collection administrators and users can use the OpenInClient feature in SharePoint 2013 to specify whether Office files will be opened in the client application or in the browser. Users can change this setting in the document library properties, and site collection administrators can change it in Site Collection Administration or by using the “Enable-SPFeature” cmdlet to enable the OpenInClient feature.

Now there are certain things which you might need to pay attention to being an IT Pro, you can configure Office web apps for your SharePoint server 2013 farm so that the Office files in the document library make a WOPI call to Office web apps server (a single machine/farm processing the request for all type of Office file i.e. word,excel,powerpoint and One note)  to  render the document  or you can configure an Office web apps farm so that each machine in that farm can take care of processing the request for each file types.

PowerPoint–>A single Office web apps machine to process the request for PowerPoint files alone

Word –>A single Office web apps machine to process the request for Word files alone

Excel–>A single Office web apps machine to process the request for Excel files alone

One Note–>A single Office web apps machine to process the request for One Note files alone.

This option can give you better scalability, however it’s going to cost you a lot.

How to know whether I’m using Excel online, Excel services or Excel Web app while I’m opening an Excel file?

If the URL resembles  “http://[servername]_layouts/15/xlviewer.aspx?id=/Documents/…” then Excel Services is used to render the workbook.

 If the URL resembles  “http://[servername]/_layouts/15/WopiFrame2.aspx?sourcedoc=/Documents/…” then Excel Web App is used to render the workbook.

Difference between Excel Web App and Excel Services in SharePoint:

Excel Web App and Excel Services in SharePoint have a lot in common, but they are not the same. Excel Services is available only in the Enterprise edition of SharePoint Server 2013. Excel Web App is available in SharePoint Server 2013 and SharePoint Foundation 2013. Both applications enable you to view workbooks in a browser window, and both enable you to interact with and explore data.

But there are certain differences between Excel Web App and Excel Services in SharePoint. For example, Excel Services supports external data connections, data models, and the ability to interact with items that use data models (such as PivotChart reports, PivotTable reports and timeline controls). Excel Services provides more business intelligence functionality than Excel Web App, but Excel Services does not enable users to create or edit workbooks in a browser window.

If your organization decides to use Excel Services instead of Excel Web App to view workbooks in the browser, you can use the Windows PowerShell New-SPWOPISuppressionSettings cmdlet to turn off Excel Web App for Excel workbooks.

Office Online File Support:

Here are file types and formats supported in each of the four Office Online applications.

Word Online:

Supported for viewing and editing	Supported only for viewing	Cannot be opened
Word Document (.docx)	Word 97-2003 Document (.doc)**	Rich text format (RTF)
Word Macro-Enabled Document (.docm)*	Word 97-2003 Template (.dot)	Hypertext Markup Language (HTML)
OpenDocument Text (.odt)	Word Template (.dotx)	Multipurpose Internet Mail Extensions HTML (MHTML)
	Word Macro-Enabled Template (.dotm)*	IRM-protected documents
	Portable Document Format (PDF)**	Password-protected documents
		Documents with digital signatures

*The document can be opened, but macros do not run.

**For editing, Word Online saves a new copy of the document in .docx or .dotx format. Word Online can’t save documents in the .doc or .dot formats.

Excel Online: 

Supported for viewing and editing	Supported only for viewing	Cannot be opened
Excel workbook (.xlsx)	Portable Document Format (PDF)	Excel 97- Excel 2003 Workbook (.xls) **
Excel binary workbook file (xlsb)		Excel 97- Excel 2003 Template (.xlt)
Excel macro-enabled workbook (.xlsm)*		Excel Template (.xltx)
OpenDocument Spreadsheet file (.ods)		Comma separated values (CSV)
		IRM-protected documents
		Password-protected documents
		Documents with digital signatures

*The workbook can be opened, but macros do not run.

**On OneDrive.com this format can be viewed. To edit, Excel Online saves a new copy of the document in .xslx format. Excel Online can’t save documents in the .xls format.

PowerPoint Online:

Supported for viewing and editing	Supported only for viewing	Cannot be opened
PowerPoint Presentation (.pptx)	PowerPoint Template (.potx)	PowerPoint Add-in (.ppam)
PowerPoint Show (.ppsx)	PowerPoint 97-2003 Template (.pot)	Rich Text Format (RTF)

OpenDocument Presentation (.odp)	PowerPoint 97-2003 .ppt and .pps*	Portable Document Format (PDF)
	PowerPoint Macro-Enabled .pptm,  .potm, and .ppsm**	PowerPoint 97-2003 Add-in (.ppa)
	Portable Document Format (PDF)	IRM files
		Password files
		Files with digital signatures

* The presentation can be opened, but macros do not run.

** For editing, PowerPoint Online saves a new copy of the document in .pptx format. PowerPoint Online can’t save documents in the .ppt or .pot formats.

OneNote Online:

Supported for viewing and editing	Cannot be opened
OneNote 2010 and later notebooks (.one)	OneNote 2003 or OneNote 2007 notebooks (.one)
	OneNote Package (.onepkg)
	Portable Document Format (PDF)

I guess this pretty much sums up everything you need to know about Office Web apps. Thanks for reading this post. Happy Share Pointing!!!!

by Vignesh Ganesan via Everyone's Blog Posts - SharePoint Community

Announcing The Winner of the SPTechCon Austin Competition

A few weeks ago I did a completion on my blog for a chance to Win a free Pass to SPTechCon Austin 2016.

I am happy to announce the Winner of the competition is Jasmine Hoegh who is pretty excited for going!

@vladcatrinescu @SPTechCon I am too excited about going to the conference. My job is also going to post it in our monthly newsletter!

— Jasmine Hoegh (@SBJISHU) January 25, 2016

Thank you to all 105 SharePointers who participated! I will try to get more Conference passes to give away soon! If you have a conference you want me to try and get a pass to, let me know in the comments! If you want to make sure you won’t miss the chance to win another competition like the page on Facebook , Follow me on Twitter & sign up to the mailing list using the sign up form on the right sidebar of the page!

The post Announcing The Winner of the SPTechCon Austin Competition appeared first on Absolute SharePoint Blog by Vlad Catrinescu.

by Vlad Catrinescu via Absolute SharePoint Blog by Vlad Catrinescu

How to set default value for people picker

In general there is no straight way for pre-populating people picker, but don't worry always there is away! Here I'm going to explain how to do this using InfoPath.

Solution:

1- Open up your form in InfoPath and add a Data Connection

2-  Choose SOAP Web service:

3- Enter the location of SOAP; for SPO it's something like this: https://tenant/_vti_bin/UserProfileService.asmx

4- Choose GetUserProfileByName;

5- Go to Form Load and add an Action Rule and choose Query for data and select GetUserProfileByName

6- Then Add "Set a field's value" Action, from fields choose DiplayName of people piker (here it's Estimator) and click OK:

7- For value click on "Insert field or group" and then choose "Show advanced view":

8- Do following steps:

9- In Filter Data window select Name as shown in picture and click OK:

10- Enter PreferredName (Just type it as text) and click OK:

11- Add another "Set a field 's Value" Action, this time for filling AccountId, choose filed name as following image:

12- Set Name equal to "AccountName" (just type it as text):

13- Re-do step 11, this time for AccountType. Simply enter "User" in Value box:

14- Now rule should be like this:

15- Done ... Now people picker is like this:

by Sarah Safari via Everyone's Blog Posts - SharePoint Community

Custom SharePoint display template

Custom SharePoint display template you can find interesting when you start playing more with branding. For the last few weeks I was very busy at my new job and during this time I was doing a lot of stuffs related to branding. Of course I am not designer, but still I have learn a lot. Today I would like to write about Custom SharePoint display template. It will be third post related to branding (part 1 and part 2). I guess that many of you saw nice widgets which presents upcoming events. Today I would like to show you how to build something like this as it's not possible to that with default sharepoint configuration. At the begging let me write a few words of some basis.

Display template is responsible for format and style of search related web parts, also it presents managed properties and how it will looks like.

In fact display template has two pieces:
Control Template - it's place holder where result from search engine will be stored. Control template is rendered just one time.
Item Template - it's responsible to single item display, for example descriptions, images, title, etc. Each element is rendered separately. Today I will write about item template.

And just one thing. Content Query Web Part, which is very useful sometime is not search based, which means that you can't make modification to related display template... I lost some time to find out that.

Display template can be a part of branding project, which can be build and stored in Design Package. It's a full branding project, which contains all of customization. Ok, let's come back to our Custom SharePoint display template. In first step we should display design manager for our site collection.

Let me remind you that to do that we need active SharePoint Server Publishing feature in our site collection/site.When we display content of our folder with display templates we will see a lot of files, which are responsible for displaying various data. Describing all those stuffs will take to much time, but in general idea is very similar. And I would like to change how Content Search present single element. Let's search for a file which has a title: "Picture on left, 3 lines on the right". This files is used when Content Search webpart present to us possible options for the Item. You can find more about all those files at Technet. Let's select it and make just simple CTRL-C, CTRL-V with changing file name during copy process. Now it's time for SharePoint designer. We are going to display all files and then we are going to:  /_catalogs/masterpage/Display Templates/Content Web Parts/our_file_name. I would like to mention that when we make a copy of our file SharePoint also created additional file with js extension. We don't touch it, we work with HTML.

First step will be modification of the title tag . Title will be used  in web part configuration page. Now it's time for the file itself, as understanding how it works could be a real challenge:

• our variables can be accessed with this entry _#=
• if we want to run JavaScript after our page has been rendered we use code just like below:

<!--#

AddPostRenderCallback(ctx, function() {

//our code

});

_#-->

And following code:

var line1 = $getItemValue(ctx, "Line 1");
var line2 = $getItemValue(ctx, "Line 2");
var line3 = $getItemValue(ctx, "Line 3");


is responsible for values from web part configuration page (managed properties). Now it's time for the code which display day number and first three letters of the month. The code should be at the end of the file:

<!--#_
}
var myDate = null;
myDate = new Date(line3);
var monthNames = ["Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec"];
var myMonth =  monthNames[myDate.getMonth()];
var myDay = myDate.getDate();

AddPostRenderCallback(ctx, function() {             
document.getElementById("monthBox"+line3Id).innerHTML = myMonth
document.getElementById("dayBox"+line3Id).innerHTML = myDay;
            });
_#-->

Let's take a look at the tags where we placed the code. I spent some time to find valid format to make code running. Variable "line3" is third line from configuration page of the web part, and we store there our event date. Then we can use our calculated values in page code:

<div id="CompanyDate" style="float: left; width: 50px; height: 50px; text-align: center; margin: auto;font-weight: bold; font-size:14px">
            <span id="monthBox_#= line3Id =#_"  >month </span>
            <br>
            <span id="dayBox_#= line3Id =#_"  >day </span>
        </div>

This HTML code above has been added to existing one, just before part responsible for image rendering. This ID entry can be strange, but in this way we can create SPAN ID's  in automatic way. Now we need just to publish our file. After that our title should be visible at possible option for the item in the web part Content Search configuration page.  Next time I will show how to configure web part and search service to get the result. And that's all.

This article is based on this post

by Tomasz Szulczewski via Everyone's Blog Posts - SharePoint Community

Tools for setting up standard operating procedures in SharePoint

Almost every organization is under the pressure of some type of compliance training and that reflects why companies put together standard operating procedures to maintain processes that will ensure services and/or products are delivered consistently every time. Setting up a system to manage standard operating procedures is essential and the solutions SharePoint provides is invaluable.

The Brandon Hall Group recently published a 2014 report on why compliance training is so critical to business. What they found is that companies ranked compliance second behind products and services for overall business strategy, many had to demonstrate compliance to an external agency, and compliance effects a large portion of their organization. Here’s the problem…less than half of those in the study felt prepared for a compliance audit. This is not good news. But, fortunately there is a solution with SharePoint and in the following blog, we’ll explain in further detail how you can feel better prepared for such circumstances.

Choosing a library vs. site

First things first, you’ll need to decide how you will organize your standard operating procedures. SharePoint reigns supreme as a content management tool but there are a few ways you can go about organizing your content. The most important thing to consider is content findability. When someone comes to your SharePoint HR Portal, they should find what they expect and they should find it with a minimum of clicks. So, the question is should you store SOPs in a library or site?

Libraries are primarily a tool of document management. Unlike folders, libraries support metadata for search, workflows, versioning, and the implementation of managed processes. Sites, on the other hand, are a tool of information management. Sites are robust and offer the ability to present documents in a broader context – links, calendar, blog. Some organizations found that depending on the situation, their site wasn’t being utilized to its fullest and the library was the only feature being used. Something to consider - a well-defined library looks much better than an unused team site.

If you choose to move forward and structure an SOP library, the best approach is to get rid of the Shared Documents library which tends to become a “junk drawer.” Don’t ask where to put it. Ask, where am I going to find it. Think about how you access your documents, and then build libraries around that.

The next step after creating a library is to distinguish how much control is needed. Who should have access to the content, add or change content, and with what restrictions?

Make sure standard operating procedures are findable with metadata

Metadata allows for library configuration that enforces consistent document classification which in turn helps improve the user’s search results. If you have a very large amount of SOPs, than metadata navigation is a tool you’ll want to get familiar with.

When metadata navigation is configured for a list or library, a tree control on the left-hand side of the page displays a hierarchy of both folders and managed metadata terms that can be used to filter the view of items in the list or library to create dynamic displays of content.

Setting up metadata navigation

1. Go to the list or library for which you want to configure metadata navigation.

2. Click the List or Library tab of the ribbon, and then click List Settings or Library Settings.

3. Under General Settings, click Metadata navigation settings. In the Configure Navigation Hierarchies section, select the field or fields that you want to display in the navigation hierarchy and then click Add.

4. By default, the navigation tree displays folders. If you do not want folders to display, select Folders and then click Remove.

5. In the Configure Key Filters section, select the fields that you want to add as Key Filters, and then click Add.

6. In the Configure automatic column indexing for this list, specify whether you want to create indexes automatically on this list. This improves the performance of the queries that users perform when they use the navigation tree and Key Filter columns that you specified. It is recommended that you select the option automatically manage column indices on this list.

7. Click OK.

Cover all your bases with SharePoint workflows

With standard operating procedures, it is imperative that there is structure from how the document is created, edited, finalized and approved. Workflows in SharePoint are a great tool to automate movement of documents or items through a sequence of actions or tasks that are related to a business process. This can happen on a document or library level.

Types of workflows:

• Approval - This workflow routes a document or item to a group of people for approval.
• Collect Feedback - This workflow routes a document or item to a group of people for feedback. Reviewers can provide feedback, which is then compiled and sent to the person who initiated the workflow.
• Collect Signatures - This workflow routes a document to a group of people to collect their digital signatures.
• Disposition Approval - This workflow, which supports records management processes, manages document expiration and retention by allowing participants to decide whether to retain or delete expired documents.
• Group Approval - This workflow is similar to the Approval workflow, but it uses a designated document library and offers a personalized view of the approval processes in which a user is participating.

Adding a workflow:

• Open the list or library for which you want to add or change a workflow.
• On the Settings menu, click List Settings, or click the settings for the type of library that you are opening.
• On the Customize page, in the Permissions and Management column, click Workflow Settings.
• On the Add a Workflow page, in the Workflow section, in the Select a workflow template list, select the name of the workflow that you want to use.
• In the Name section, type a unique name for the workflow. This name will be used to identify the workflow to site users.
• In the Task List section, specify a tasks list to use with this workflow.
• In the History List section, select a history list to use with this workflow. The history list displays all of the events that occur during each instance of the workflow.
• In the Start Options section, specify how (automatically or manually), when (item update, creation or both), or by whom a workflow can be started. Note that the available start options are determined by the workflow template and will differ from one workflow to another.
• Click Next to configure workflow-specific settings, as necessary.
• After you have configured workflow-specific settings, click OK to finish adding the workflow to the list or library.

Keep all standard operating procedure records with auditing and version control

According to the previously mentioned Brandon Hall Group study, many organizations must demonstrate compliance to an outside agency. SharePoint makes it easy with auditing and version control.

Now that we’ve added metadata and workflows to your SOP library, now it’s time to set versioning.

• Navigate to your standard operating procedures library
• On the ribbon, in the Library Tools group, click the Library tab.
• Click Library Settings.
• On the Library Settings page, under General Settings, click Versioning settings. The Versioning Settings dialog box opens.
• In the Document Version History section, select one of the following options: create major versions or create major and minor versions.
• Optional: Limit the number of versions you want to retain.
• Optional: Determine which users should be allowed to see draft items in the document library.
• Optional: Determine whether you want to require check out in this library.
• Click OK to close the dialog box and return to the Document Library Settings page.

 

SOP training is crucial because not only is it the backbone of the organization but it also becomes the living, breathing foundation that evolves with the organization. Add to the fact that about 78 percent of companies employ SharePoint, wouldn’t it make sense to utilize its supreme content management capabilities for your standard operating procedures? Content management, advanced search capabilities, workflows, versioning and auditing are just a click away. See how SharePoint can cover all your compliance needs to make your job easier.

by Amber Rasmussen via Everyone's Blog Posts - SharePoint Community

SharePoint 2016 Reaches RC Stage: What It Means for You

Unless you have been asleep for the past week, then you should have seen that SharePoint 2016 hit Release Candidate. Here's what that means, now and moving forward.

read more

by via SharePoint Pro

SharePoint Community Newsletter - Week 3

Hello SharePointers...here's the weekly round-up.

COLLAB365 SOLUTIONS DAY - DOES SHAREPOINT AND OFFICE 365 MANAGEMENT HAVE TO BE SO HARD?

We don't think so and neither do Sharegate! Join SharePoint legend, Benjamin Niaulin for an in-depth session explaining how to take control of your SharePoint and Office 365 environments. If you need to know how to move data from one platform to another, or even how to manage security policies - this session is a MUST SEE. Benjamin will also be joined by 3 other fabulous solution providers who will be explaining how they can help solve your most common SharePoint / Office 365 problems. Join Sharegate, Rencore, Axioworks and the company behind SP Data Manager on February 18th’s for our next Collab365 Solutions Day.

Read more : http://ift.tt/201OR34

====

COLLAB365 TODAY (RE)LAUNCHED

As mentioned previously, we are currently busy uniting everything we do for the SharePoint Community under the 'Collab365' brand. This will hopefully make it much more familiar and easy to find what you need. The first launch I would like ot announce, is the introduction of "Collab365.Today" which will bring you all of the latest and greatest about SharePoint, Office 365 and Azure categorised for your convenience.

Read more : http://collab365.today/

====

COLLAB365 SUMMIT - CALL FOR SPEAKERS

The "Collab365 Summit" Call for Speakers (and Live Show guests) is still open. The Call for Speakers will end on 1st March 2016 and we'll will let everyone who we can fit in know during March. For those we cannot fit into this event, we will invite you to submit for the 24 Hour Global Conference in October 2016.

Note: This is an "on-line" conference that will be streamed from Redmond and although there are some opportunities to take part live, to present a session you do NOT need to travel to Redmond. In other words, your session can be delivered 100% from the comfort of your office desk!

Call for Speakers ...
http://ift.tt/1ZQqPmn

Call for Guests on the Live Show ...
http://ift.tt/201OPrZ

Registration now open (2000 places available) ...
http://ift.tt/1PPzbtq

====

COLLAB365 GLOBAL CONFERENCE - LIVE TV CHANNEL FOCUS (Andy Talbot)

Check out Collab365 Live Show Host, Andy Talbots, long overdue recap of out last 24 hours conference. Andy also shares links to some of his amazing live content ranging from sessions on "Office 2016 to in-depth discussions about migrating the Cloud.

Read more : http://ift.tt/201OR37

====

IS IT TIME TO RECERTIFY YOUR MCSE SHAREPOINT 2013? LEARN HOW

For some of you SharePoint Experts who took your exams in early 2016, the time to re-certify your MCSE SharePoint 2013 might be approaching. As you probably know, Microsoft requires you to re-certify every three years, to make sure your skills are still up to date.

http://ift.tt/1U6WwpZ

====

CALLING ALL SHAREPOINT MOBILE USERS! THE BEST IS YET TO COME IN SHAREPOINT 2016

Fpweb.net intro "We’ve been keeping up with all of the many new features that the upcoming SharePoint 2016 will be providing. Aside from newer increased speed, greater usability, and a larger content database size (among many other exciting elements), one of the best features of the latest version of SharePoint is all of the enhancements that are aimed at smartphone and tablet users."

http://ift.tt/201OR39

by Mark Jones via Everyone's Blog Posts - SharePoint Community

SharePoint: Enabling Knowledge Management

I had the chance recently to have chat with TechnologyAdvice’s Josh Bland (@JoshBlandTA). This interview was a part of the TechnologyAdvice Expert Interview Series. The series explores a variety of business and technology landscapes through conversations with industry leaders.

There’s plenty of great content there, including interviews with some of the speakers for the SharePoint Technology Conference – SPTechCon Austin – coming up February 21-24. If you register with code ANDERSON, you’ll get an extra $200 off any other discounts you might receive.

In this episode we discussed how I see SharePoint fitting into a successful knowledge management strategy, how modern work happens, big things that happened with SharePoint in 2015, and of course, the upcoming SPTechCon. If you enjoy this interview, you might want to check out the one I did with Josh last summer, just before SPTechCon Boston: Software Adoption: A People Problem, or A Technology Problem?

Below is an excerpt from the conversation:

Josh: What would you say, Marc? How would you sort of summarize the year? What sort of big developments occurred and what would you say were some of the highlights from 2015 in SharePoint?

Marc: One of the biggest things is that the hybrid story that Microsoft is just telling is getting richer and richer. We saw some capabilities that are available on Office 365 starting to filter back on Premises, and that’s via hooking up to a SharePoint online instant. So that you can sort of take advantage of the best of the cloud but still keep your content in-house. And of course, we’re seeing tremendous strides forward in Office 365 as well. It’s hard at this time of the year to look back and try to remember, how many of these things actually got stuffed into this one year? And it’s pretty incredible when you look at how many things have changed over the last year in the SharePoint space. We have things like Delve and groups and the video portal, and all these things that have really come into their own this year and shown that Microsoft is not sitting still, that they’re — I’m very bullish on Microsoft in what they’re doing with Office 365. And I’m not an easy one to convince [chuckles]. But I see them doing some very cool things – Planner – just all kinds of new experiences as they say, with fantastic user interfaces that really are bringing the whole platform ahead in leaps and bounds.

Josh: I want to hear what were some of the sort of difficulties that you have experienced, not only with your customers, but just in general that you think the industry has seen from SharePoint?

Marc: An ongoing challenge for anyone using these platforms is that the development story continues to evolve. And that’s not a bad thing, but for your average developer who’s trying to sort of swim with both hands tied behind their back, sometimes, keeping ahead of what the enterprise wants, it’s difficult because we look at the different– historically we’ve had features and solutions, we’ve had the sandbox model now. We have the apps crossed out, add-in model, and we’ll probably see some evolution from here. People are continually having to keep their skills fresh. Now, that to me is a damn good thing. Anybody who stops learning and thinks that what they know now is going to serve them forever is sort of letting themselves die intellectually. The fact that we have to learn new things all the time is a good thing. We’re seeing an evolution from server site code toward JavaScript and client site code to a degree that is really — it’s been a bumpy ride for some people over the last couple of years to make that mental switch. As we’re seeing better experiences coming out of Microsoft, we’re seeing these challenges for the developers inside enterprises who are trying to build bespoke functionality that is unique to that organization, or something that that organization wants that Microsoft does not provide exactly. It’s that 20% that’s actually the hard part. That’s going to be an ongoing set of challenges – understanding how this hybrid model, as you mentioned fits into the organization’s ethos – is going to be a tough one for a lot of people to get to.

Two years ago we would have been talking about the tremendous fear about security and, “Does the cloud make sense?” And, now we always talk about it as, “Which part of the cloud makes sense to me? Which parts should I take advantage of? Where am I going to get the bang for my buck?” So, we’re on a different part of the learning curve for all of that. But the development story is tough. And that hybrid aspect just adds a little bit of complexity to the whole thing.

Josh: One final question here on SPTechCon 2016. Do you see a lot of differences between Boston and Austin? All that to say, what do you think will be different about this year, Austin 2016 vs. Austin 2015 or Boston 2015?

Marc: The obvious difference is that we’ve got SharePoint 2016 coming up. So — Yeah, new software smell. There are a couple things there. One is obviously there is some new software out there; new bits. So, people will be able to hear some good information about what’s there, why would you be interested in it, how does it work and that sort of thing. One of the best things though about SPTechCon is that they’re very careful to manage the mix between: here’s the shiny new stuff and here’s that stuff that you are actually still stuck working with [chuckles]. There are still a lot of people in the crowd who use SharePoint 2010, there’s still a lot of people who are using 2013 obviously. There’s a great mix of content across that spectrum as opposed to just going for the new stuff. Go to the Microsoft conference for that. They’ll only talk about the new things. But SPTechCon has been traditionally very good about having that balance, so that everybody who comes to the conference gets a lot of depth out of it.

This podcast was created and published by TechnologyAdvice, an Inc. 5000 company looking to help buyers find the best cloud storage, payroll systems, and more. Interview conducted by Josh Bland.

by Marc D Anderson via Marc D Anderson's Blog

Cloud Warning! The risk of online services

I ran across a dark underbelly of cloud services

picture taken by cjohnson7

this week. It was fairly unexpected but I think that it emphasizes one of the key problems when looking at cloud services.

Who really owns the data?

This is the question when we start looking at cloud services. The immediate answer from cloud providers is most likely "you do!" but is that really the case?

Just this week, I have a situation that refutes cloud service congeniality. To set the scenario I must confess that I  have possibly "lost" the raw material files that were used to create some online education packages. This was due to system malfunction and data loss. My need of backups is only a side-note in this narrative though.

The stormy weather of cloud services is revealed when our online learning host was approached about downloading copies of the materials that we had uploaded. We were given a solid "that is not available" response.

I am honestly stymied by this response. I created the content. My company owns copyright. I uploaded it to their service, yes, but I am very confident that I never signed an agreement to hand over rights to my digital files. This greatly concerns me when I look at the technology world crying "cloud, cloud, cloud". Is this really the way of the future with possession of bytes the nine-tenths of the law that matters?

This particular episode has once again soured my belief in cloud services. If you want to retain your data securely with a guarantee of access not confirmed only by your monthly bill, I would highly recommend to think twice before jumping to your cloud panacea.

Do you have any cloud horror stories?  Please feel free to drop them in the comments.  Best Wishes.

by noreply@blogger.com (Robert Schley) via SharePoint Solutions Blog

How to find permission changes in SharePoint 2013 site collection

Introduction

SharePoint is gradually emerging as the most preferred collocation platform for enterprises. The greatest challenge to any collaboration platform is to ensure security without compromising the collaboration facilities. Access to SharePoint data is controlled by the permissions given to users. But what would happen if permissions can be changed without being noticed? Such a possibility should be avoided at any cost. That is why auditing permission changes becomes important in SharePoint. SharePoint has the facility to audit permission changes and there are alsosome specialized third-party SharePoint auditing solutions that can provide all the change details in a very simplified way.

Here are the steps to audit permission changes using SharePoint 2013 features:

• Enable Audit logging (Central Administration>Application Management>Manage service applications)

• Configure audit settings (Site settings>Site Collection Administration>Site collection audit settings)

• View audit logs (Site settings>Site Collection Administration>Audit log reports)

Step 1 :
Go to Central Administration>Application Management. Under Service Applications, click Manage service applications.

Step 2 :
Select the Secure Store Server Application, go to the tool bar and click Properties.

Step 3 :
Check the Audi log enabled check box; click OK.

Step 4 :
Click OK when the confirmation message is displayed.

Step 5 :
Click the Settings icon and then click Site Settings.

Step 6 :
Under Site Collection Administration, click Site collection audit settings.

Step 7 :
Now choose Editing users and permissions, and click OK.

Step 8 :
Now again go to Settings > Site Settings. Under Site Collection Administration, click the link Audit log reports.

Step 9 :
Under Security And Site Settings Reports, click the link Security Settings.

Step 10 :
Select the location to save the excel report using the Browse button; click OK.

Step 11 :
To get the auditing details, click the link Click here to view the report.

Conclusion :
By default, user permission changes are not enabled in SharePoint. After enabling audit logging, and configuring Site collection auditing setting, you can get the details of users and permissions changes on SharePoint audit log reports. For more simplified auditing, you can rely on specialized SharePoint auditing solutions.

by Satyendra Tiwari via Everyone's Blog Posts - SharePoint Community

Is it time to recertify your MCSE SharePoint 2013? Learn how!

For some of you SharePoint Experts who took your exams in early 2016, the time to re-certify your MCSE SharePoint 2013 might be approaching. As you probably know, Microsoft requires you to re-certify every three years, to make sure your skills are still up to date.

But how do you renew your MCSE SharePoint certification? At the time of writing this blog post, the SharePoint 2016 certifications, are not out yet, and there is no exam to renew the MCSE. However, Microsoft made it possible for everyone to renew their MCSE SharePoint trough Microsoft Virtual Academy (MVA). Let me first start with what you need to do, and then I will give you my opinion. The first thing you need to do, is create an account at http://ift.tt/1NIVLB9 , listen to the following modules, and then pass the associated assessments.

 

 

Step	Microsoft Virtual Academy course	Skill
1	Deep Dive: Building Blocks and Services of SharePoint	Configure advanced productivity tools
2	Deploying & Managing SharePoint 2013 with PowerShell	Manage user access Manage workload optimization Manage productivity solutions Implement Enterprise Search
3	Developing Microsoft SharePoint Server 2013 Core Solutions Jump Start	Manage user access Manage productivity solutions
4	Developing SharePoint Server Advanced Solutions Jump Start	Implement Enterprise Search
5	Managing SharePoint On-Premises vs. SharePoint Online	Architect and install SharePoint
6	SharePoint 2013 Best Practices	Architect and install SharePoint Manage workload optimization
7	Support Corner: Configure SharePoint Outbound Hybrid Search	Architect and install SharePoint
8	Support Corner: Manage Storage Quota for SharePoint Online	Manage user access
9	Upgrading to SharePoint 2013	Architect and install SharePoint
10	Initial Implementation of SharePoint Server	Architect and install SharePoint
11	Plan a Collaboration Solution Using Office 365	Manage productivity solutions

After you finish and pass all of them, you need to email your MVA Username and your Microsoft Certification ID to certquest@microsoft.com to get your transcript updated.

Pros

Making re-certification available through MVA does have its advantages:

1. It’s FREEJ.
2. It’s easy to do on your own time.
3. You get to pass the assessment after every “module” allowing you to be able to restart a specific test only.

Cons

I don’t know what Microsoft’s plan is for SharePoint 2016 certifications, but if their goal of having the MCSE SharePoint certification without version numbers, everyone could be SharePoint certified and up to date until 2019, even if they didn’t do a SharePoint 2016 exam. But before talking about that in detail, let’s see what Microsoft will do for SharePoint 2016. Here are some cons according to me, on re-certifying professionals through MVA.

1. Dumps will be even easier to access, as MVA probably has an a lot smaller question pool, and anyone can take unlimited tries, so you can probably find questions in a few minutes on the net.
2. Certification value will go even lower. Everyone knows the value of certifications went down in the last few years, and being able to do your re-certification assessments, unlimited number of times until you get it right, brings down the value of the cert.
3. Some courses have no link to the MCSE SharePoint, or its intended audience. For example, let me talk to you about the Deep Dive: Building Blocks and Services of SharePoint . That 7h course, talks about CSOM, Rest, Event receivers, and stuff for the MCSD… it has nothing to do with IT Pros, which should be the intended audience for a MCSE. Another one, Developing Microsoft SharePoint Server 2013 Core Solutions Jump Start . Wait so I need to do a 6h jumpstart for the 70-488 exam, which as an MCSD exam, and be able to PASS it, in order to be a SharePoint admin? It makes no sense.

The total time of videos, not including lab and assessments to re-certify your MCSE SharePoint 2013 is 36 hours. I think it’s quite a lot of videos to watch, especially that 12 of those hours are strictly dev, and SharePoint Administrators will have to learn to create both SharePoint Apps and SharePoint Farm solution, and be familiar with CSOM, REST and another technologies that they don’t touch in their day to day jobs.

Don’t get me wrong, I do think that it’s good to learn new skills, and it’s not a bad thing for SharePoint Administrators to learn how to develop for SharePoint. But I don’t think they should have made it mandatory, for a SharePoint Admin to know how to dev, in order for him to retain his IT PRO MCSE Certification.

Here is the official Microsoft details + FAQ about the re-certification process:   What’s your opinion for this new way to renew your MCSE SharePoint Cert? Do you have any other Pros or Cons? Let me know in the comments!

The post Is it time to recertify your MCSE SharePoint 2013? Learn how! appeared first on Absolute SharePoint Blog by Vlad Catrinescu.

by Vlad Catrinescu via Absolute SharePoint Blog by Vlad Catrinescu

Minimal Download Strategy feature in SharePoint 2013

This is a new feature that came up in SharePoint 2013 that is used to optimize page rendering. It reduces the page loading time by sending only the differences that were made to the page when users try to access a new page.

So in detailed words, Minimal download strategy takes care reducing the amount of data that the client browser has to download when users navigate from one page to another page within a SharePoint site. When a user browses a site that has the MDS feature enabled on it, the user will see only the differences (or delta change) between the current page and the requested page.

Methods to activate Minimal Download Strategy:

The Minimal Download Strategy feature (MDS) can be enabled in a SharePoint site using the below mentioned methods.

1. Activate the MDS feature using the site settings UI.
2. Using PowerShell Command
3. Using Server Object Model
4. Using Client Object Model

Now, let’s take a look at the first two methods….

Using the site settings UI:

Go to site –> Site settings –>Manage site features–> Activate Minimal Download Strategy

Using Power Shell command:

Use the below mentioned Power Shell command to activate the MDS feature in a site.

$web=Get-SPWeb “http://ift.tt/1J8VfOA;

$web.EnableMinimalDownload=$true;

$web.Update();

To disable the feature, use the below command:

$web=Get-SPWeb “http://ift.tt/1J8VfOA;

$web.EnableMinimalDownload=$false;

$web.Update();

Enable/Disable MDS through PowerShell:

You can use the “Disable-SPFeature / Enable-SPFeature” commands to enable or disable the MDS feature.

The following command will disable the MDS for a particular site.

Disable-spfeature –url http://SharepointSite –identity “MDSFeature”

Power Shell Command Enable/Disable MDS across all web applications:

foreach($webApp in Get-SPWebApplication)

{

    foreach ($SPsite in $webApp.Sites)

    {

       foreach($SPweb in $SPsite.AllWebs)

        {

             Disable-SPFeature –identity “MDSFeature” -URL $spweb.URL -confirm:$false

        }

    }

  }

Identifying whether MDS is working on your site:

Once you’re done activating the MDS feature in your SharePoint site you can confirm its functionality by taking a look at the site url …

You can notice all the pages having “start.aspx” for rendering.

The requested new page url will have a prefix of “#” before it.

URL’s formatted in MDS mode:

Non-MDS URL	MDS URL
http://server/SitePages/	http://server/_layouts/15/start.aspx#/SitePages/
http://server/subsite/SitePages/home.aspx	http://server/subsite/_layouts/15/start.aspx#/SitePages/home.aspx
http://server/_layouts/15/viewlsts.aspx?BaseType=0	http://server/_layouts/15/start.aspx#/_layouts/viewlsts.aspx?BaseType=0

So how this works:

There are 2 components that enable MDS:

1. Server-side
2. Client-side

Each page will be divided into multiple sections.

When a client requests a new page, the server calculates the delta (changes). Only the changed sections will be sent to the client. The client will be smart enough to patch the received sections to appropriate sections.

Let’s take a look at the below mentioned example from TechNet:

Figure 1 shows the sections that change from page to page and therefore require an update. The delta usually includes the data in the (1) content areas, as well as other components such as (2) navigation controls.

We can identify a site that has MDS enabled by taking a look at the URL. An MDS-enabled site has the (3) _layouts/15/start.aspx page in the URL followed by a hash mark (#) and the relative URL of the requested resource, as shown in

Figure 1. For example, the following is the MDS-formatted URL for the page newpage.aspx:

https://sp_site/_layouts/15/start.aspx#/SitePages/newpage.aspx

This is equivalent to the below mentioned non–MDS-formatted URL:

https://sp_site/SitePages/newpage.aspx

MDS Flow Mechanism:

1. The browser requests the changes between the current page and a new one in the SharePoint site.
2. The MDS engine in the server calculates the delta between the current and the new pages.
3. The MDS engine in the server sends the delta to the MDS engine in the client.
4. The MDS engine in the client replaces the changed areas on the current page with the new page content.

Benefits of Minimal Download Strategy :

• Speed:This is the main objective of using MDS in your SharePoint site. When you are using MDS, the browser doesn’t have to reprocess the chrome user interface (UI). MDS also reduces the payload compared to a full page load.
• Smooth transitions:By updating only the areas that change, you draw the user’s eye toward these areas, as opposed to a full page load where the whole page “flashes.” When the whole page is updated, the user must parse it in its entirety to detect what is new. Users have an easier time navigating a site that only updates the areas that changed from the previous page.
• Browser navigation controls:Other AJAX-based systems confuse the previous and next buttons in browsers. Because MDS updates the URL in the browser window, the previous and next buttons work just as they are supposed to.
• Backward compatibility:The MDS engine either provides MDS navigation immediately or detects when it isn’t possible. In the case where MDS navigation isn’t possible, a full page load occurs instead. This process is called failover, and it ensures that all pages render properly regardless of whether they contain MDS-compliant components. MDS also works nicely with search engines because the href attribute of anchor tags uses the regular, non MDS-formatted URLs. Instead, the MDS engine in the client captures the onclick event and uses it to communicate with the server.

Note: The Minimal Download Strategy is enabled by default and can be disabled if necessary .You can disable it on a per Web application basis /Site basis using the UI or PowerShell command.

So in a nutshell, the MDS (Minimal Download Strategy) is a new feature that came up in SharePoint 2013 that helps in page optimization by only loading the changes made to a page when an end user tries to access a new page in a SharePoint site.

Happy SharePointing !!!  Thanks for reading this post.

 

by Vignesh Ganesan via Everyone's Blog Posts - SharePoint Community

Looping Through Content in a SharePoint 2013 Site Workflow – Part 2 – Setting Up App Permissions

This entry is part 2 of 2 in the series Looping Through Content in a SharePoint 2013 Site Workflow

Wait, is a workflow an app? Well, as they keep trying to tell us, everything is an app. No, an Add-in.

Before we can even think about writing the workflow (which on some levels turned out to be the easy part of all of this), I had to figure out the authorization side of things. It wasn’t enough to get the digest token from the server – there’s a more heavy duty permissions set up required even to make the REST calls into other Webs (sites to normal people).

Luckily I have good friends in the community. Matt Bramer (@ionline247) was the first person who replied to one of my tweets, and he gave me some good tips. Through him I found that Fabian Williams (@fabianwilliams) had written several blog posts about the trials and tribulations he went through so that I wouldn’t have to. But it’s still confusing, so here are the high level steps I went through.

Enable the “Workflows can use app permissions” Feature in your Site

This is documented fairly well at Create a workflow with elevated permissions by using the SharePoint 2013 Workflow platform, but here’s my version.

Step 1 – Allow the workflow to use app permissions

Go to Site Settings in the site where you want to run the workflow and turn on the Workflows can use app permissions feature.

Step 2 – Grant full control permission to a workflow

This is the step that gets pretty weird. We have to give this workflow the permission to run as if it’s an app add-in (though one might say that it’s an app add-in already – everything is an app add-in, right?).

Navigate to Site Settings and then under Users and Permissions, to Site app permissions. If things have gone according to plan, you should see Workflow as one of the two or more items listed here.

What you want to grab is the yellow text below. It follows a bar character – “|” – and precedes an “@” character.

Now you have to navigate to a hidden, super secret page at:

http://yourtenant/sites/yoursitecollection/_layouts/15/appinv.aspx

In the example on MSDN, they send you off to the /sites/AppCatalog Site Collection for this. That’s only because they are showing an example interacting with a list there. You should go to the secret page where you want the workflow to run. (Yes, I was down a rat hole on this for a while. Maybe I was just being stupid. It seemed like they were telling me I need to give permissions on the App Catalog site for this to work.)

So go to the super secret page in your Site Collection, paste in the yellow stuff from above, and click the Lookup button. The next three fields will be filled in. You shouldn’t need to change anything in those fields.

Next you need to paste this XML into the last field called Permission Request XML. Don’t try to get all smart about it like I did: paste in EXACTLY this XML – don’t make any changes.

You have two options here:

<AppPermissionRequests>
  <AppPermissionRequest Scope="http://sharepoint/content/sitecollection/web" Right="FullControl" />
</AppPermissionRequests>

or…

<AppPermissionRequests>
  <AppPermissionRequest Scope="http://sharepoint/content/sitecollection" Right="FullControl" />
</AppPermissionRequests>

In this case, I went with the latter; I want my workflow to have permissions on the entire Site Collection. The former would give my workflow permissions only in the subsites of the Site Collection; I need permission on the root of the Site Collection because I want to iterate through the subwebs (subsites) from there.

Click on the Create button.

Next you’ll be asked if you trust the workflow. One would think this would be a given, but click the Trust It button.

 

At this point, you have the permissions set up which give you the possibility of looping through the subsites off the root, even though you haven’t created an actual workflow yet. (Or, if you’re like me, you beat your head against the workflow first and then realized you had to figure this part out.)

References for this step

• Gotcha on SharePoint Designer Workflows in App Step by Fabian Williams
• ACTUALLY RESOLVED: Unable to Create List using SharePoint 2013 REST API in SPD2013 by Fabian Williams
• Create a workflow with elevated permissions by using the SharePoint 2013 Workflow platform

by Marc D Anderson via Marc D Anderson's Blog