Sharepoint designer 2007 installation guide

Configure SharePoint Server. Learn how to configure settings like services, authentication, and specific features after you install SharePoint Server. Install and manage apps for SharePoint Server. Upgrade to SharePoint Server Learn how to plan, prepare, and perform an upgrade to SharePoint Server Deploy software updates for SharePoint Server Learn how to prepare for, download, install, and configure software updates and patches for SharePoint Server Test and troubleshoot an upgrade to SharePoint Server SharePoint Server in Microsoft Azure.

Learn about why Microsoft Azure is the best place to host your SharePoint Server farms in the cloud. Install for SharePoint Learn about permissions, accounts, security settings, and what you have to do to prepare your environment for SharePoint Server Learn how to configure settings like services, authentication, and specific features after you install SharePoint Server Upgrade from SharePoint to SharePoint On the Installation Options tab, click the down arrow and select Not Available for these three sections:.

Click the down arrow for the Microsoft Office Document Imaging option, and then select Run all from my computer. Click Install Now , and then click Close. Click Start , and then select All Programs. On the Installation Options tab, click the down arrow and select Not Available for all sections. Note: No support is provided for side-by-side installations of bit and bit editions of Office. For more information about bit editions of Office , visit the following Microsoft web site: bit editions of Office Note: A repair of Office may need to be done after installing MODI when using Office media.

For more information on how to use Office with other versions of Office installed, click the following article number to view the article in the Microsoft Knowledge Base: Information about how to use Office suites and programs on a computer that is running another version of Office. If you cannot install MODI by using one of the methods that are provided in the "Resolution" section of this article, there are some alternative methods that you can use to regain some functionality that was provided by Microsoft Office Document Imaging.

The Microsoft Office Document Scanning component of MODI is used to scan documents and to make documents available on your computer by using any scanner that is installed. To scan documents, use the Windows Fax and Scan service. For more information about the Windows Fax and Scan service, visit the following Microsoft websites:.

Send a fax. Set up your computer to send and receive faxes Note If you use a third-party scanning software or a scanning software that is included with your scanning or printing device, you should contact your device manufacture for more information.

This driver enables you to save any Microsoft Office document in the. Currently, there is no viewer available from Microsoft to view. To open an. Use this action to calculate the time difference, in terms of minutes, hours or days, between two dates and stores the output in a variable.

Document Set Actions. Actions in this category are pertinent to a document set. A document set is a folder that stores multiple documents. In a workflow, a document set is treated as a single item. Note: To be able to use a document set in your library, you have to add the Document Set content type from your library settings page in your SharePoint site.

This action is initially displayed in workflow steps as Start Approval process for the contents of this Document Set with the users specified by this column. It starts an approval action on a document set to specific users. When you use this action, the status of the documents set and the documents that comprise the document set are changed, such as to Approved or Rejected.

If you used the Start Approval Process action on a document set, only the status of the document set would be changed. Start Bill of material approval process for the contents of this Document Set with the users specified by Variable: B ill of Materials Approvers.

This action is initially displayed in workflow steps as Capture a version of this Document Set that includes the type versions of the contents with comment: comment. It locks the version of the document set that has the version of documents —major or minor— that you specify in the action. Capture a version of this Document Set that includes the last major versions of the contents with comment: Last major version of the B ill of Material.

This action is initially displayed in workflow steps as Submit Document set using this action to this destination content organizer with this explanation Output to Variable: submit file result. It allows you to move or copy the document set to a document repository. A document repository can be a library in your SharePoint site, or a site on its own like the Document Center, that routes records to a specific destination based on rules that you define.

Note: To be able to define rules and route documents, you have to first enable the Content Organizer site feature in your SharePoint site. For more information, see the Configure the content organizer to route records topic in the See Also section. This action is initially displayed in workflow steps as Set content approval status for the contents of this Document Set to this status with comment.

