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" actionem possumus promptus pro diversis user notitia frenos, ut si comprobaritis, et maybe quidam comments quaerunt quid haberet alter nocte cenae.

The forms are perfectly functional. They are tied to a task list as a content type. Sunt 100% system-generated. This is their strength and weakness. If we can live with the default form, then we’re good to go. Autem, we don’t have too much control over how SPD creates the form. If we don’t like that default behavior, ut circa illud variis artibus uti oportet (enim, statuentes prioritatis ex negotii).

Opus ad providere a link ex his formis negotium aperuit visum proprietatum (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:

Gratanter, we can do that and it’s not very hard. Broadly speaking, accenderet 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, missionibus vel p alia quaerere, this will be easy for you. In facto, Inveni eam esse plerumque facilius cum forma generati, est aliquanto facilius sequuntur, per comparationem ad a quaero praecessi textus partem cori (uoniam nightmarish CWQP).

Utique, 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" step.

Test 1:

• Temperare file per manum ASPX.
• Experiri (verificetur quod mutationes sunt proprie vestra et non fregerunt aliquid salvus).
• Et aperire workflow addere finitimus actione (such as "log to history").
• Nisi workflow.

Result: In hoc, SPD non re-creare forma.

Test 2:

• Ut idem faceret quod #1 except directly modify the "collect data from a user" Actio.

Result: Hac re-creare forma a VULNUS, nimium scriptis mutationes tuas.

Nota finali:

• Saltem duarum partum formas huiusmodi actiones SPD: "Collect Data From a User" and "Assign To Do Item". Both of these actions’ formae possunt tincidunt modified.
• Fui quod posse generare mea pagina dispform.aspx, hoc in casu, the relate item always has its ID embedded in the related item’s URL. I was able to extract it and then build an <a 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, Nescio si ita fuerit soluta trans.
• Non cognituros, Sed non est mirum si in aliquam lectus lima 12 quod posset immutare alvum pertinere quam default formas generat SPD (multo sicut nos can modify intenti Templates).

</finem>

Scribet ad mea blog!