UPDATE: Ikusi MSDN eztabaida hau, batez ere, azken sarrera: http://forums.microsoft.com/MSDN/showpost.aspx?postid=2631057&siteid=1. It describes a condition that may short circuit this whole thing. Laburbilduz, izan bezain sinplea izan daiteke gisa hartzeko, gutxienez eremu bat derrigorrezkoa.

Dokumentuan liburutegi onartzen zortzi eduki mota behar dut.

I have a SharePoint Designer workflow that wants to calculate and assign a "reminder date" by simply subtracting 30 days from another column, "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." (You can read more about this kind of KPI and more substantial drill-down hemen).

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.

This strategy does not work when I upload a document.

I upload the document and I am presented with the meta data entry screen. Puntu honetan, I’m already in trouble. SharePoint has already, prematurely from my perspective, fired the workflow. I haven’t had a chance to pick the correct content type nor assign a due date. Aldi berean,, 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. Beraz, … my workflow has fired and when it executed, 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, I select the correct content type, enter the meta data and submit. The pause completes and the workflow proceeds as needed. (Note that in my environment, timer workflow activities from SPD do not work out of the box. You may have the same trouble. Ikusi hemen for more details).

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, but I still don’t like it.

I wrote about this on the MSDN forums here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2430725&SiteID=1

Behin edo bitan hilabete, Norbaitek mezu foro galdera bat: "How do I include hyperlinks to URL’s that are clickable from a SharePoint Designer email?"

Iruzkin gabe aurkezten: (ondo, Egia esan, ez da gehiago irudi ondoren duzu):

Becky Isserman honela sortu lagungarria azalpen nola elementu bati esteka bat txertatzeko email buruzko: 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

Eszenatoki: I have an InfoPath form that front-ends a workflow process implemented using SharePoint Designer. At one point, a manager must approve the form. Ezin dut, ez baita historia kontatzen workflow nire kontu ikuskaritza baldintzak betetzen, Nire kontu ikuskaritza mezua gordetzeko zuzenean forma bera erabaki dut.

Orokorra:

Diseinatzeko forma du, eta gisa, argitaratzen eduki mota 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" forma bat liburutegia (edo asko, nahi izanez gero). Write a workflow that updates the field.

Berariazko Urratsak:

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:
   bat) Save the .xsn file to the document library (urratsa #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.
   bat) 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" besterik egiaztatzeko inprimakia hori argitaratua behar bezala eta nahi duzun bezala jardunez.
8. Sua sortu SharePoint Designer eta gune hori inprimaki zure liburutegia antolatzen nabigatu (urratsa tik 2).
9. Sortu forma liburutegia atxikitako berriak eu.
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. Klik Amaitu eta itzuli inprimaki liburutegian.
12. Create a new form and put some test value into the "Audit Message" Eremu.
13. Gorde eta atzera inprimaki liburutegian.
14. Eskuin-klikatu, select "Workflow" eta martxan zure workflow.
15. It should run almost immediately. Pull up the form (urratsa tik 12) eta guztiak joan nahi izanez gero,, "Audit Message" izan bada esleitutako balioa edozein dela ere, betiere urratsean duzu 10.

Oharrak:

Not all controls may configured for this bi-directional communication. Adibidez, 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 ingurumena eta, seguruenik, baita Enterprise SharePoint ingurumena eskatzen.

UPDATE: Hori CodePlex kaleratu hemen: http://www.codeplex.com/spdwfextensions

UPDATE: Ikusi hemen oharra Azken oharrak: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!381.entry

UPDATE: Ikusi hemen nire pentsamenduak proiektu honi buruzko merkaturatzea: 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 (bidaltzea) any C# function that you incorporated into the linked assembly.

Urria berandu gisa, 2007, this is just an initial version of the project. I plan to expand it with a number of additional functions, azpikateak barne, indizea, ordeztu, 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.

Behar duzu iruzkinak egin nahi izanez gero, galderak edo iradokizunak, Mesedez, utzi iruzkin edo posta elektroniko.

Lege-oharra:

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

