UPDATE: Sjá þessa MSDN umræðu, sérstaklega síðustu færslu: http://forums.microsoft.com/MSDN/showpost.aspx?postid=2631057&siteid=1. It describes a condition that may short circuit this whole thing. In short, það getur verið eins einfalt og að minnsta kosti eitt af þeim sviðum sem nauðsynlegur.

Ég er með skjal bókasafn sem styður átta tegundir efnis.

I have a SharePoint Designer workflow that wants to calculate and assign a "reminder date" með því einfaldlega að draga 30 dagar frá öðrum dálki, "due date". This should only happen for one of the content types, "Insurance". The business objective is to produce a KPI that shows two categories of insurance documents: "about to expire" and "expired." (Þú getur lesið meira um þessa tegund af KPI og umfangsmeiri bora niður hér).

I have configured the workflow to fire when a new item is created and when an item is modified. The idea is that when an insurance document is uploaded, we calculate a "warning date" based on the expiration date. A pair of views work in connection with a KPI List to highlight these conditions when users hit their home page.

Þessi stefna virkar ekki þegar ég hlaða skjal.

I upload the document and I am presented with the meta data entry screen. Á þessum tímapunkti, I’m already in trouble. SharePoint has already, snemma frá sjónarhóli mínum, fired the workflow. I haven’t had a chance to pick the correct content type nor assign a due date. Á sama tíma, the workflow does not fire when I hit the submit button at this time. There’s some built-in logic that "believes" that first submit is part of the "create" event. Svo … workflow minn hefur rekinn og þegar hann framkvæma, it was passed default meta data values.

The best work-around I know of is to insert a "pause until" activity in the workflow. I have the workflow pause for 1 minute. While it’s pausing, Ég velja rétta gerð efnis, enter the meta data and submit. The pause completes and the workflow proceeds as needed. (Athugið að í umhverfi mínu, timer workflow activities from SPD do not work out of the box. You may have the same trouble. Sjá hér fyrir frekari upplýsingar).

I don’t like "magic delay" work-around. What happens if the user uploads a document and the phone rings and the ensuing conversation outlasts the pause? I can make the pause longer, en ég samt líkar það ekki.

Ég skrifaði um þetta á MSDN málþing hér: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2430725&SiteID=1

Einu sinni eða tvisvar mánuði, einhver innlegg vettvangur spurning: "Hvernig bæti ég tengla á URL sem eru smella af SharePoint Designer tölvupósti?"

Kynnt án frekari athugasemda: (vel, raun það er frekar athugasemd eftir myndina):

Becky Isserman fylgir með gagnlegar skýringar á hvernig á að embed in tengil á hlut í tölvupósti: http://www.sharepointblogs.com/mosslover/archive/2007/11/20/addition-to-paul-galvin-s-post-about-sending-an-e-mail-with-hyperlinks-in-spd.aspx

Atburðarás: I have an InfoPath form that front-ends a workflow process implemented using SharePoint Designer. At one point, a manager must approve the form. Since I cannot count on workflow history to meet my auditing requirements, Ég ákveð að geyma eigin endurskoðun skilaboð minn beint á formi sjálft.

Yfirlit:

Design the form and publish it as a efnisgerð and the form itself to a document library. Mark desired form fields as being updateable from MOSS. The form is tied to the content type and the content type is "attached" to a forms library (or many, if you want). Write a workflow that updates the field.

Specific Steps:

1. Create a document library. This will hold your InfoPath template.
2. Create a forms library.
3. Create the InfoPath form. Include a text field, "Audit Message".
4. Publish the form as a content type (NOT a document).
5. While filling out the publishing dialogs:
   a) Save the .xsn file to the document library (stíga #1).
   B) Publish the "Audit Message" field and mark true: "Allow users to edit data in this field by using a datasheet or properties page".
   c) Create a new content type and give it an appropriate name.
6. Access the forms library.
   a) Go to its advanced settings and enable the forms library to manage content types.
   B) Select the newly created content type (5c above). It will be grouped under "Microsoft InfoPath" (or similar).
   c) Remove the default "Form" content type from the library.
   d) Mark the library to "show as web page" so that the form will launch from SharePoint and not the InfoPath workstation client.
7. Go back to the forms library proper and click "New" to simply verify that the form is posted correctly and acting as you want.
8. Fire up SharePoint Designer and navigate to the site that hosts your form library (from step 2).
9. Create a new workflow attached to the forms library.
10. Add a single action "Set Field in Current Item". You should expect SharePoint Designer to list your your field, "Audit Message". Assign it a value.
11. Click Finish and go back to the form library.
12. Create a new form and put some test value into the "Audit Message" sviði.
13. Save it and go back to the form library.
14. Right-click, select "Workflow" and start up your workflow.
15. It should run almost immediately. Pull up the form (from step 12) and if all has gone to plan, "Audit Message" has been assigned whatever value you provided in step 10.

Skýringar:

Not all controls may configured for this bi-directional communication. Til dæmis, it does not seem to implement an SPD workflow that modifies text fields wrapped inside repeating sections.

One of the key take-away’s here is that we’ve really created a content type with an associated template. This also enables us to store multiple InfoPath form templates in the same form library.

This requires forms server. It’s most certainly not going to work in a WSS 3.0 environment and probably even requires an Enterprise SharePoint environment.

UPDATE: Þetta hefur verið gefið út til Codeplex hér: http://www.codeplex.com/spdwfextensions

UPDATE: Sjá hér fyrir nýjustu útgáfuna: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!381.entry

UPDATE: Sjá hér fyrir hugsunum mínum á commercializing þetta verkefni: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!569.entry

