Showing posts with label SPD. Show all posts
Showing posts with label SPD. Show all posts

Sunday, July 18, 2010

Hide a List with SharePoint Designer 2010

With SharePoint Designer 2010 it is possible to hide a list.

Just select the list an enable hidden

clip_image001

If you want to hide a list please uncheck "Display this ilist on the Quick Launch" otherwise you can not hide the list

After saving this works realy fine. You also would not see the list in SharePoint Designer again.

You can if you know the URL browse to the list and work with this list, but you can not configure it in SharePoint Designer.

There is a way to make the hidden list available again.

Select in SharePoint Designer in "All Files"/Lists with a right click the hidden list.

clip_image002

Then choose Properties

Now you can change all settings in SharePoint Designer and also change the hidden attribute

clip_image003

Saturday, March 20, 2010

Workflows with Visio and SharePoint Designer

    Create a new Visio diagram

    clip_image001

    Choose Microsoft SharePoint Workflow

    clip_image002

    The following Actions are supported by Visio to design a workflow:

    clip_image003

    clip_image004

    After you designed the workflow do not forget to add an start and an end to the workflow

    clip_image005

    Export the workflow in the Visio Workflow Interchange format

    clip_image006

    Open SharePoint Designer and connect to the site collection where you want to enable the Visio workflow

    clip_image007

    Open up the workflow site objects and click on the button "Import from Visio"

    clip_image008

    Select the vmi file create and exported with Visio

    clip_image009

    After choosing the workflows file a wizard will be started

    clip_image010

    You can define the name for the workflow and choose the type

    • Bound to a list or library or
    • Reusable (all or specific content type)

    clip_image011

    SharePoint Designer is preparing the workflow configuration

    clip_image012

    The following pictures shows the workflow designed in Visio. You can now change the name (ID3) and all blue underline terms and configure the actions.

    clip_image013

    For example

    • increment a variable
    • copy the current item to the calendar list
    • replace contribute permissions of the current item to read permissions
    • the finally send a mail to the administrator

    clip_image014

    If there is a error in the workflow definition, you will get the following error message.

    clip_image015

    Save the xoml file to SharePoint.

    clip_image016

    After saving the workflow you can configure it with SharePoint Designer

    clip_image017

    And now we will test the workflow. First of all we need a element in the calendar list

    clip_image018

    And now we need to start the new workflow

    clip_image019

    Click on SharePoint Workflow

    clip_image020

    And click on Start

    clip_image021

    After starting we can have a look to the workflow history

    clip_image022

    Here we can see the SharePoint Designer/Visio workflow completed

    clip_image023

    In my environment if you want to see the workflow diagram i get a unexpected error.

    clip_image024

Saturday, February 6, 2010

Disable SharePoint Designer

Edit ONET.XML in Site Definition

<?xml version="1.0" encoding="utf-8"?>

<Project Title="$Resources:onet_TeamWebSite;" Revision="2" ListDir="$Resources:core,lists_Folder;" xmlns:ows="Microsoft SharePoint" DisableWebDesignFeatures="wdfopensite">

Add this Property

DisableWebDesignFeatures="wdfopensite"

Change WebPart Page - No Navigation, only Content

 

This is the complete web page

clip_image001

First create a "lite" master call blank.master

<%-- Identifies this page as a .master page written in Microsoft Visual C# and registers tag prefixes, namespaces, assemblies, and controls. --%>

<%@ Master language="C#" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<%@ Import Namespace="Microsoft.SharePoint" %>

<%@ Register Tagprefix="SPSWC" Namespace="Microsoft.SharePoint.Portal.WebControls" Assembly="Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Register Tagprefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Register Tagprefix="PublishingNavigation" Namespace="Microsoft.SharePoint.Publishing.Navigation" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/Welcome.ascx" %>

<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %>

<%@ Register TagPrefix="PublishingVariations" TagName="VariationsLabelMenu" src="~/_controltemplates/VariationsLabelMenu.ascx" %>

<%@ Register Tagprefix="PublishingConsole" TagName="Console" src="~/_controltemplates/PublishingConsole.ascx" %>