Use this action to set content approval of a document set to Approved , Rejected , or Pending. Set content approval status for the contents of this Document Set to Approved with The bill of materials is approved.

Note: Content approval needs to be enabled in the list in order to be able to use this action. The following actions are used in approval scenarios. Pre-built actions are like sub-workflows, meaning that the workflow logic is already defined in the actions; all you need to do is supply the appropriate information. For information about when to use these workflows and when to use the actions, see the When should you use approval actions section of this article.

There is also the Start Custom Task Process. It has built-in logic, but unlike the previous two actions, does not come pre-built with what the workflow should be doing at each phase. Note: A category of actions called Task Behavior Actions appear in the actions list only when you customize the behavior of an approval action such as Assign Item for Approval or Assign Item for Feedback.

For more information on Task Behavior Actions , see the Actions available inside approval actions section of this article. This action is initially displayed in workflow steps as Start Approval process on Current Item with these users. It routes a document for approval. Approvers can approve or reject the document, reassign the approval task, or request changes. The Start Approval Process action behaves like a pre-built workflow—the logic is already defined in the action.

The action has several different phases built into it that defines task behaviors, task process behaviors, logging to the History Log, e-mail notifications, and completion conditions. Although the action comes with pre-built logic, it still needs information from you—such as the users the reviewers , the order in which the tasks are to be routed to the participants—serial or parallel, the default is serial, and the due dates for task completion. You can assign tasks to both internal and external participants in the action.

An external participant can be an employee in your organization who isn't a user in the site collection, or anyone outside your organization. This action is initially displayed in workflow steps as Start Feedback process on Current Item with these users.

Use this action to assign task items for feedback to users in a specific order—serial or parallel. The default is parallel. Users or task participants can also reassign a task to other users. When the users are done, they can click the Submit Feedback button to indicate task completion.

The Start Feedback Process action behaves like a pre-built workflow—the logic is already defined in the action. Although the approval action comes with pre-built logic, it still needs information from your end—such as the users the reviewers , the order in which the tasks are to be routed to the participants—serial or parallel, and the due dates for task completion.

This action is initially displayed in workflow steps as Start Task process on Current Item with these users. The Start Custom Task Process action is an approval process template that you can use if the above approval actions do not meet your needs.

The Start Custom Task Process also allows logic to be built inside of it, but unlike the other two approval actions, it does not come pre-built with what the workflow should be doing at each phase. You can specify your own actions and conditions in task behaviors or completion conditions. This action displays in a workflow steps as Declare this item as a record.

Use this action to identify a document as a record and apply the record restrictions settings you may have defined in the Record Declaration Settings page on your SharePoint site. You can define record declaration settings at the top-level site in your site collection. Record declaration settings specify restrictions that should apply after an item is declared as a record, user roles allowed to declare records and if record declaration is available to all site users.

This action displays in a workflow steps as Undeclare the item as a record Use this action to undo any record declaration settings that are applied to a record. Record declaration settings specify restrictions that should apply after an item is declared as a record, user roles allowed to declare records, and if record declaration is available to all site users.

Relational Actions. The action in this category enables you to use the relationship between a user and the user's manager. This action is initially displayed in workflow steps as Find Manager of this user output to Variable: manager. Use this action to look up a user's manager. The output value is then stored in a variable. Actions such as Start Approval Process and Start Feedback Process can be used in workflows to assign list items for approval or feedback.

These actions are pre-built, which means that much of the workflow logic is already defined in the action; you need to supply the appropriate information, such as the approvers or reviewers.

Note: If the above actions do not meet your needs, you can customize them in the browser, SharePoint Designer , and development environments compatible with SharePoint, such as Visual Studio. You can also customize the Start Custom Task Process action with the same tools.

This action is a template that you can use to define your own process for your organization. When you customize task behavior inside actions such as Start Approval Process and Start Feedback Process , a new category of actions titled Task Behavior Actions are available. Note: The actions available in the category vary depending on your context in a workflow. This action is initially displayed in workflow steps as End Task Process.