This project provides a custom activity in SharePoint Designer. Use this custom activity to invoke (senda) any C# function that you incorporated into the linked assembly.

Eins lok október, 2007, this is just an initial version of the project. I plan to expand it with a number of additional functions, including substring, Vísitala, replace, invoking web services and anything that seems useful or interesting. I also plan to post this to codeplex once I have my act together on that front. This will also be deployable as a solution at some point.

If you have any comments, spurningar eða ábendingar, vinsamlegast láta þá í athugasemdir eða sendu mér tölvupóst.

Fyrirvari:

I make absolutely no claims as to the suitability of this for any purpose. Use at your own risk.

Uppsetningu skref (að fylgja fyrir hvern WFE í bænum):

1. Sæktu. Zip og þykkni.

2. Install the .dll into the GAC. I usually open c:\Windows samkoma að nota Windows Explorer og afrita það þar.

3. Breyta web.config að bæta samkoma á örugga eftirlit:

<System.Workflow.ComponentModel.WorkflowCompiler>
<authorizedTypes>

<authorizedType Assembly="SpdGenericInterface, Útgáfa = 1.0.0.0, Menning = hlutlaus, PublicKeyToken = abe076fd8125f3c4" Namespace="Nivlag" TypeName="*" Authorized="True" />

4. Copy "SpdGenericInterface.actions" til C:\Program Files Common Files Microsoft Shared vefur framreiðslumaður eftirnafn 12 SNIÐMÁT 1033 Workflow

Athugaðu að ofan staðsetning er sérstaklega ensku innsetningar tungumál.

5. Close SharePoint Designer (if it’s already open).

6. iisreset

7. Open SPD and create a new workflow.

If all goes well, you should be rewarded with a new category of action:

Skýringar:

Sjá hér (http://blogs.msdn.com/sharepointdesigner/archive/2007/03/15/adding-activities-to-spd.aspx) for a terrific overview of the process for creating, installing and configuring a solution like this.

The .zip is designed to extract directly to you c:\ drive. If you do this, you can open the project and all the paths will be consistent.

To use this in visual studio, you probably need to install "Extensions for Windows WF".

The initial upload contains just one "dispatcher function", "ToLower()". To add more functionality, add it to the Execute method as shown:

 vernda forgang ActivityExecutionStatus
          Execute(ActivityExecutionContext executionContext)
        {

            band functionToDispatch;
            functionToDispatch = þetta.DispatchFunction.ToLower();

            switch (functionToDispatch)
            {
                case "tolower()":
                    {
                        þetta.OutResult1 = þetta.InParam1.ToLower();
                        break;
                    }

                default:
                    {
                        þetta.OutResult1 = "Unknown function: [" + þetta.DispatchFunction + "].";
                        break;
                    }
            }

            aftur ActivityExecutionStatus.Closed;
        } // ActivityExecutionStatus

    }

Þá, re-build the project and copy the assembly to the GAC. I expect an iisreset would be required.

Part of the process for creating a custom action for SharePoint Designer involves create a ".actions" skrá.

Ég hef fundið og reynt að nota sýnishorn sniðmát sem byrjar sem:

<?XML útgáfa="1.0" Kóðun="UTF-8" ?>
<WorkflowInfo xmlns="HTTP://schemas.microsoft.com / SharePoint /">
<Actions Sequential="þá" Parallel="og">

Hins, that xmlns attribute prevents my environment from working. My actions don’t show up in SPD.

The solution is to strip out the xmlns attribute, do an iisreset and close/re-open SPD.

Use the "Collect Data from User" action to create and assign a task to a user that prompts them for data. Among other things, Ég hef notað það til að hvetja notandann til að samþykkja eða hafna beiðni og slá nokkrar athugasemdir.

Þessi aðgerð tekur mynd af:

Safna gögn frá Þessi notandi (Framleiðsla til Variable: collect1)

Ef smellt er á gögn draga upp röð af svarglugganum sem þú tilgreinir hvaða gögn sem notandinn ætti að veita þegar klára verkefni og Þessi notandi er augljóst.

The framleiðsla hluti (Variable: collect1) saves the ID of the task. You use this in your workflow to extract the user’s actual response via the "Compare any data source" condition.

Það ástand sýnir sem

Ef sviði jafngildir gildi

Smelltu á sviði og síðan f(x) icon and it pulls up another dialog box. Use this generalized dialog box to to tell SPD two things;

1. What is the list and column whose value you want to compare.

2. Hvernig ætti workflow vél finna tiltekna röð í þeim lista?

Til að gera þetta:

1. Change the "Source" dropdown to point at the correct task list. Note that the dialog box expands to show a "Find the List Item" kafla.
2. Í leit Upplýsingar sviði listanum, velja nafn á sviði þar sem verðmæti sem þú vilt (þetta kort til hvað þú heitir í safna gögnum valmynd ofan).
3. In the "Find the List Item" kafla, select "Tasks:ID" á sviði listanum.
4. Í gildi sviði, smelltu á f(x). This opens yet another dialog box.
5. Change the source "Workflow Data"
6. Select the workflow variable that matches to the "Output to Variable" frá safna gögnum aðgerð.
7. Smelltu á OK / Í lagi og þú ert búinn.

Það lítur út eins og þetta fyrir mig:

Á þessum tímapunkti, þú getur núna notað það gildi í workflow sem krafist.

Á Skýringar:

Sem innskot stutt, I always create an appropriately named workflow variable of type "List Item ID" and use that instead of the auto-generated "collect1".

This "compare any data source" valmynd sett er notað í nokkrum mismunandi stöðum í SPD og er vel þess virði að húsbóndi.

== Endir