<%@ Register TagPrefix="PublishingSiteAction" TagName="SiteActionMenu" src="~/_controltemplates/PublishingActionMenu.ascx" %>

<%-- Uses the Microsoft Office namespace and schema. --%>

<html>

<SharePoint:RobotsMetaTag runat="server"/>

<%-- The head section includes a content placeholder for the page title and links to CSS and ECMAScript (JScript, JavaScript) files that run on the server. --%>

<head runat="server">

<asp:ContentPlaceHolder runat="server" id="head">

<title>

<asp:ContentPlaceHolder id="PlaceHolderPageTitle" runat="server" />

</title>

</asp:ContentPlaceHolder>

<Sharepoint:CssLink runat="server"/>

<asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server" />

</head>

<%-- When loading the body of the .master page, SharePoint Server 2007 also loads the SpBodyOnLoadWrapper class. This class handles .js calls for the master page. --%>

<body onload="javascript:_spBodyOnLoadWrapper();">

<%-- The SPWebPartManager manages all of the Web part controls, functionality, and events that occur on a Web page. --%>

<form runat="server" onsubmit="return _spFormOnSubmitWrapper();">

<WebPartPages:SPWebPartManager runat="server"/>

<PublishingSiteAction:SiteActionMenu runat="server"/>

<PublishingWebControls:AuthoringContainer id="authoringcontrols" runat="server">

<PublishingConsole:Console runat="server" />

</PublishingWebControls:AuthoringContainer>

<%-- The PlaceHolderMain content placeholder defines where to place the page content for all the content from the page layout. The page layout can overwrite any content placeholder from the master page. Example: The PlaceHolderLeftNavBar can overwrite the left navigation bar. --%>

<asp:ContentPlaceHolder id="PlaceHolderMain" runat="server" />

<asp:Panel visible="false" runat="server">

<%-- These ContentPlaceHolders ensure all default SharePoint Server pages render with this master page. If the system master page is set to any default master page, the only content placeholders required are those that are overridden by your page layouts. --%><asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server"/><asp:ContentPlaceHolder id="PlaceHolderTitleBreadcrumb" runat="server"/><asp:ContentPlaceHolder id="PlaceHolderPageTitleInTitleArea" runat="server"/><asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server"/><asp:ContentPlaceHolder ID="PlaceHolderPageImage" runat="server"/><asp:ContentPlaceHolder ID="PlaceHolderBodyLeftBorder" runat="server"/><asp:ContentPlaceHolder ID="PlaceHolderNavSpacer" runat="server"/><asp:ContentPlaceHolder ID="PlaceHolderTitleLeftBorder" runat="server"/><asp:ContentPlaceHolder ID="PlaceHolderTitleAreaSeparator" runat="server"/><asp:ContentPlaceHolder ID="PlaceHolderMiniConsole" runat="server"/><asp:ContentPlaceHolder id="PlaceHolderCalendarNavigator" runat ="server" /><asp:ContentPlaceHolder id="PlaceHolderLeftActions" runat ="server"/><asp:ContentPlaceHolder id="PlaceHolderPageDescription" runat ="server"/><asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat ="server"/><asp:ContentPlaceHolder id="PlaceHolderTitleAreaClass" runat ="server"/><asp:ContentPlaceHolder id="PlaceHolderBodyRightMargin" runat="server" /></asp:Panel>

</form>

</body>

</html>

Create a new file an call it blank.master with SharePoint Designer under

_catalogs/masterpage

clip_image002

Create a new webpart page and configure the webpart. This can be done afterwards also.

Open the webpart page in SharePoint Designer

In this example the page is called test.aspx

clip_image003

Change the master page reference for this page

clip_image004

And click on the preview window

clip_image005

Click on attach a master page

clip_image006

And select the master page blank.master

clip_image007

Click on OK

clip_image008

Click on Ok and save the modified webpart page

That's all

SharePoint Designer Workflows (German)

SharePoint Designer Workflows

clip_image001

clip_image002