The workflows included with SharePoint products are features that you can use to automate your business processes, making them both more consistent and more efficient. You can use a SharePoint Collect Signatures workflow to route documents created in Excel, Word, or InfoPath to one or more people for their signatures. Show
Note: SharePoint 2010 workflows have been retired since August 1, 2020 for new tenants and removed from existing tenants on November 1, 2020. If you’re using SharePoint 2010 workflows, we recommend migrating to Power Automate or other supported solutions. For more info, see SharePoint 2010 workflow retirement. For more info, see Overview of workflows included with SharePoint. Important: By default, the Collect Signatures workflow is not activated and is not listed in the Select a workflow template list box of the association form. To make it available for use, a site administrator must activate them at the site collection level. If you have Site collection level permissions, see Enable SharePoint workflow templates. If all you need to do is complete a Collect Signatures workflow task Just go to the COMPLETE segment and expand it. You might not need any of the other segments for now.
SharePoint workflows are:
Here’s a diagram of a very simple version of the Collect Signatures workflow.
Tips for using this articleThe information in this article is presented in expandable segments. If all you need to do is complete a Collect Signatures workflow task Just go to the COMPLETE segment and expand it. You might not need any of the other segments for now. If you want to add, start, monitor, and maintain workflows If you aren’t already familiar with these tasks, you might find it useful to work your way through this article, segment by segment, the first time that you design and add a workflow. Once you’re familiar with the information and the article layout, you’ll be able to go straight to the segment you need on any return visits. A note on the graphics Screen images and conceptual diagrams in this series of workflow articles are generally based on the Approval workflow type. Wherever necessary for conceptual or instructional clarity, however, images and diagrams in this article have been customized for Collect Signatures workflows. A word about printing this article This is a long article. If you want to print only selected segments, make sure that only those segments are expanded when you print. (Also, if you want to include the complete graphics in your printed copy, print in landscape orientation and not portrait orientation.) And a word about searching Before you search for any text or term in this article, make sure that all of the segments in which you want to search are expanded. Learn more about Collect Signatures workflowsA Collect Signatures workflow is a SharePoint products feature that routes a document or form created in Word, Excel, or InfoPath to one or more people for their signature. The workflow automates, streamlines, and standardizes the whole process.
The basic Collect Signatures workflow that’s included with SharePoint products functions as a template. Using this template, you can add one or more Collect Signatures workflows to your sites. Each workflow that you add is a unique version of the basic Collect Signatures workflow, each with its own specialized way of working, based on the settings that you specify when you add it.
The Collect Signatures workflow isn’t designed to collect approvals and rejections for a document, or to control webpage publishing for a website. If you want to add a workflow in which participants approve or reject the document that they review, see the article, All about Approval workflows. Also, Collect Signatures workflows aren’t designed to collect feedback. If you want to use a workflow to collect feedback about a document, see the article, All about Collect Feedback workflows. You can also use Microsoft SharePoint Designer 2013 to further customize any of the workflows included with SharePoint products. To add a workflow By default, you must have the Manage Lists permission to add a workflow. (The Owners group has the Manage Lists permission by default; the Members group and the Visitors group do not.) To start a workflow Also by default, you must have the Edit Items permission to start a workflow that’s already been added. (The Members group and the Owners group both have the Edit Items permission by default; the Visitors group does not.) Alternatively, Owners can choose to configure specific workflows so that they can be started only by members of the Owners group. (To do this, select the Require Manage Lists Permissions to start this workflow check box, on the first page of the association form.) More and more business transactions are being conducted electronically. Consequently, digital signatures are being used increasingly to legally bind relying parties to their transactions. A digital signature is used to verify the identity of the person who signed the document, and confirms that the content was not modified after the digital signature was applied to the document. Digital signatures provide security that is based in encryption technologies, and help mitigate risk associated with electronic business transactions. With improvements to digital signing, Office aims to meet the information security needs of enterprises and public sector entities worldwide. To create a digital signature, you must have a digital certificate, which proves your identity to relying parties, and which should be obtained from a reputable certificate authority (CA). If you do not have a digital certificate, Microsoft also has partners that provide digital certificates as well as other advanced signatures. These are the basic stages:
The following flow chart illustrates these stages from the perspective of the person who is adding a new workflow.
Plan a new Collect Signatures workflowIn this segment, we identify the decisions you need to make and the information you need to assemble before you add a version of the Collect Signatures workflow. If you’re already familiar with how to add this type of workflow and only need a reminder about the specific steps, you can go straight to the appropriate ADD segment (List/library or Site collection) of this article. The workflows included with SharePoint products function as master templates on which the specific, individual workflows that you add to your lists, libraries, and site collection are based. Each time that you add a Collect Signatures workflow, for example, you’re actually adding a version of the general Collect Signatures workflow template. You give each version its own name and its own settings, which you specify in the association form when you add that particular version. That way, you can add multiple workflows, each one a version based on the Collect Signatures workflow master template, but each version named and tailored for the specific way that you will use it. In this illustration, three workflows based on the Approval workflow template have been added — one for all content types in a single library, one for a single content type in a single library, and one for a single content type in a whole site collection.
Whenever you add a new workflow version based on one of the included workflow templates, you fill out an association form to specify the way that you want your new version to work. In the following section, you’ll find a list of questions that will prepare you to complete the association form. First, though, take a moment or two to look over the form and its fields. First page of the association form
Second page of the association form
The fields on this second page also appear on the initiation form, which is presented each time that the workflow is started manually, and can be edited at that time for that single run only. Nine questions to answerAs soon as you have the answers to all of the questions in this section, you’re ready to add your workflow. This article concerns the workflow template that appears in the menu as Collect Signatures – SharePoint 2010. If you’re not sure that this workflow type is the best choice for you, refer back to the LEARN segment of this article. For further information about the other workflow templates that are available, see the article, About the workflows included with SharePoint. It’s important to know that signature lines of the type we’re discussing here can be inserted only in documents created in Word, Excel, or InfoPath. What’s a content type? Each document or other item stored in a SharePoint list or library belongs to one or another content type. A content type can be as basic and generic as Document or Excel Spreadsheet, or as highly specialized as Legal Contract or Product Design Specification. Some content types are available in SharePoint products by default, but you can both customize these and add others that you create yourself. You can make your new version of the Collect Signatures workflow available in a single list or library only, or you can make it available throughout the entire site collection.
Give your workflow version a name that:
An example Imagine that you’re a member of a group of editors. Your group wants to use two different Collect Feedback workflows:
You might name the first workflow Inside Submission Feedback and the second one Outside Submission Feedback. Tip: As usual, it’s a good idea to establish consistent naming conventions, and to make sure that everyone involved with your workflows is familiar with those conventions. You can have your workflow use the site’s default Tasks list and History list, use other existing lists, or request new lists just for this workflow.
Signature lines can be inserted in the document at either of two times:
Adding a digital signature to a document is a two-step process:
Keep this in mind From the moment that the first participant adds their signature to the document, the document is locked against editing. Any further change to the document after that point — except other signers adding their signatures — invalidates or deletes all signatures that have been added. And because the insertion of a signature line counts as a change in the document, all signature lines must already be present in the document before the first participant adds their actual signature to one of those lines. So, there are three simple ways to answer this question:
Here’s a rapid graphic summary of the main point.
A workflow can be set up to be started manually only, automatically only, or either way:
The following illustration shows the difference between manual starts and automatic starts.
Any changes that you make in the initiation form are applied only during the current instance of the workflow. To change the permanent, default settings of the workflow, you edit the original association form, as explained in the CHANGE segment of this article. Manual starts If you allow manual starts, anybody who has the necessary permissions can start the workflow on any eligible document at any time. The advantages of a manual start are that you and your colleagues can run the workflow only when and if you choose to, and that each time you run it you’ll have the chance to change some settings by using the initiation form. Of course, with a manual start somebody has to remember to run the workflow whenever it’s appropriate to do so. Automatic starts You can set up the workflow to be started automatically by either or each of the following events:
The advantage of an automatic start is that no one has to remember to start the workflow. It runs every time a triggering event occurs. Special considerations for automatic starts with Collect Signatures workflows Unlike in some of the other included workflows, it isn’t possible to add more tasks after a Collect Signatures workflow has started. When the workflow starts automatically, it assigns only those signature tasks already specified in its default settings. Each of those tasks can indeed be reassigned during the workflow run, but no additional tasks can be created and assigned. In other words, a Collect Signatures workflow should only run automatically when the identity, or at least the number, of participants is known beforehand. What is possible after an automatic start is to delete or cancel tasks that are already assigned — but note that canceling a task will not remove the associated signature line from the document. Following are three scenarios in which an automatic start is used. Notice that in each scenario:
Of course, in each of these scenarios, if the item that is uploaded is a document or form that already contains the appropriate signature lines, there is no need for the workflow participants to insert signature lines during the workflow run. Scenario 1: Single task, single signer New expense claims need to be signed by Anna, so Anna creates a library named New Expense Claims. Anybody in the organization can create or upload a claim. Anna creates a workflow and gives it the same name: New Expense Claims. The workflow runs automatically on each new document, assigning only one signature task — to Anna, of course.
Scenario 2: Multiple tasks, multiple signers This time, contracts need to be signed by Anna and Sean and Frank — by all three of them. Sean creates a library named Contracts for Signatures. She creates a Collect Signatures workflow named Signatures (annaANDseanANDfrank). The workflow runs automatically on each new document, assigning one signature task to each of the three people. The first signer to open the document inserts the signature lines for all three signers before adding their own signature.
Scenario 3: Multiple tasks, single signer In this version, contracts need to be signed by Anna or Sean or Frank — by only one of the three. Sean creates a library named Contracts for Signature and a workflow named Signature (annaORseanORfrank). She also creates a mailing list or distribution group, also named annaORseanORfrank, which includes all three of them. Again the workflow runs automatically on each new document in the library, but this time it assigns only one signature task, to the annaORseanORfrank group. This sort of task is called a group task, and it works like this: The workflow sends an email task notification to each member of the group, but creates only a single task, which any individual member of the group can claim and complete on behalf of the whole group.
For instructions on claiming and completing a group task, see the COMPLETE segment of this article. When you add a workflow to a content type for the entire site collection, you’re given the option of also adding the workflow to all other content types in the site collection that inherit from the content type you’re adding the workflow to. (Note that if you’re adding a workflow for a single list or library only, this option won’t appear.) Notes:
You’ll need to supply the name or email address for each person to whom a signature task will be assigned. Group tasks or individual? If you assign a task to a group or distribution list, a group task will be assigned: Each member of the group will receive a task notification, but only one member will need to claim and complete the task. For instructions on claiming and completing a group task, see the COMPLETE segment of this article. One stage or multiple stages? You can choose to have only one stage of signature tasks, or to have multiple stages. If you have more than one stage, the stages will be performed one after another. Parallel reviews or serial reviews? For the participants in any one stage, you can choose either to have their signature tasks assigned all at the same time (in parallel) or to have their tasks assigned one after another (in serial) in the order that you indicate. The serial option can be useful if, for example, one of the signers is the real decision-maker concerning the document and it doesn’t make sense for any of the other signers to complete their signature tasks if the decision-maker decides not to sign. An example This simple scenario illustrates a few of the advantages of both multiple stages and serial task assignments: Imagine that Frank is adding a new Collect Signatures workflow for a contracts library. Because Frank is the real decision-maker, he wants to be the first person to sign each contract. If he decides not to sign, neither Anna nor Sean will be assigned a signature task. Frank can set this up in either of two ways:
Here are diagrams of both solutions. In both versions, if Frank does not complete his signature task, tasks are never assigned to either Anna or Sean.
In the CC field, on the second page of the association form, you can enter names or addresses for anyone who should be notified each time that this workflow starts or ends.
Add a Collect Signatures workflow (for only one list or library)If you’re not yet familiar with adding workflows, you might find it useful to review the preceding LEARN and PLAN segments in this article before you proceed with the steps in this segment. Two matters need to be in order before you can add a workflow: Email In order for the workflow to send email notifications, email must be enabled for your SharePoint site. If you’re not sure that this has already been done, check with your SharePoint administrator. Permissions The SharePoint products default settings require that you have the Manage Lists permission to add workflows for lists, libraries, or site collections. (The Owners group has the Manage Lists permission by default; the Members group and the Visitors group do not. For more information about permissions, see the LEARN segment of this article.) Follow these steps:
SharePoint products creates your new workflow version. What’s next? If you’re ready to start and test your new workflow, go to the START segment of this article. You’ll find instructions for inserting signature lines into a document in the INSERT segment of this article. Add a Collect Signatures workflow (for a whole site collection)If you’re not yet familiar with adding workflows, you might find it useful to review the LEARN and PLAN segments in this article before you proceed with the steps in this segment. Two matters need to be in order before you can add a workflow: Email In order for the workflow to send email notifications, email must be enabled for your site. If you’re not sure that this has already been done, check with your SharePoint administrator. Permissions The SharePoint products default settings require that you have the Manage Lists permission to add workflows for lists, libraries, or site collections. (The Owners group has the Manage Lists permission by default; the Members group and the Visitors group do not. For more information about permissions, see the LEARN segment of this article.) Follow these steps:
SharePoint products creates your new workflow version. What’s next? If you’re ready to start and test your new workflow, go to the START segment of this article. You’ll find instructions for inserting signature lines into a document in the INSERT segment of this article. Insert signature linesBefore a workflow participant can add their signature, a signature line must be inserted in the document. The inserting of the line and the adding of the signature itself are two separate actions. It’s important to remember that:
Here’s a rapid graphic summary of all of that.
To insert a signature line in Word or Excel:
Repeat the same procedure to add more signature lines. To delete a signature line in Word or Excel:
Important: Signature lines can be inserted only in InfoPath Filler forms. To insert a signature line in InfoPath:
To delete a signature line in InfoPath:
What’s next? If you’re ready to test your new workflow, go to the START segment of this article. If you’re completing a workflow task, go (or return) to the COMPLETE segment of this article. Start a Collect Signatures workflowA reminder about the signatures process: All changes must be made to the document — including all insertions and deletions of signature lines — before the first participant adds their signature to a signature line. (For more details, see the PLAN segment in this article.) Also, make sure that the people to whom the workflow will be assigning tasks understand how to add their signatures and complete their task forms. They might find the COMPLETE segment in this article useful. Two ways to start a workflow A workflow can be set up to be started manually only, automatically only, or either way:
A workflow can’t start on any document that is currently checked out. (A document can be checked out after a workflow has been started on it; but after it’s checked out, no further workflows can be started on that document until it’s checked back in again.) If the workflow is configured to start automatically, then each time a triggering event occurs, the workflow runs on the document that triggered it. When it starts, the workflow assigns the first task or tasks and sends a task notification to each assignee. Meanwhile, it also sends start notifications (distinct from task notifications) to the person who originally added the workflow and to anyone listed in the CC field of the second page of the association form. If the necessary signature lines are not already present in the document before the triggering action starts the workflow, then they must be inserted before the first signature is added to the document. A note on permissions Ordinarily, you must have the Edit Items permission to start a workflow. (By default, the Members group and the Owners group both have this permission, but the Visitors group does not. However, an Owner can also choose, on a workflow-by-workflow basis, to require the Manage Lists permission for people who start the workflow. By choosing this option, Owners can essentially specify that only they and other Owners can start a particular workflow. For more details, see the Learn segment of this article.) Two places to start from You can start a workflow manually from either of two places:
The remaining two sections in this segment provide instructions for both methods.
The workflow assigns the first task or tasks, and meanwhile sends start notifications to you and to anyone listed in the CC field of the initiation form.
The workflow assigns the first task or tasks, and meanwhile sends start notifications to you and to anyone listed in the CC field of the initiation form. What’s next?
Complete a Collect Signatures workflow taskIf this is the first time that you’ve been assigned a task in a Collect Signatures workflow, you might find it useful to review this segment of the article in full before you complete your task. That way, you’ll be aware of all of the options that may be open to you. Note: If you know that a workflow task has been assigned to you, but the notification message hasn’t appeared in your email Inbox, make sure that the notification hasn’t been misrouted by your junk email filter. If it has, adjust the settings of your filter accordingly. First, make sure you’ve got the right article Different types of workflows require different task actions. So before you begin, make sure that the task you’ve been assigned is indeed a Collect Signatures workflow task, and not a task for some other type of workflow. Look for the text This document requires your signature in any of the following locations:
If you don’t see the This document requires your signature text in these locations, check with the person who started or originally added the workflow to find out which workflow template it’s based on — or whether it’s a custom workflow. If your task is a Collect Signatures task, however, keep right on reading! When you’re assigned a task in a workflow, you usually find out about the task in one of three ways:
When you find out that you’ve been assigned a Collect Signatures workflow task, you usually do two things:
Often, therefore, the following three items are involved in your completion of the task:
Here’s what those three items look like. Note: The Open this Task button on the ribbon in the task notification message appears only when the message is opened in the full, installed version of Outlook, and not when it’s opened in the Outlook Web Access web application.
Note: The Open this Task button on the Ribbon in the task notification message appears only when the message is opened in the full, installed version of Outlook, and not when it’s opened in the Outlook Web Access web application. (Note that if the task is not assigned to you personally, but to a whole group or distribution list of which you are a member, then you should claim the task before completing it. For more information, see the Claim a group task before you complete it section in this segment.) Follow these steps:
Note: The Open this Task button on the ribbon in the task notification message (shown in the illustration at the top of the black arrow) appears only when the message is opened in the full, installed version of Outlook, and not when it’s opened in the Outlook Web Access web application. (Note that if the task is not assigned to you personally, but to a whole group or distribution list of which you are a member, then you should claim the task before completing it. For more information, see the Claim a group task before you complete it section in this segment.) Follow these steps:
Note that if the task is not assigned to you personally, but to a whole group or distribution list of which you are a member, then you should claim the task before completing it. For more information, see the Claim a group task before you complete it section in this segment. Also be aware that if the signature line is set up for a specific user, and you sign it while logged on as a different user, the discrepancy might be visible in the signature line. In this example, the signature line was set up for Frank Martinez, but the signature was added by someone logged in as Anna Lidman.
In the following example, the document was created in Word.
Notice the three yellow message bars at the top of the document: Marked as Final This message bar tells you that at least one person has already added their signature on a signature line. Important: From that point forward, any change in the document other than the adding of signatures to already-present signature lines results in the removal or invalidation of all signatures already added. (That is, the insertion or deletion of signature lines is not allowed at this point, only the addition of the signatures themselves.) Signatures You can click the View Signatures button to open the Signatures pane. Under Requested Signatures, click the arrow next to your name and then, on the drop-down menu, click Sign. Notes:
If you see a message about third-party digital signature service providers, click OK to continue. (To avoid seeing the message in the future, select the check box.) The Sign dialog box opens.
To sign the document, just type your name in the box next to the big X, click Sign, and then click OK in the Signature Confirmation dialog box. Remember: If your name appears more than once in the Requested Signatures list, then there’s more than one signature line for you to add your signature to. Use this same procedure to add each signature. Workflow Task When you’re ready to complete and submit the task form, click the Open this task button in the Workflow Task message bar. The task form for a Collect Signatures workflow task looks something like this.
Note that the first two controls (Delete Item and This workflow task applies to Document Title) don’t appear in the task form when it’s opened from inside the document to be signed. They appear only when the task form is opened directly from either the task notification message or the Task list on the Workflow Status page.
If only a single task is assigned to an entire group that you belong to, then any member of the group can claim and complete that single task on behalf of the whole group. Claim the task before you open and sign the document. As soon as you claim the task, it’s assigned to you, and no other member of the group can complete it. (This way, only one person does the necessary work.)
When the Workflow Status page is refreshed, you can see that the task is no longer assigned to the group, but now specifically to you. Later, if you want to release the task to the group again without completing it, use the same steps to return to the task form, but now click the Release Task button.
If you want someone else to complete a workflow task that has been assigned to you, click the Reassign Task button in the workflow task form. This form is displayed.
When the form is complete, click Send. Your task is marked Completed, a new task is assigned to the person now responsible for the task, and a task notification is sent. Any new information that you supplied is included in the Delegated by text in the new task notification (number 1 in the following illustration).
Meanwhile, all of these changes are tracked and visible in the Tasks and History sections of the Workflow Status page, as shown here.
Monitor, adjust, or stop a running Collect Signatures workflowThe central location from which you can monitor, adjust, or stop a running workflow is the Workflow Status page for that instance of the workflow. First we’ll show you how to get to that page, then we’ll show you how to use the options and information that you find there. Finally, we’ll show you two other pages where you can get additional monitoring information. In the list or library where the item is located, click the In Progress link for the item and workflow that you want. In this example, the item is the document named Keynote Draft and the workflow is Approval 3.
The Workflow Status page opens.
Here, under the illustration of each section of the Workflow Status page, you’ll find the monitoring questions that the section answers. Workflow Information section
Questions answered:
Tasks section
Questions answered:
Tasks that have been deleted and tasks that haven’t yet been assigned don’t appear in this section. Workflow History section
Questions answered:
There are two ways that you can stop a running workflow instance before its normal completion:
Instructions for both methods follow. Cancel (all tasks canceled but retained in both Tasks list and History) If the current instance of a workflow is no longer needed, it can be canceled. By default, this procedure can be performed by the person who started this instance of the workflow or by anyone who has the Manage Lists permission. (Again, the Owners group has the Manage Lists permission by default; the Members group and the Visitors group do not.)
All current tasks are canceled, and the workflow ends with a status of Canceled. The canceled tasks are still listed both in the Tasks area and in the Workflow History area. End (all tasks deleted from Tasks list but retained in History) If an error occurs, or if the workflow stops and fails to respond, it can be ended. By default, this procedure can be performed only by someone who has the Manage Lists permission. (Again, the Owners group has the Manage Lists permission by default; the Members group and the Visitors group do not.)
All tasks created by the workflow are canceled and are deleted from the Tasks area on the Workflow Status page, though they’re still reflected in the Workflow History area. The workflow ends with a status of Canceled. On the Workflows page for any item, you’ll find a list of the workflows currently running on that item.
Note: Note that multiple instances of a single workflow version cannot run on the same item at the same time. For example: Two workflows, both based on the Collect Signatures template, have been added. One is named Plan Feedback and the other is named Budget Feedback. On any one item at any one time, one instance each of Plan Feedback and Budget Feedback can be running, but not two instances of either workflow. Site collection administrators can view at a glance:
Here’s how:
The Workflows page opens, displaying the information. What’s next? If this is the first time that this workflow version has run, you might want to use the instructions in the REVIEW segment of this article to view the events in the instance and discover whether the workflow functions as you want it to. Review Collect Signatures workflow results and create reportsAfter your workflow instance has completed, you can review the events recorded in its history. (You can access the record for any instance for up to 60 days after the instance completes.) Important: Note that the workflow history is provided for informal reference only. It cannot be used for official audits or for any other legal, evidentiary purpose. You can also run reports about the overall performance of the workflow across instances. As long as an item remains in the same list or library, and until the same workflow is run again on that same item, the history of the most recent instance can be accessed from the list or library. To view the Workflow Status page for the most recent instance of a workflow run on any item:
In this example, the item is the document titled Keynote draft and the workflow is New Doc Approval.
On the Workflow Status page, the Workflow History section is located near the bottom.
What if you want to review the history of an instance after you’ve run the same workflow again on the same item? In fact, you can do so for up to 60 days, from either of two entry points: the list or library, or the workflow completion notification. (Sixty days is how long SharePoint products retains task history for workflows.) From the list or library
From the workflow completion notification
The Workflow Status page for that instance opens. In order to retain all of your completion notifications, you might want to create an Outlook rule. Set up the rule to copy all incoming messages that have the text has completed on in the Subject line into their own, separate folder. (Make sure that your Outlook rule copies the incoming messages and doesn’t simply move them, or they won’t also appear in your Inbox.) To learn how one of your workflow versions is performing generally — over time and over multiple instances — you can create either or both of two predefined reports:
Create the available reports for a workflow
What’s next? If your workflow functions just the way you want it to, you’re all set to start using it. If there’s anything you want to change about how it works, see the CHANGE segment of this article. Create workflow performance reports To learn how one of your workflow versions is performing generally — over time and over multiple instances — you can create either or both of two predefined reports:
Create the available reports for a workflow
What’s next? If your workflow functions just the way you want it to, you’re all set to start using it. If there’s anything you want to change about how it works, see the CHANGE segment of this article. Change, disable, or remove a Collect Signatures workflowAfter you run the first instance of your new Collect Signatures workflow and review the results, you might want to make one or more changes to the way the workflow is configured. Also, you might at various times in the future want to make further changes to the configuration. Finally, you might at some point wish to disable the workflow for a shorter or longer period, but not remove it — or you might, indeed, choose to remove it entirely. To make permanent changes to the settings for an existing workflow, you open and edit the association form that was originally used to add it. If the workflow runs in only one list or library
If the workflow runs in all lists and libraries in the site collection
On the Site Settings page, under Galleries, click Site Content Types.
If the workflow runs in only one list or library
There are five columns in the form:
What’s next? If you’ve made any changes, run a test instance of the workflow to double-check the effects of the changes.
There are a wide variety of ways to further customize the workflows included with SharePoint products. You can even create custom workflows from scratch. You can use any or all of the following programs:
For more information, see the Microsoft Software Developer Network (MSDN) Help system. What is a business requirement quizlet?business requirements. the specific business requests the system must meet to be successful. requirements management. the process of managing changes to the business requirements throughout the project.
What is a formal approved document that manages and controls the entire project?Project Plan. a formal, approved document that manages and controls the entire project.
Which phase of the SDLC gathers business requirements?Which phase of the SDLC gathers business requirements? Project goals and business requirements are gathered and turned into precise functions in the analysis phase.
What modify software to meet specific user or business requirements?DAC1. modifies software to meet specific user or business requirements. supports general business processes and does not require any specific software customization to meet the organization's needs.
|