Instalazioa urrats (WFE bakoitzean jarraitu beharreko etxalde batean):

1. Deskargatzeko. Zip eta erauzteko.

2. Install the .dll into the GAC. I usually open c:\Windows muntaia Windows Explorer erabiliz, eta berau ez.

3. Aldatzeko web.config muntaia gehitzeko seguru kontrolak:

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

<authorizedType Assembly="SpdGenericInterface, 1.0.0.0 bertsioa =, Kultura = neutrala, PublicKeyToken = abe076fd8125f3c4" Namespace="Nivlag" TypeName="*" Authorized="True" />

4. Copy "SpdGenericInterface.actions" C:\Program Files Common Files Microsoft Shared web zerbitzari hedapenak 12 PLANTILLA 1033 Workflow

Kontuan gainetik kokapena dela ingelesaren instalazio espezifikoak.

5. Itxi SharePoint Designer (da dagoeneko ireki).

6. iisreset

7. Ireki SPD eta workflow berri bat sortzeko.

Dena ondo badoa bada, duzun jarduera-kategoria berri bat behar da saria:

Oharrak:

Ikusi hemen (http://blogs.msdn.com/sharepointdesigner/archive/2007/03/15/adding-activities-to-spd.aspx) prozesuaren ikuspegi orokor bat sortzeko emanaldirik for, instalatu eta konfiguratzen hau bezalako irtenbide bat.

. Zip diseinatuta dago zuzenean erauzi nahi duzu c:\ drive. If you do this, Proiektuaren ireki ahal izango duzu, eta bide guztiak koherentea izango da.

Hau erabili ahal izateko ikusmen estudioan, you probably need to install "Extensions for Windows WF".

The initial upload contains just one "dispatcher function", "ToLower()". To add more functionality, gehitu exekutatu metodoa erakusten:

 babesa baliogabetzeko ActivityExecutionStatus
          Exekutatu(ActivityExecutionContext executionContext)
        {

            katea functionToDispatch;
            functionToDispatch = honetan.DispatchFunction.ToLower();

            aldatzeko (functionToDispatch)
            {
                Kasu "tolower()":
                    {
                        honetan.OutResult1 = honetan.InParam1.ToLower();
                        apurtu;
                    }

                lehenetsi:
                    {
                        honetan.OutResult1 = "Unknown function: [" + honetan.DispatchFunction + "].";
                        apurtu;
                    }
            }

            itzultzeko ActivityExecutionStatus.Itxita;
        } // ActivityExecutionStatus

    }

Gero, 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" fitxategia.

Aurkitu dut eta saiatu txantiloia lagin bat hasten den bezala erabili nahi:

<?xml bertsioa="1.0" kodeketa="utf-8" ?>
<WorkflowInfo xmlns="http://schemas.microsoft.com / SharePoint /">
<Ekintzak Sekuentziala="ondoren," Paralelo="eta">

Hala eta guztiz ere, that xmlns attribute prevents my environment from working. My actions don’t show up in SPD.

Konponbidea da, kenduko xmlns atributuaren, 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, Erabiltzen dut erabiltzaile baten gonbita onartu edo ukatzeko eskaera bat eta zenbait iruzkin sartu.

Ekintza hau forma hartzen:

Collect data tik this user (Irteera Aldakorra: collect1)

Clicking on data pulls up a series of dialog boxes where you specify what data the user should provide when completing the task and this user begien bistakoa da.

The output part (Aldakorra: 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.

That condition shows as

Bada Eremu equals balioa

Click on Eremu and then the 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. How should the workflow engine locate the specific row in that list?

To do this:

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" section.
2. In the Lookup Details field dropdown, select the name of the field whose value you want (this maps to what you called in the Collect data dialog box from above).
3. In the "Find the List Item" section, select "Tasks:ID" in the Field dropdown.
4. In the value field, click on the 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" from the Collect data action.
7. Click OK/OK and you’re done.

It looks like this for me:

Puntu honetan, you can now use that value in your workflow as required.

Additional Notes:

As a brief aside, 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" dialog set is used in several different places in SPD and is well worth mastering.

==end