UPDATE: Ara din id-diskussjoni MSDN, speċjalment l-aħħar dħul: http://forums.microsoft.com/MSDN/showpost.aspx?postid=2631057&siteid=1. It describes a condition that may short circuit this whole thing. In short, jista 'jkun sempliċi bħala teħid mill-inqas wieħed mill-oqsma obbligatorji.

I jkollhom librerija dokument li jappoġġja tmien tipi ta 'kontenut.

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

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. F'dan il-punt, 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. Fl-istess ħin, 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. Allura … 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. Ara hawn 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

Darba jew darbtejn fix-xahar, xi ħadd postijiet ta 'kwistjoni forum: "How do I include hyperlinks to URL’s that are clickable from a SharePoint Designer email?"

Ippreżentat mingħajr aktar kummenti: (ukoll, attwalment hemm aktar kummenti wara l-immaġni):

Becky Isserman ġej bi spjegazzjoni utli dwar kif ssodata link għal oġġett fil-email: 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

Xenarju: I have an InfoPath form that front-ends a workflow process implemented using SharePoint Designer. At one point, a manager must approve the form. Peress I ma jista 'joqgħod fuq l-istorja workflow biex jissodisfaw rekwiżiti ta' verifika tiegħi, I jiddeċiedu li jaħżen messaġġ tiegħi verifika stess direttament fuq il-formola innifsu.

Ħarsa ġenerali:

Disinn tal-forma u jippubblikaha bħala Tip kontenut 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" għal librerija forom (jew ħafna, jekk inti tixtieq). Write a workflow that updates the field.

Passi speċifiċi:

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. Tippubblika l-forma bħala tip kontenut (MHUX dokument).
5. Filwaqt li timla l-dialogs pubblikazzjoni:
   a) Salv l-fajl. Xsn għal-librerija dokument (pass #1).
   b) Tippubblika l Messaġġ Verifika "" qasam u l-marka vera: "Ħalli l-utenti li jeditjaw data f'dan il-qasam bl-użu ta datasheet jew proprjetajiet paġna".
   c) Oħloq tip kontenut ġdid u tagħtih l-isem xieraq.
6. Aċċess-librerija forom.
   a) Mur settings avvanzati tagħha u jippermettu lill-librerija formoli biex jimmaniġġjaw tipi ta 'kontenut.
   b) Agħżel it-tip kontenut għadu kif inħoloq (5c hawn fuq). It will be grouped under "Microsoft InfoPath" (jew simili).
   c) Neħħi l-default "Formola" Tip kontenut mill-bibljoteka.
   d) Immarka l-librerija biex "juru kif web page" sabiex il-formola se tniedi mill SharePoint u mhux il-klijent workstation InfoPath.
7. Go back to the forms library proper and click "New" li kemm jivverifika illi l-formola huwa mibgħut b'mod korrett u li jaġixxu kif tixtieq.
8. Fire up Disinjatur SharePoint u jinnavigaw-sit li tospita librerija formola tiegħek (minn pass 2).
9. Oħloq fluss tax-xogħol ġdid mehmuż mal-librerija forom.
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. Ikklikkja Finish u jmorru lura lejn il-librerija formola.
12. Create a new form and put some test value into the "Audit Message" qasam.
13. Ħlief dan u jmorru lura lejn il-librerija formola.
14. Right-click, select "Workflow" u jibdew fluss tax-xogħol tiegħek.
15. It should run almost immediately. Pull up the form (minn pass 12) u jekk kollox marret għall-pjan, "Audit Message" ġie assenjat kwalunkwe valur inti provdut fil-pass 10.

Noti:

Not all controls may configured for this bi-directional communication. Per eżempju, 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 ambjent u probabbilment anki teħtieġ ambjent SharePoint Intrapriża.

UPDATE: Dan ġie rilaxxata għall CodePlex hawn: http://www.codeplex.com/spdwfextensions

UPDATE: Ara hawn għal noti rilaxx aħħar: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!381.entry

UPDATE: Ara hawn għal ħsibijiet tiegħi fuq il-kummerċjalizzazzjoni dan il-proġett: 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 (dispaċċ) any C# function that you incorporated into the linked assembly.

Bħala ta 'Ottubru tard, 2007, this is just an initial version of the project. I plan to expand it with a number of additional functions, inklużi substring, indiċi, jissostitwixxu, 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.

Jekk għandek xi kummenti, mistoqsijiet jew suġġerimenti, jekk jogħġbok jħallu lilhom fil-kummenti jew email me.

