SharePoint Workflow 2011
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

SharePoint Workflow 2011

  • 1,173 views
Uploaded on

SharePoint Workflow 2011

SharePoint Workflow 2011

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,173
On Slideshare
1,090
From Embeds
83
Number of Embeds
1

Actions

Shares
Downloads
33
Comments
0
Likes
0

Embeds 83

http://estarktechnologies.wordpress.com 83

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • When taking this by itself it does not seem like much, and you are probably thinking how does this help me? Let's take this a step further. If you automate a process that helps you be more efficient, and you gain insight into your processes that continually make it more so. Even 1 minute improvement makes a difference. How you ask?
  • Build VS. BuyGovernance Typical sharepoint projects – bring in contractor and custom build a solution.Walk through-Reporting Custom VS OOB-Escalations Organizations seeking to involve the business users and analysts in all aspects of development, not just during the requirement gathering.One of the reasons for the success of SharePoint has been its ability to empower the end users. From creating custom views on lists, customizing Web Parts and building workflows, SharePoint has allowed the end-users to create much of the functionality they need without relying on IT each step of the way. However, in many instances this has led to organic growth that can get out of control easily. By enhancing the collaboration between these roles and providing a model for better IT governance, SharePoint 2010 makes further inroads in this area.
  • event receivers
  • PrivilegesIn Windows SharePoint Services 3.0 workflows executed by using the System account. Windows SharePoint Services 3.0, of course, respected the permissions of the workflow initiator. However, in SharePoint Foundation 2010, the introduction of high privilege workflows allows a workflow initiator to specify a higher privileged account to run the workflow, thereby providing a type of delegation or elevation of privileges.Usage ExamplesThis capability might be used if a special document repository has limited permissions. Only a designated group has rights to it, which might not include the workflow initiator. However, an organization wants a workflow that requires, as one of its steps, copying a document into this repository. With an elevated permission level, the workflow designer can specify a higher privileged account to perform the copy operation
  • - Basic business requirement
  • Workflow Model only Limited to using SharePoint Workflow Shapes No ability to go “Back” in the model Duplication of workflow logic Model not representing the actual business problem
  • - Basic business requirement
  • Build VS. BuyGovernance Typical sharepoint projects – bring in contractor and custom build a solution.Walk through-Reporting Custom VS OOB-Escalations Organizations seeking to involve the business users and analysts in all aspects of development, not just during the requirement gathering.One of the reasons for the success of SharePoint has been its ability to empower the end users. From creating custom views on lists, customizing Web Parts and building workflows, SharePoint has allowed the end-users to create much of the functionality they need without relying on IT each step of the way. However, in many instances this has led to organic growth that can get out of control easily. By enhancing the collaboration between these roles and providing a model for better IT governance, SharePoint 2010 makes further inroads in this area.
  • Prescriptive Guidance: Think goals, Analyze what your needs are, think about your processes, not just right now but thinking beyond.But for processes where differentiation can make or break the success of a company, like customer service or order management, best practices just aren’t good enough and therefore, static packaged apps alone aren’t good enough,” Leaver says. “When it comes to those differentiating processes, companies could easily get leapfrogged by the competition if they wait for the app vendors to ‘get’ BPM.”Success comes down to a few simple steps. First, make sure that you have a specific process in mind that you would like to improve with a BPM product. Next, monitor the process to learn how it works now. (You can use BPM monitoring software to do this.) Then, you and the process owner need to figure out how you want to change the process and redesign it accordingly. If it's appropriate, you can use a BPM workflow application to manage the new process. Cook of the Star Alliance says that a successful BPM project leaves a company with a documented set of business rules that could prove to be its important intellectual property, as well as provide a road map for future development of IT projects. "It's hard to extract and document years of experience," he says. "You end up with tons of information. But it ends up making [future projects] much easier for IT