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" ekintza da, beraz, informazio-bit desberdinak erabiltzaileari galdetuko dezakegu, onetsiko dira, hala nola, bertan duzun, zenbait iruzkin eta agian zer eskatu zuten afaria beste gau.

The forms are perfectly functional. They are tied to a task list as a content type. Dira 100% system-generated. This is their strength and weakness. If we can live with the default form, then we’re good to go. Hala eta guztiz ere, we don’t have too much control over how SPD creates the form. If we don’t like that default behavior, hainbat trikimailu jotzea da mugitu behar dugu (adibidez, lehentasuna ezartzeko zeregin batean).

Zeregin bat inprimaki horietan lotura duten ikuspegi ireki propietate eman behar nuen (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:

Zorionez, we can do that and it’s not very hard. Broadly speaking, sua sortu 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, bilaketa edo beste XSL eszenatoki, this will be easy for you. Izan ere,, Izango da, oro har, errazago aurkitu dut sortutako forma zertxobait errazagoa baita bilaketa-core emaitzak web parte aldean jarraitu behar (edo nightmarish CWQP).

Jakina, 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" urratsa.

Test 1:

• Aldatzeko eskuz fitxategia ASPX du.
• Probatu ezazu (egiaztatu diren aldaketak behar bezala gorde, eta ez du ezer apurtu).
• Ireki workflow eta kanpoko ekintza bat gehitu (such as "log to history").
• Gorde eu.

Emaitza: Kasu honetan, SPD ez da berriro sortu inprimakia.

Test 2:

• Bera egiten gisa #1 except directly modify the "collect data from a user" Ekintza.

Emaitza: Hau hutsetik formularioa re-sortzen, Zure aldaketak baino gehiago idazten.

Final Oharrak:

• Gutxienez bi SPD sortzeko ekintza hau bezalako forma: "Collect Data From a User" and "Assign To Do Item". Both of these actions’ forma eskuz alda daiteke.
• Gai nire dispform.aspx lotura sortu nahi izan dut delako, kasu honetan, 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 bat> 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, beraz, ez dakit leizetik beste aldean bada lortzen.
• Ez dut ikertu, baina ez nuke ez da harritu batzuk txantiloi fitxategi mota badago 12 hive SPD nola sortzen lehenetsi forma eragin hori ezin dut aldatu (askoz bezala alerta txantiloiak alda dezakegu).

</amaiera>

Nire blog Harpidetu!