I’m working on a project that uses five different SharePoint Designer work flows to handle some document approvals. SPD provides the "collect data from a user" hatua ili tuweze kuchochea mtumiaji kwa bits tofauti ya habari, kama vile kama wao kupitisha, some comments and maybe ask what they had for dinner the other night.

The forms are perfectly functional. They are tied to a task list as a content type. Wao ni 100% system-generated. This is their strength and weakness. If we can live with the default form, then we’re good to go. Hata hivyo, we don’t have too much control over how SPD creates the form. If we don’t like that default behavior, we need to resort to various tricks to get around it (kwa mfano, setting priority on a task).

I needed to provide a link on these task forms that opened up the view properties (dispform.asxp) of the "related item" in a new window. This provides one-click access to the meta data of the related item. This is what I mean:

Nashiriki, we can do that and it’s not very hard. Broadly speaking, fire up SPD, navigate to the directory that houses the workflow files and open the ASPX file you want to modify. These are just classic XSL transform instructions and if you’ve mucked about with itemstyle.xsl, search or other XSL scenarios, this will be easy for you. Kwa kweli, Nimeona ni kuwa kwa ujumla rahisi tangu fomu yanayotokana fulani ni rahisi kufuata ikilinganishwa na sehemu tafuta matokeo mtandao msingi (au nightmarish CWQP).

Bila shaka, there is one major pitfall. SPD’s workflow editor expects full control over that file. If you modify it, SPD will happily overwrite your changes give the right set of circumstances. I did two quick tests to see how bad this could get. They both presuppose that you’ve crafted a valid SPD workflow that uses the "collect data from a user" hatua.

Mtihani 1:

• Kurekebisha faili ASPX kwa mkono.
• Mtihani ni (kuhakikisha kwamba mabadiliko yako walikuwa vizuri kuokolewa na hakuwa na kuvunja kitu).
• Kufungua workflow na kuongeza hatua lisilohusiana (such as "log to history").
• Ila workflow.

Kusababisha: Katika kesi hiyo, SPD did not re-create the form.

Mtihani 2:

• Do the same as #1 except directly modify the "collect data from a user" hatua.

Kusababisha: This re-creates the form from scratch, over-writing your changes.

Final Notes:

• At least two SPD actions create forms like this: "Collect Data From a User" and "Assign To Do Item". Both of these actions’ forms can be manually modified.
• I was able to generate my link to dispform.aspx because, katika kesi hii, the relate item always has its ID embedded in the related item’s URL. I was able to extract it and then build an <href> based on it to provide the one-click meta data access feature. It’s unlikely that your URL follows this rule. There may be other ways to get the ID of the related item but I have not had to cross that bridge, so I don’t know if gets to the other side of the chasm.
• I didn’t investigate, but I would not be surprised if there is some kind of template file in the 12 hive that I could modify to affect how SPD generates the default forms (much like we can modify alert templates).

</mwisho>

Kujiunga na blog yangu!