Nyaraka za kila mwezi: Septemba 2007

MRO Workflow kesi utafiti kwa kutumia MOSS, SPD, InfoPath & mtandao wa huduma.

Overview

Kuingia hii inaeleza utafiti kesi kuelezea MRO halisi (Matengenezo, Kukarabati na Uendeshaji) workflow idhini ya mchakato wa kutekelezwa katika MOSS.

Hii si mjadala overtly kiufundi, lakini badala yake hutumika kutoa mfano halisi ya dunia kwamba inaonyesha jinsi jukwaa MOSS alikutana haja halisi ya dunia.

(Kuingia hii ni kuvuka posted kati ya http://paulgalvin.spaces.live.com na http://blogs.conchango.com)

Background

mteja mchakato MRO alikuwa na sifa zifuatazo

  • Mwongozo idhini ya mchakato.
  • Baadhi ya msaada kwa kutumia kuutumia Spreadsheets.
  • Irregular approval process. The same MRO purchase approval process would vary day to day, mtu kwa mtu.
  • Kura ya karatasi na saini mkono kuandikwa — Maombi ya kununua inahitajika hadi 3 imeandikwa saini kabla ya idhini ya mwisho.

malengo ya mradi huu ni pamoja:

  • Kikamilifu aŭtomate mchakato.
  • Kutekeleza viwango vya biashara kwa ajili ya idhini.
  • Kutoa maoni ya imara ya MRO ununuzi wa mameneja mbalimbali.
  • Detailed audit trail.

As a side effect of the solution, saini imeandikwa walikuwa tena required.

Mchakato idhini

The approval process consists of four "swim lanes": Mwanzilishi, Moja kwa moja meneja, Kazi meneja na meneja mgawanyiko.

Mwanzilishi:

Sees the need for the purchase and starts the process. Note that the originator may or may not actually enter the purchase requisition, but instead direct another staff member to do so. Some times, the originator does not have the technical expertise to fill out the PO requisition. Kwa mfano, user kutaka Shurutisho mpya mbali ya kompyuta, lakini hajui muuzaji bora, IT viwango, nk. Katika kesi hiyo, the originator works with IT and IT actually fills out the requisition.

Moja kwa moja meneja:

Hii ni meneja wa moja kwa moja ya mwanzilishi (ambayo inaweza kuwa tofauti kutoka kwa mtu ambaye kweli aliingia ndani ya shurutisho PO MOSS). Direct managers must approve the PO requisition before the system seeks approval further down the line.

Kazi Meneja:

The functional manager is the individual responsible for ensuring that the proposed purchase conforms to enterprise standards within the scope of a particular corporate function. Kwa mfano, IT purchases are approved by an IT functional manager.

Idara ya Meneja:

Division managers approve purchase requisitions strictly by dollar amount. Division manager approve purchase requisitions in excess of a configurable dollar amount.

Solution

We used the following tools and components to implement the solution:

Moss: Serves as the platform off which everything else "hangs". MOSS provides bedrock services for security, bwana data, ukaguzi trails na sifa nyingine.

InfoPath hutengeneza huduma: Moss sehemu, hii inawezesha watumiaji kujaza Maombi ya kununua kupitia kivinjari.

SharePoint Designer (SPD): Sisi kutumika SPD kutekeleza automatiska workflow mchakato.

Mtandao Huduma: A c# web service enhances the user experience by enabling cascading selections lists in the InfoPath form and provides better performance with respect to filtering data. Kuona hapa kwa ajili ya kiufundi dive kina juu ya somo hili na sababu zetu kwa kutumia.

Desturi Lists: MOSS user profiles provided a given user’s direct manager, but did not provide most of the data that controlled workflow decisions (e.g. kama meneja wa tarafa anahitajika kuidhinisha Shurutisho PO). We used custom lists in an "Enterprise Data" site to maintain data such as "Divisional Manager Approval Dollar Amount", "Functional Area Manager" and so forth. Lists integrated very nicely with InfoPath and also provide create/update/delete (CRUD) utendaji na ukaguzi na nje ya usalama wa sanduku.

Kutumia Uchunguzi

Hii kesi ya matumizi unaeleza jinsi ufumbuzi inafaa pamoja:

  1. Paul wants a new laptop. He describes his needs to Vivek, Mtu IT ukoo na viwango vya ushirika mbali, preferred wachuuzi, nk.
  2. Vivek magogo katika MOSS, accesses the PO Requisition form and enters the requisition on behalf of Paul. The form prompts Vivek for a purchase category which then uses the web services to populate a drop-down list of company-approved vendors. Vivek also specifies the corporate functional area of this purchase (e.g. "IT" or "Finance").
  3. SPD workflow makao kuanza, huamua Paulo moja kwa moja meneja na njia Shurutisho na meneja wake, Stacy.
  4. Stacy imeidhinisha Shurutisho ununuzi.
  5. SPD workflow inspects the requisition and determines it’s an IT purchase. It routes the workflow to the IT functional manager, Wonson.
  6. Wonson imeidhinisha shurutisho.
  7. SPD workflow tena inspects Shurutisho na huamua kwamba kiasi ununuzi unazidi maxium dola kiasi na njia yake na meneja mgawanyiko kwa idhini.
  8. meneja mgawanyiko imeidhinisha Shurutisho ununuzi.

Maelezo

  • The use case demonstrates a "clean" run with no rejections or jumps.
  • Every approver has the ability to approve or reject the requisition as well as provide written comments. These are logged in the audit trail.
  • Kama meneja kuwajibika anakataa Shurutisho ununuzi katika hatua yoyote, the PO requisition is "dead" and the process must be started from the beginning.
  • Workflow notifies mwanzilishi katika kila hatua ya mchakato.
  • Hakuna saini imeandikwa — mteja kuamua (baada ya baadhi ya mapendekezo ya kuingilia kwa nguvu) kwamba uchaguzi ukaguzi kama zinazotolewa kupitia historia workflow, aliwahi ukaguzi ya mahitaji yao ya.
  • Juhudi — it took approximately three man weeks to implement this solution.

Hitimisho

This solution leverages MOSS as a development and run-time platform. The client was able to leverage core MOSS features to automate a routine business process that affected nearly every employee in the company. With the exception of a simple web service (ambayo yenyewe leverages MOSS), almost no actual "programming" alitakiwa.

The solution also serves as a "showcase" kwa ajili ya mteja, demonstrating how different MOSS features can be combined to create a fully featured business application and generate new consulting opportunities in the future.

Glossary

MRO: Matengenezo, repair and operations. These purchases typically include items such as notepads, viti, kompyuta binafsi, Printers, kiini na kama.

Mtihani 70-542: Utafiti mapendekezo (Microsoft Office SharePoint Server 2007 – Matumizi ya Maendeleo)

UPDATE: Katika maoni, mtu posted kiungo hiki: http://www.midnightmonkey.co.uk/blog/blogging/?page_id=5. It looks good to me too.

Mimi kupita MOSS kiufundi mtihani leo, entitled "Microsoft Office SharePoint Server 2007 – Application Development". I found the exam to be pretty rigorous and that it matched up quite well with Microsoft’s maandalizi mwongozo.

Nimekuwa kazi na MOSS juu ya kila siku na hakuna kitu beats halisi mikono juu ya uzoefu kwa wote wa mitihani hizi.

Kwamba alisema, I took note of what I was studying as I studied. I believe that all of these resources are helpful, hasa kama njia ya kuimarisha kwamba mikono juu ya uzoefu.

Somo Kiungo
Kuutumia Huduma http://msdn2.microsoft.com/en-us/library/ms519581.aspx
Kutafuta No special recommendation. I had taken a class on search earlier this year and real-world experience carried me through. Work with the "search center" sehemu ya MOSS.
BDC http://msdn2.microsoft.com/en-us/library/ms563661.aspx
Watazamaji http://msdn2.microsoft.com/en-us/library/ms496822.aspx
Maelezo http://msdn2.microsoft.com/en-us/library/ms496822.aspx
Maudhui Mgmt http://www.sharepointblogs.com/tonstegeman/archive/2007/02/01/moss-custom-policies-part-1-creating-a-custom-information-management-policy.aspx

http://blogs.msdn.com/ecm/archive/2007/03/04/customize-the-page-editing-toolbar-in-moss-2007.aspx

http://msdn2.microsoft.com/en-us/library/aa674506.aspx

BI Mikono juu ya kazi na ya KPI katika MOSS.
Workflow http://msdn2.microsoft.com/en-us/library/aa830816.aspx
Info Mgmt http://msdn2.microsoft.com/en-us/library/bb397403.aspx
Tofauti http://aspnetcoe.wordpress.com/2007/02/09/customize-variation-root-landing-logic/
Records MGMT http://blogs.msdn.com/recman/archive/2006/06/16/633393.aspx
InfoPath http://msdn.microsoft.com/msdnmag/issues/06/08/infopath2007/default.aspx

Wengi wa viungo Wale kuongozwa na viungo zaidi na mimi wakijifanya kufuata yao hadi kuhusu 3 ngazi ya kina.

Napenda kusema kwamba kila kitu mimi kusoma moja kwa moja kutumika kwa mtihani, lakini mimi wala majuto kusoma yoyote ya hiyo na hata kama baadhi ya bits walikuwa si moja kwa moja husika. Ni mambo yote vizuri kujua na mimi sana kupendekeza vifaa kwa ajili ya kila anayetaka zilizofanyiwa watengenezaji MOSS.

MOSS / WSS Matokeo ya utafutaji (na dataviews): mtazamo ghafi XML data

Hii inaweza kuwa wazi kwa wengi, lakini wakati kusoma kwa ajili ya mtihani MOSS yangu programu, Nilijifunza kwamba ni pretty rahisi kupata XML halisi kutoka kutafuta swala kupitia interface user.

Njia moja ya haraka ni kama ifuatavyo:

  • Kupata tafuta ya juu.
  • Kufanya search kwamba anarudi baadhi ya data.
  • Hariri ukurasa (kupitia tovuti ya mazingira).
  • Change the XSL to the following:

<?xml toleo="1.0" encoding="UTF-8"?>
<
xsl:Lahamtindo toleo="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<
xsl:pato njia="xml" toleo="1.0" encoding="UTF-8" Indent="ndiyo"/>
<
xsl:template mechi="/">
<
pre>
<
xsl:copy-of kuchagua="*"/>
</
pre>
</
xsl:template>
</
xsl:Lahamtindo>

  • Hit apply.
  • View Source in the browser.

Note that the <pre> tag doesn’t do much except serve as a convenient marker when you view the results.

This trick can be very helpful when working with managed properties and customizing search. It will provide a definitive list of the XML available for you to use in your xslt which would have been very helpful the last 25 times I created some customized search results.

This ought to work for dataviews as well, though I have not tested that out as yet.

Hakuna CQWP kwa WSS? Jaribu hili…

I see that Eric Kraus was faced with a requirement normally met with a content query web part. tatizo? He was in a pure WSS environment with no access to the CQWP. Rather than curling up in the fetal position (kuwaomba nina kupigana, kila siku, inaonekana), he came up with solution that at least gives WSS shops a fighting chance to succeed. It’s described hapa.

Kipaji na kina mtazamo wa usimamizi wa maudhui API

Stefan Goßner has put together a terrific 4-part series on the SharePoint Content and Deployment API hapa. It offers a great overview and very good examples in code (C #).

I first picked up this link from joris poelmans blog at http://jopx.blogspot.com/.

Hata kama wewe ni kama mimi, in that you have not had to do much hands-on work for content management, this is well worth 20 minutes of your time to read.

Using the API, one can:

  • Export and import content very easily.
  • Re-parent content. If you want to export some content from a site "A" and send it to site "B" but in a totally new place in the hierarchy, this is possible.
  • Export content from a site A and import selected bits into site A.
  • Re-link content (meaning deal with all the hyperlinks).

WSS, doc libs & orodha ya, Mahesabu nguzo kuwashirikisha [Mimi]

Someone on the Internets was asking about how to create a calculated column on a list that would show a value formatted as "[Mtumiaji] – [Hali ya] – [Mahali]" as in "Paul Galvin – Kunywa [bure] Bia – The Beach".

Paul would go in and update his entry in the list and the calculated column would update appropriately. The [Mtumiaji] lazima default kwa mtumiaji kuingia / uppdatering orodha.

A calculated column cannot use "volatile" kazi kama vile [Mimi] au [Leo]. I solved it in a test environment with these steps:

  1. Create a text column named "Current User".
  2. Kuweka default thamani yake kwa [Mimi]
  3. Create a calculated column called "Calc Test".
  4. Kuweka thamani yake = [Sasa mtumiaji]

Nilikwenda katika, aliongeza bidhaa na orodha na ni kazi.

Kupita wangu 70-315 mtihani leo!

I passed the "Developing and Implementing Web Applications with Microsoft Visual C# .NET and Microsoft Visual Studio .NET" mtihani leo katika hali kubwa ya MA katika ofisi yenye heshima ya SolarTech katika HASBROUCK Heights.

I put this exam up there with BizTalk in terms of difficulty. You can’t fake your way through it.

Kujifunza, Nilikuwa MCAD / MCSD Self paced Mafunzo kit kitabu kiitwacho Zinazoendelea Maombi Mtandao na Microsoft Visual Basic NET na Visual C. #. NET.

Microsoft miongozo (hapa) are exactly correct IMO. The book addresses everything and if you have a modicum or real-world experience, it should be a straight-forward exam. If not, take the time get some real world experience or at least execute the labs in the book. That will probably give you what you need.

Mimi hata kwenda mbali kama kupendekeza kitabu wa pro, especially self-taught people like myself. It covers some basic stuff which I just never had a reason to stumble upon in my travels and I’m kicking myself a little bit for never having taken the time to learn them.

SharePoint Designer, “Kukusanya takwimu kutoka mtumiaji” na kutumia matokeo hayo.

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:

picha

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

Tags technorati:

Vipindi IE shambulio wakati wa kupata nyaraka katika maktaba WSS / MOSS hati

Nimekuwa wanakumbana na hii kwa 9 miezi na mimi kuona kwamba watu MSDN na vikao Usenet kuwa ni too.l

Wakati mwingine, wakati wa kupata hati neno (au nyingine doc aina) kutoka maktaba hati husababisha Internet Explorer tu ajali na kwenda mbali (kuchukua tabo wote na ni kama wapo ni wazi).

This MS hotfix may solve it: http://support.microsoft.com/kb/938888

Pia, there’s some description about the problem here:

http://jopx.blogspot.com/2007/07/solving-internet-explorer-crash-when.html

Mapenzi ya kweli XPath hatua mbele?

Overview:

Created orodha desturi kwamba itaweza aina maudhui na nguzo baadhi kadhaa.

Aliongeza kwa ukurasa na kisha kupitia SPD, waongofu katika mtazamo data.

Tatizo:

My Xpath expression was returning blank for a column named "Current Position". I referenced it thusly:

    <table border="1">
      <xsl:for-each select="/dsQueryResponse/Rows/Row" >
        <tr>
          <td>
            Current Status:
            <xsl:value-of select="@Current_x0020_Status"></xsl:thamani ya>
          </td>
        </tr>
      </xsl>
    </meza>

The column in the CT is named "Current Status". It shows up in the lookup as "Current Status". Everywhere you look, you see "Current Status".

While thrashing madly about, looking for a solution, I instead referred to "@Recruiter" and behold! — that actually returned back the current status. I expected it to return back the recruiter when I did that.

Ufumbuzi:

I poked about in SPD. Go to that page in SPD and it shows the data view. You can inspect the actual data provided to the view and associated Xpath. Here I found out that indeed, the Xpath pointed at "Recruiter". Strangely enough, the "actual" recruiter field pointed from "Recruiter1".

Take Away:

SPD provides authoritative Xpath expressions for rows & columns in a data view.

Pili, it shows the actual data. So for example, a column of type shows this:

<nobr><span><A HREF="/sites/Corporate/HumanResources/TalentAcquisition/_layouts/userdisp.aspx?ID=17">Galvin, Paulo</A><img mpaka ="0" height="1" width="3" src="/_layouts/images/blank.gif"/><a href=’javascript:’ onclick=’IMNImageOnClick();return false;’ class=’ms-imnlink’><img name=’imnmark’ title=” mpaka =’0′ height=’12’ width=’12’ src=’/_layouts/images/blank.gif’ alt=’No presence information’ sip=’PGalvin@xxx.com’ id=’imn_77,type=smtp’/></a></span></nobr>