Thursday, April 19, 2012

[sharepointdiscussions] Digest Number 4427

Messages In This Digest (1 Message)

1a.: Re: Workflow policies/abilities From: Knox

View All Topics | Create New Topic

Message

1a.: Re: Workflow policies/abilities

Posted by: "Knox" kcameron@kpmg.com.au knoxcameron

Tue Apr 17, 2012 6:24 pm (PDT)

Eric

Further to Paul's comment, with SharePoint 2010 you have much better control over what people do with SharePoint Designer. At the farm level, you can restrict whether or not it can be used to detach pages from the site definition, or to customise master pages, or manage site structure. Site collection administrators also have controls on the use of SPD in their site collection.

So you can enable use of SPD for workflows, and things like dataform web parts, without opening up a risk that users will "break" a site. I suggest as a "toe in the water" that you select the setting to enable use of SPD but leave all the three detailed settings mentioned above disabled. Ensure the rights to use SPD within the site collection are kept to a limited group of users for the purpose of the workflow.

Regards
Knox

--- In sharepointdiscussions@yahoogroups.com, "Paul Stork" <pstork@...> wrote:
>
> You can rough in the overall flow of a workflow in Visio. But that's just a
> tool for using with business users to discuss the overall flow. The actions
> and conditions added in Visio have no details behind them and aren't an
> actual workflow. Once the general flow of the workflow is designed then you
> have to import that into SPD and fill in the rest of the details. Visio is
> another tool its not a replacement for SPD when building workflows.
>
>
>
> Paul Papanek Stork
>
> Chief Architect . ShareSquared, Inc. . <http://www.sharesquared.com/>
> http://www.ShareSquared.com
>
> The SharePoint Solution Experts!
>
>
> <https://mvp.support.microsoft.com/profile=6D05CC8D-32ED-4626-A29E-142DC7A68
> 0E0> SharePoint MVP, MBA, MCT, MCSE+I, MCSA, MCSD, MCDBA, MCITP, MCPD
>
> <mailto:Paul.Stork@...> Paul.Stork@... .
> 800.445.1279 x404
>
> blog: <http://dontpapanic.com/blog> http://dontpapanic.com/blog . twitter:
> <http://twitter.com/pstork> @pstork
>
>
>
> The information contained in this e-mail message may be privileged,
> confidential, and protected from disclosure. If you are not the intended
> recipient, any further disclosure or use, dissemination, distribution, or
> copying of this message or any attachment is strictly prohibited. If you
> think that you have received this e-mail message in error, please delete it
> and notify the sender.
>
>
>
> From: sharepointdiscussions@yahoogroups.com
> [mailto:sharepointdiscussions@yahoogroups.com] On Behalf Of eeeeeeeee9000
> Sent: Tuesday, April 17, 2012 9:01 AM
> To: sharepointdiscussions@yahoogroups.com
> Subject: [sharepointdiscussions] Workflow policies/abilities
>
>
>
>
>
> We've recently migrated to SP2010, although much of the site is set up to
> appear in the 2007 skin.
> We are getting requests from users to be able to create Workflows. We never
> did this much in previous iterations chiefly due to a lack of training and
> understand of how to accomplish this.
> I understand in 2010 you can actually design workflows in Visio. But it
> appears that they still need to be imported/exported via SP Designer.
> The last thing we feel we want to do at this juncture is open up the
> enterprise to untrained users with Designer. I was wondering how this role
> is handled in other institutions? This is for our intranet, but we will be
> facing a similar situation for our publishing site eventually.
>
> Eric
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

Back to top
Reply to sender | Reply to group | Reply via web post
Messages in this topic (3)