UPDATE: Kuona huu mjadala MSDN, hasa kuingia mwisho: http://forums.microsoft.com/MSDN/showpost.aspx?postid=2631057&siteid=1. It describes a condition that may short circuit this whole thing. Kwa kifupi, inaweza kuwa rahisi kama kufanya angalau moja ya mashamba ya lazima.

Nina maktaba hati kwamba inasaidia bidhaa za aina nane.

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 hapa).

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. Katika hatua hii, 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. Wakati huo huo, 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. Hivyo … 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. Kuona hapa 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

Mara moja au mara mbili kwa mwezi, mtu posts swali jukwaa: "How do I include hyperlinks to URL’s that are clickable from a SharePoint Designer email?"

Kuwasilishwa bila maoni zaidi: (vizuri, kweli kuna zaidi maoni baada ya picha):

Becky Isserman ifuatavyo na maelezo muhimu ya jinsi ya embed kiungo kwa bidhaa katika barua pepe: 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

Mazingira: 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, Mimi kuamua kuhifadhi ukaguzi yangu mwenyewe ujumbe moja kwa moja kwenye fomu yenyewe.

Overview:

Design the form and publish it as a aina ya maudhui 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 (hatua #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" shamba.
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.

Maelezo:

Not all controls may configured for this bi-directional communication. Kwa mfano, 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: Hii imekuwa iliyotolewa kwa CodePlex hapa: http://www.codeplex.com/spdwfextensions

UPDATE: Angalia hapa kwa maelezo ya karibuni kutolewa: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!381.entry

UPDATE: Kuona hapa kwa mawazo yangu juu ya kibiashara ya mradi huu: 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 (dispatch) any C# function that you incorporated into the linked assembly.

Kama wa Oktoba mwishoni mwa, 2007, this is just an initial version of the project. I plan to expand it with a number of additional functions, ikiwa ni pamoja na substring, index, nafasi, 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.

Kama una maoni yoyote, maswali au mapendekezo, tafadhali waache katika maoni au email yangu.

Disclaimer:

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

Ufungaji hatua (kufuatwa kwa WFE kila aina katika shamba):

1. Download zip. Na dondoo.

2. Install the .dll into the GAC. I usually open c:\madirisha mkutano kutumia madirisha Explorer na nakala yake huko.

3. Kurekebisha web.config kuongeza mkutano na udhibiti salama:

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

<authorizedType Assembly="SpdGenericInterface, Version = 1.0.0.0, Utamaduni = neutral, PublicKeyToken = abe076fd8125f3c4" Namespace="Nivlag" TypeName="*" Authorized="True" />

4. Copy "SpdGenericInterface.actions" na C:\Mpango Files kawaida Files Microsoft Shared mtandao kompyuta upanuzi 12 KIOLEZO 1033 Workflow

Kumbuka kwamba mahali hapo ni maalum kwa mitambo ya lugha ya Kiingereza.

5. Karibu SharePoint Designer (ikiwa ni tayari kufungua).

6. iisreset

7. Kufungua SPD na kujenga workflow mpya.

Kama wote unaendelea vizuri, unapaswa watalipwa na jamii mpya ya hatua:

Maelezo:

Kuona hapa (http://blogs.msdn.com/sharepointdesigner/archive/2007/03/15/adding-activities-to-spd.aspx) kwa maelezo ya kali ya mchakato kwa ajili ya kujenga, kufunga na Configuring ufumbuzi kama hii.

Zip. Imeundwa ili kutoa moja kwa moja wewe c:\ drive. If you do this, unaweza kufungua mradi na njia yote itakuwa thabiti.

Kutumia hii katika studio ya Visual, you probably need to install "Extensions for Windows WF".

The initial upload contains just one "dispatcher function", "ToLower()". To add more functionality, kuongeza kwa Fanyeni njia kama inavyoonekana:

 kulindwa override ActivityExecutionStatus
          Kutekeleza(ActivityExecutionContext executionContext)
        {

            string functionToDispatch;
            functionToDispatch = hii.DispatchFunction.ToLower();

            kubadili (functionToDispatch)
            {
                kesi "tolower()":
                    {
                        hii.OutResult1 = hii.InParam1.ToLower();
                        kuvunja;
                    }

                default:
                    {
                        hii.OutResult1 = "Unknown function: [" + hii.DispatchFunction + "].";
                        kuvunja;
                    }
            }

            kurudi ActivityExecutionStatus.Kufungwa;
        } // ActivityExecutionStatus

    }

Kisha, 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" faili.

Nimepata na kujaribu kutumia template sampuli ambayo kuanza mbali kama:

<?xml toleo="1.0" encoding="UTF-8" ?>
<WorkflowInfo xmlns="http://schemas.microsoft.com / SharePoint /">
<Vitendo Mtiririko="kisha" Sambamba="na">

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

suluhisho ni strip nje sifa xmlns, 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, Nimekuwa kutumika kwa kuchochea mtumiaji kuidhinisha au kukataa ombi na kuingia baadhi ya comments.

Hatua hii inachukua fomu ya:

Kukusanya data kutoka hii mtumiaji (Pato kwa Kutofautiana: collect1)

Kwenye data pulls up mfululizo wa masanduku dialog ambapo wewe bayana nini data user wanapaswa kutoa wakati kukamilisha kazi na hii mtumiaji ni dhahiri.

sehemu ya pato (Kutofautiana: 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.

Kwamba hali inaonyesha kama

Kama shamba sawa na thamani

Bonyeza shamba na kisha 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. Jinsi lazima injini ya workflow Machapisho safu maalum katika orodha ambayo?

Kwa kufanya hivyo:

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" sehemu.
2. Katika Luke Maelezo shamba dropdown, kuchagua jina la uwanja ambao thamani unataka (hii ramani ya nini wewe kuitwa katika sanduku data dialog kukusanya kutoka juu).
3. In the "Find the List Item" sehemu, select "Tasks:ID" katika Shamba dropdown.
4. Katika uwanja thamani, bonyeza 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" kukusanya data kutoka hatua.
7. Click OK / OK na wewe ni kosa.

Inaonekana kama hii kwa ajili yangu:

Katika hatua hii, sasa unaweza kutumia kwamba thamani katika workflow yako kama inavyotakiwa.

Ziada Notes:

Kama kifupi kando, 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" kuweka dialog ni kutumika katika maeneo kadhaa tofauti katika SPD na ni pamoja na thamani mastering.

== Mwisho