It ends the task process. The main workflow then continues to the next action. This action is initially displayed in workflow steps as Set content approval of item that the task process is running on to this status run as the workflow author. It allows you to set the approval status of the list item to Approved , Rejected , or Pending using the permissions of the workflow author, and not the workflow initiator.

This is commonly used if the person who starts an approval workflow may not have the permissions to approve a document. The list item is the item that the action is currently running on. This may or may not be the item the workflow is running on. Note: Content approval needs to be enabled in the list that the workflow is associated to. This action is displays in workflow steps as Wait for change in item that the task process is running on.

Use this action to make the workflow pause the task process until a value changes in the item that the approval process is currently running upon. This action is displays in workflow steps as Wait for deletion of item that the task process is running on. Use this action to make the workflow pause the task process until a value is deleted in the task item that the approval process is currently running upon. The following action appears only when you are customizing the Start Approval Process action, click changing the behavior of a single task , and then click inside the Before a Task is Assigned step.

This action is initially displayed in workflow steps as Set Task field to value. Use this action to set a field in the current task item to a value. It can be used on a task that has not been created yet. The following actions appear only when you are customizing the Start Approval Process action, click changing the behavior of a single task , and then click inside the When a Task is Pending or When a Task Expires.

This action is displayed in workflow steps as then Rescind this task. It completes the task without an outcome. This action is displayed in workflow steps as then Append a new task and assign to this user. A new task will be assigned to the user specified in the action, at the end of the current stage in the approval action.

This action is initially displayed in workflow steps as then Delegate this task to this user. The task assigned to the current user is rescinded and the task is then assigned to the new user, irrespective of whether it is a single user or a group. There are not variables to set for this action. The task is assigned to the manager of the user who is currently assigned the task. This action is initially displayed in workflow steps as then Forward this task to this user.

The task assigned to the current user is rescinded and the task is then assigned to the new user. If the new user is a group, and not a single user, then one task is created for each member in the group.

This is unlike the Delegate Task action where one task is created even if the user is a group. This action is initially displayed in workflow steps as then Insert a task assigned to this user. It inserts a new stage after the current stage in the approval process where the user specified in the action is the only participant.

This action is initially displayed in workflow steps as then Reassign this task to this user. Reassigns the task to another user. This action is initially displayed in workflow steps as then Request a change of this user. Use this action to request a change from a user and get a new task back to the current user when the change is completed.

This action is initially displayed in workflow steps as then Email these users. Use this action to include the Edit Task button in the email that is sent to the specific users.

Note: This action also appears when you click On Task Completed. Although both the task actions and the pre-built workflows can be used in collecting feedback and approval scenarios, the pre-built workflows provide a more sophisticated and complete solution. If the pre-built reusable workflows do not meet your needs, you customize them with SharePoint Designer If customizing a pre-built workflow to meet your needs will be more work that creating a new workflow, you can leverage the Start Approval Process and Start Feedback Process actions in your workflow.

If you want the structure that these actions provide, but not the functionality, you can use the Start Custom Task Process action. Task actions can be used in a scenario that does not necessarily have to adhere to a larger-scale approval process. For example, sending out reminders to employees to fill out timesheets.

P re-built Reusable W orkflows. Multiple users can be involved in multiple assignment stages. An assignment stage enables you to specify two things —if the task process should run in serial or parallel, and the users or task participants to whom the task will be assigned. Task actions do not have built-in logic. You have to use other actions and conditions to build out an approval or feedback mechanism. These are workflows equipped with in-built logic to give you a start-to-finish approval or feedback experience.

You can use the default logic or customize them to meet your needs. Collect data from a user is an action with an output clause—the data generated at a workflow's run time is stored in the variable in the output clause.

You have to then use this variable in the workflow in several different actions to build an approval or feedback scenario on your own. These workflows take advantage of data sources, making it easier to customize a workflow to meet your needs.