Ċaħda ta 'responsabbiltà:

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

Passi installazzjoni (li għandhom jiġu segwiti għal kull WFE fil-farm):

1. Niżżel il-. Zip u estratt.

2. Install the .dll into the GAC. I usually open c:\użu twieqi assemblaġġ twieqi Explorer u kopja hemm.

3. Timmodifika web.config li żżid l-assemblea għall-kontrolli sikuri:

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

<authorizedType Assembly="SpdGenericInterface, Verżjoni = 1.0.0.0, Kultura = newtrali, PublicKeyToken = abe076fd8125f3c4" Namespace="Nivlag" TypeName="*" Authorized="True" />

4. Copy "SpdGenericInterface.actions" sa C:\Program Files Files Komuni Microsoft maqsuma estensjonijiet web server 12 TEMPLATE 1033 Workflow

Innota li l-post ta 'hawn fuq huwa speċifiku għall-installazzjonijiet tal-lingwa Ingliż.

5. Designer SharePoint Agħlaq (jekk huwa diġà miftuħa).

6. iisreset

7. Iftaħ SPD u toħloq workflow ġdida.

Jekk kollox imur sew, inti għandek tkun ippremjata bi kategorija ġdida ta 'azzjoni:

Noti:

Ara hawn (http://blogs.msdn.com/sharepointdesigner/archive/2007/03/15/adding-activities-to-spd.aspx) għal ħarsa terrific tal-proċess għall-ħolqien, installazzjoni u l-konfigurazzjoni ta 'soluzzjoni bħal din.

Il. Zip hija mfassla biex estratt direttament lilek c:\ drive. If you do this, inti tista 'tiftaħ il-proġett u l-mogħdijiet kollha ser ikunu konsistenti.

Biex tuża dan studio viżwali, you probably need to install "Extensions for Windows WF".

The initial upload contains just one "dispatcher function", "ToLower()". To add more functionality, iżżidhiex mal-metodu Teżegwixxi kif muri:

 protetti override ActivityExecutionStatus
          Teżegwixxi(ActivityExecutionContext executionContext)
        {

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

            jaqilbu (functionToDispatch)
            {
                każ "tolower()":
                    {
                        dan.OutResult1 = dan.InParam1.ToLower();
                        break;
                    }

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

            ritorn ActivityExecutionStatus.Magħluq;
        } // ActivityExecutionStatus

    }

Imbagħad, 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" fajl.

Stajt misjuba u ppruvaw jużaw kampjun ta 'mudell li jibda off bħala:

<?xml Verżjoni="1.0" encoding="UTF-8" ?>
<WorkflowInfo xmlns="http://schemas.microsoft.com / Sharepoint /">
<Azzjonijiet Sekwenzjali="imbagħad" Parallel="u">

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

Is-soluzzjoni hija għal strixxa l-attribut 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, Stajt użati biex fil-pront lill-utent biex japprovaw jew jiċħdu talba u jidħol xi kummenti.

Din l-azzjoni tieħu l-forma ta ':

Iġbor data minn dan l-utent (Output biex Varjabbli: collect1)

Tikklikkjaw fuq data jiġbed up serje ta 'kaxxi dialog fejn inti tispeċifika liema data l-utent għandhom jipprovdu meta titlesta l-kompitu u dan l-utent huwa ovvju.

Il-parti output (Varjabbli: 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.

Din il-kundizzjoni turi kif

Jekk qasam ugwali valur

Ikklikkja fuq qasam u allura l-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. Kif għandha l-magna workflow jillokalizza l-ringiela speċifiku f'dik il-lista?

Biex tagħmel dan:

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" taqsima.
2. Fil-qasam Dettalji Lookup dropdown, tagħżel l-isem tal-qasam li l-valur trid (dan mapep għal dak li jissejjaħ fil-Iġbor dialog box data minn fuq).
3. In the "Find the List Item" taqsima, select "Tasks:ID" fil-Qasam dropdown.
4. Fil-qasam tal-valur, ikklikkja fuq il-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" mill-azzjoni data Iġbor.
7. Ikklikkja OK / OK u qed isir.

Jidher qisu dan għalija:

F'dan il-punt, inti issa tista 'tuża dak il-valur fil-fluss tax-xogħol tiegħek kif meħtieġ.

Noti Addizzjonali:

Bħala qasira 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 sett huwa użat f'diversi postijiet differenti fil SPD u huwa ukoll jiswa nikkontrollaw.

== Aħħar