Monthly Archives: Mars 2008

Ákveða HRATT QRServer höfn

1 Svara

Til þess að samskipti við Fljótur Leita gegnum API, við þurfum að vita hafnar á tré QRServer er í gangi.

Ég fylgdi þessum leiðbeiningum til að finna það:

  1. Skráðu þig inn á the fljótur admin síðuna (http://server:port/admin).
  2. Sigla til System Overview.
  3. Locate "Search Dispatcher" og smelltu á Spyglass táknið:

    mynd

  4. Ég notaði tókst gildi, 15100 for "Info Name" = "http":

    mynd

Skýringar:

1. Port 15100 appears to be the default out-of-the-box port number for the QRServer.

2. Notaðu þennan kóða svipaðar eftirfarandi að ræst tengingu við FAST:

     ISearchFactory searchFactory;

    NameValueCollection nameValueCollection = ný NameValueCollection();

    nameValueCollection.Add("fastsearchengine", "Com.FastSearch.Esp.Search.Http.HttpSearchFactory");
    nameValueCollection.Add("Com.FastSearch.Esp.Search.Http.QRServers", "fastdemoback:15102");
    nameValueCollection.Add("Com.FastSearch.Esp.Search.Http.RequestMethod", "GET");

    searchFactory = SearchFactory.NewInstance(nameValueCollection);

3. Ef þú velja stórlega rangt höfn, þú færð gagnlegar villuboð:

mynd

4. Hins, ef þú velur gátt skráð á yfirlitinu (15102) you don’t get that helpful error message. Staðinn, síðar þegar þú reynir að fá aðgang að þeim gögnum um leit eða vísa a fljótur útsýni, you get an error. Debugging shows that the searchFactory’s view count is zero. You’ll be given the message "Failed to fetch Search View List".

</enda>

Technorati Tags:

Gerast áskrifandi að bloggið mitt.

Undir SharePoint Tæknilegar Patterns Design: SharePoint Designer Vinnuflæði + Atburður Receiver = High Virkni hanastél

Skildu eftir skilaboð

Einn af vaxandi mynstur ég finna í föndur SharePoint lausnir notar SharePoint Designer workflow og atburð móttökutæki.

Hér er fyrirtæki atburðarás tvö setja það í samhengi:

  • Ég senda skjal til læknir lib.
  • Ég sparka burt multi-skref workflow búin til með SharePoint Designer.
  • Á einhverjum tímapunkti á því ferli, workflow assigns a task to someone (via collect data from user or assign a task).
  • We want to use a KPI to track how long that task is awaiting completion. The KPI shows green for tasks that are completed or due more than 3 days from now. It shows yellow if the task is due tomorrow or today. It shows red if the task is past due.
  • Here’s the kicker: I want the date that drives that KPI to be holiday-aware.

I can’t calculate a holiday-aware due date in SharePoint Designer workflow very easily. I would have to create a custom action or use a 3rd party tool. Hins, it’s easy enough to calculate such a date in an event receiver. Merge those two together and we get a pattern like this:

  • Define a hidden yes/no site column on the document library labeled "DoCalcualteDueDate".
  • Initialize it to false.
  • At the appropriate time in the workflow (e.g. just before the "collect data" aðgerð), assign that value to True.
  • An ItemUpdate() event receiver looks to see if "DoCalculateDueDate" is true. Since the event receiver runs on every update, "DoCalculateDueDate" is normally false.
  • When workflow assigns DoCalculateDueDate to true, the event receiver calculates the holiday-aware due date.
  • When the event receiver does this calculation, it sets the DoCalculateDueDate flag to false.

Í lok, SPD workflow is communicated with an event receiver via the DoCalculateDueDate semaphore and we have holiday-aware due dates that are assigned at the exactly correct moment in the workflow’s life. SharePoint Designer controls when the due date is assigned but the event receiver performs the actual calculation and assignment.

</enda>

Gerast áskrifandi að bloggið mitt.

Mæld Hegðun: Færa SPD Verkferlar innan vefsvæðis Collection

Skildu eftir skilaboð

UPDATE: I’ve been researching how to embed a SPD workflow into a site definition. Þetta MSDN vettvangur keðja hefur nokkrar áhugaverðar upplýsingar. It’s not conclusive, en bendir á leið í gegnum frumskóginn.

I’m giving this post a slightly oddball "Observed Behavior" lead since I’m a little leery of drawing conclusions from it. SPD workflows are … skapstór.

Fólk er oft að spyrja / spá / fretting over moving SPD workflows from one place to another. Í dag, Ég fylgdi þessum leiðbeiningum og gert þessar athuganir:

  • Ég bjó til Workflow nota SharePoint Designer í síðuna fylgir skjal bókasafn.
  • Tilheyrandi skjal bókasafn húsa þegar nokkur skjöl.
  • Ég bjargaði síðuna sem sniðmát.
  • Þegar ég vistað á síðuna sem sniðmát, Ég spara efni og.
  • Ég bjó til nýja síðu í sama staður safn með að sniðmát.

Á þessum tímapunkti, I tried to run the workflow. It promptly terminated itself with the log message, "Failed on start".

I expected this. I have low expectations when it comes to moving SPD workflows around.

I continued:

  • Opened the site in SharePoint Designer.
  • Had a peek at the workflow. It seemed fine.
  • I clicked "Finish".
  • I ran the workflow.

Í þetta sinn, það í uppnámi fínn.

I’ll add that this workflow used the "collect data from user" action which is a relatively complex action under the hood.

I tentatively conclude that the process of "finishing" the workflow caused SPD to properly associate the SPD workflow with the new document library. I also conclude the XOML and other XML artifacts are reasonably "loose". They are not super tightly coupled to the document library.

What does this mean? Assuming it’s a reliable and reproducible process, there’s at least one rough method we can use to move them around. I don’t know if this would work if we crossed site collection boundaries or even more drastically, entire new farms (e.g. dev to stage to prod).

If you’re reading this and inclined, please post a comment or email mig your SharePoint Designer migration story. I’ll gladly update this posting with any insights thus offered.

</enda>

Gerast áskrifandi að bloggið mitt.

Technorati Tags:

Fljótleg og einföld: Workflow aðeins Update Field

1 Svara

It’s often useful to store status information in a custom list such as an approval code which should never be directly manipulated by end users. This is a common business scenario. I have been working on a project this year that generates various status and reminder dates via SharePoint Designer workflows that then drive KPIs and generally support time-critical business processes.

Use a site content type / column to achieve this effect.

Create a site content type with the status column as shown:

mynd

Note the "Status (for Demo)" field at the bottom.

Næsta, click on the column name to access the column’s properties. Select "Hidden (Will not appear in forms)" in the Column Settings section as shown:

mynd

This removes the field from the standard edit/update forms. Hins, it is still available in views, KPIs, the object model and anywhere else you want to use it, including SPD workflow.

</enda>

Gerast áskrifandi að bloggið mitt.

Sunnudagur Fyndið: “Ég hélt að þetta átti að vera ríkur Town”

1 Svara

Rúmlega þrjú ár síðan, konan mín og ég skráði son minn upp í sumar starfsemi, The Midland Park Players. This is a drama group that spends about three or four weeks preparing for a play and then showing it to the parents, friends and relatives. It’s always been done very well.

Ég veit ekki hvort barn allra er eins og þetta, but my son is extremely reluctant to try new things. Knowing this, we signed him up for the program. We’ve found that it’s best to alert him to these kinds of things early and often. Svo, í því skyni að sigrast á náttúrulega tregðu hans, Við sögðum honum snemma og gerði okkar besta til að gera það hljóð eins og gaman, o.fl.. Even with a multi-month advertising campaign, he still wasn’t convinced. We forced him to do, þó, og eins og er oft raunin, he had a great time.

Með því að næsta ár velti um, he had once again convinced himself that he didn’t want to participate. En, við höfðum skrifað undir hann og á núll-dagur, I dropped him off one morning at the high school where they practice. When I went to pick him up after lunch, hann var mjög spenntur, allar brosir og tilkynnt, "The play is the Velveteen Kanína and I want to be the Rabbit". He had spent literally months carrying on (stundum hysterically) um hvernig hann vildi ekki hafa neitt að gera með leikmenn Park og eftir fyrsta dag, he wants to be the lead role in the play. We’ve seen this pattern before.

(Mikið að koma á óvart okkar, Hann gerði fá Kanína hlutverk og hann var ótrúlegt.)

Fast forward a few years. He’s been in Park Players three times now, so he’s something of a veteran. This summer (2008), Players starts up again. Í the meðalvegur tími, hann er loksins sannfærður okkur að hann í raun doesn’t want to play soccer and he never liked basketball. That left him with no extra-curricular activities for late Winter / early Spring. A client with whom I was working mentioned that his daughter was in a program called Stage Right. Stage right is a slightly more expensive version of Park Players and it’s not in my town, but adjacent to it. Perfect.

The thing to know about that town is that it’s practically another country in terms of wealth. It has a high-frequency train right to Wall Street and NYC in general. It’s just a wealthy place. One of the on-going family discussion themes is whether we should have moved to that town instead of where we live now. It’s a bigger town, skóla bjóða fleiri forrit fyrir börn, o.fl.. My wife grew up in that town and her parents live there, so we are "hooked in" despite not living there. I personally grew up in different circumstances in Massachusetts, so I don’t have a lot to say about this during family dinner conversation. This isn’t to say that we aren’t very happy where we live. We just know that that town is a level above our town economically.

Stage Right’s next program started too soon for us to launch our normal advertising campaign to overcome my son’s reluctance. This is when he came up with one my personal favorite arguments against doing something: "Friday nights are blómi nætur fyrir utanríkis sofa!" Stage Right was going to interfere with his weekend socials.

Í dag kemur, við að koma honum þangað og sleppa honum burt og eins og með allt annað, eðlilegt ást hans bara að vera á lífi tók og hann hefur verið að hafa góðan tíma með það.

Þetta síðasta helgi konan mín var að tala við hann og í fyrsta sinn, I think he’s tailoring his discussions very precisely for his audience. She had asked him how Stage Right compares to Midland Park Players. He tells her that "In Park Players, we have teenagers that help us out. There aren’t any in in Stage Right. In Park Players, teenagers make all props. In Stage Right, we have to bring our own props. We have to do everything. And then he twists the knife: "I thought this was supposed to be a rich town."

Öll þessi ár, I never really thought that he was hearing or understanding anything as it related to the "rich town". Hins, það kemur í ljós að hann var.

</enda>

Gerast áskrifandi að bloggið mitt.

Technorati Tags:

SharePoint veitir ekki Dagatal Roll-ups; Mögulegum lausnum

4 Svör

UPDATE: An anonymous person in the comments posts this link: http://www.atidan.com/atidan-collaboration-kit.php

Spjallborð notendur spyrja oft með spurningu eins og þessa:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, notendur í undirvefsvæðum mun skapa Dagskrá, and will have the option of marking them as ‘public.’ Events marked as public will dynamically appear in the shared site calendar. Thus the shared site calendar is a roll-up of all public events from all subsite calendars."

Er WSS 3.0 eða Moss 2007, it is not possible to directly configure a "roll-up" calendar. Calendars exist on their own, óháð öðrum dagbók.

Til að búa til rúlla-upp dagbókina, fylgja eina af þessum leiðum:

  1. Use a Content Query Web Part. This is the easiest solution for MOSS users (WSS veitir ekki CQWP). CQWP, því miður, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (sjá hér fyrir eitt dæmi) en sjálfgefið, shows its results in simple list format. In many cases, CQWP sennilega gott val.
  2. A more programming-oriented solution would be to use event receivers. Implement event receivers on the subsite calendars that keep their public events in sync with the master calendar. As a given subsite calendar is modified, reach out to the master calendar and update it as needed. This option is available in both WSS 3.0 og Moss.

There are probably other clever solutions to this problem. If you have one or know of one, vinsamlegast eftir umsögn eða email mig og ég mun uppfæra þessa færslu.

</enda>

Gerast áskrifandi að bloggið mitt.

Búa Síður (SPWeb) með SharePoint Designer Workflow

Skildu eftir skilaboð

This blog entry is more of an "in the realm of the possible" færslu vs. steypu upplýsingar.

We have a technical design that calls for us to create a site in a site collection via a manually launched workflow process. Grundvallaratriðum, users enter data into a "new customer" Custom lista og svo þegar þeir hafa lokið og staðfest á færslu gögn ferli, við þurfum að búa til síðu fyrir að viðskiptavinur.

Ég er bæði stór aðdáandi af skilgreiningarþekkingar workflow og veikur Visual Studio workflow forritari, svo ég vildi til að mæta kröfum með SharePoint Designer.

Ég ætla að skrifa um þetta í meiri smáatriðum (og vonandi til staðar til notenda hóp eða tveimur á komandi ári), en hér er almennt lausn:

  • Búa til sérsniðnar aðgerðir sem sameinar með SPD.
  • The siðvenja aðgerð gerir SPD að beita vefur þjónustu og gefa það a band af XML.
  • Vefur þjónusta staðsetur róður í sérsniðnum lista og skapar nýja síðu eins og á gögnum um þessi nýju viðskiptavini með sérsniðna síða skilgreiningu.
  • Vefur þjónusta endurnýja þá sérsniðin lista með einhverjum upplýsingum eins og tengil á nýju síðuna.

Við talin önnur aðferðir, such as event handlers and visual studio based workflow. The SPD approach gives our end users a little more control over the process. Granted, það er mikið af C # kóða í þessa lausn, en það er vafinn inn í skilgreiningarþekkingar workflow, þannig að við fá sumir af the hagur af skilgreiningarþekkingar workflow en krókur inn á síðuna-sköpun þjónustu.

All we need now is an easy tool to automatically migrate SPD workflows around as easily as we can for visual studio workflows and we’ll really be cooking with gas 🙂 I understand that some folk are out there working on this problem and I hope they have some good success with it soon.

</enda>

Gerast áskrifandi að bloggið mitt.

Technorati Tags: ,

Fljótleg og einföld: Framlag a Web Site Með SharePoint Object Model Í C #

3 Svör

I tried searching for a little snippet code that would show how I can create a new SPWeb in a site collection. I didn’t find it as quickly or easily as I expected so I thought I’d slap together a little entry on the subject.

Þessi kóði býr til nýja Wiki síðuna:

 SPSite siteCollection;

    siteCollection = ný SPSite("http://conchang-o9l8qi");

    SPWeb W = siteCollection.OpenWeb();

    w.Webs.Add("xyzzy", "xyzzy Title",
        "xyzzy description", 1033, SPWebTemplate.WebTemplateWIKI, ósatt, ósatt);

My initial searches failed because I was looking for phrases like "provision a web site using sharepoint object model" and the like.

Ef þú leita for "Webs.Add()", þú munt finna fjölda af mjög gagnlegur bloggfærslur, MSDN articles and SDK documentation that go into depth on this subject. I definitely recommend þetta vefsvæði.

</enda>

Gerast áskrifandi að bloggið mitt.

Technorati Tags:

Samþætta SharePoint hönnuður workflows með vefþjónustu

2 Svör

Ég hef verið að leika í kring með sérsniðnum aðgerðir fyrir SharePoint Designer í nokkurn tíma (sjá hér fyrir nokkru ítarlegar efni, ef að hagsmunir þú).

Í núverandi verkefni mitt, we need to do some fairly heavy lifting and we want to use declarative SPD workflow to manage the associated business process.

Langa sögu stutta, this is entirely possible. I extended my Codeplex project to invoke a "helper service" and now we can invoke a web service directly from an SPD workflow.

Hér er undirskrift:

 almennings band Dispatcher(
        GUID WebID, // Samþykkt á keyrsluumhverfið
        GUID SiteID, // Samþykkt á keyrsluumhverfið
        band ListID, // Samþykkt á RTE (veit ekki hvers vegna þetta er band, ekki GUID)
        INT ListItemID, // Samþykkt á RTE.
        band XmlMessage) // Samþykkt af notanda sem tilgreind er í SPD.

Þetta notar þá staðreynd að við getum fengið á mikilvægum workflow upplýsingar, eins og síðuna, Listi ID, o.fl.. This is well documented in several places for those of you interested in creating your own custom actions. The idea is to extract the XML string as provided by the user to dispatch an appropriate procedure. Fun stuff!

Því miður, þetta er augljóslega ein leið miða niður "Loosey Goosey" andstæðingur-mynstur land, but it’s better than hitting a brick wall 🙂

Er það and-mynstur ef þú gerir það jafnvel þó að þú veist það er and-mynstur?

I hope to wrap this inside Codeplex in the near future. If you’re interested in me doing so, gefa mér pota (netfang eða eftir umsögn) and I’ll be that more enthusiastic about doing it 🙂

</enda>

Gerast áskrifandi að bloggið mitt.

Technorati Tags: ,

Sunnudagur Fyndið: “Ég furða ef lykilorðið er …”

1 Svara

Ég keypti nýlega hádegisverð fyrir bróður minn (eins og venjulega) and we ended up talking about funny things that we did at our respective colleges. At my alma mater, Lafayette College, the academic support IT department had a very inclusive way about it. We were given a LOT of rope and I took advantage of that at times.

Tvær mín uppáhalds minningar tengjast góðum vini mínum, Gabe. He had made the terrible mistake of telling people his freshman year that "I’m a freshman, en ég hef sophomore stöðu" vegna ýmissa háþróaður flokkum staðsetningu hafði hann tekið, o.fl.. Many of us were similarly situated but we didn’t talk about it so much. His senior year, Þegar við hann að fólk, we’d say "This is Gabe. He’s a Senior, but he has Sophomore standing".

The college had some Sun workstation/servers running X-Window. They had gigantic monitors and the engineers used them for CAD and other boring engineer stuff. We CS people used them to learn programming and, auðvitað, að spila leiki.

Við gerðum ekki eins og tölva-hjálparvana verkfræðinga að mikið svo einn af uppáhalds dótið okkar til að gera væri að telnet til kassi sem þeir voru á og hlaupa X-auga on them. This would pop up a pair of eyes that followed the mouse around on the screen. You could pop up even more and have literally a dozen or more of the X-eye applications running. Try not to laugh out loud when a hapless engineer is trying to close X-eye after X-eye and muttering under his breath about it 🙂

We also played X-trek on those boxes. To do that, þú þurftir að sækja uppruna, get various dependencies wherever you could find them and build it. I wasn’t a sophisticated C programmer, but I could read header files. I was looking through these and found directives like "#DEFINE MAX_TORPEDO_DISTANCE 10". I played around with that increase range and power for phases and torpedoes, aftur byggt það og síðan eytt Gabe næsta skipti sem við uppgefinn.

Gabe var einnig gríðarlegur aðdáandi af TV sýning sem heitir S Blake 7. I had never seen it, en ekki koma í veg fyrir mig heimta að sendi tölvupóst á Dr. Who is the superior show. The arguments would get heated at times 🙂

Einn daginn, it occurred to me that I could probably guess his UNIX password. I sat down next to him one day and announced in a loud tone, "I’m going to guess your password right now, Gabe." "Yeah, rétt" was his answer. I then logged in, inn notandi persónuskilríki hans, sneri sér að takast á honum, tegund og sagði upphátt, "I wonder if it’s B-L-A-K-E-7" ? Touch typing has never paid off as handsomely as it did that day.

Næsta vika (eða fljótlega): More computer room antics from college.

Ert þú hefur einhverjar til að deila? Leave a comment or email me and I’ll publish them here.

</enda>

Gerast áskrifandi að bloggið mitt.

Technorati Tags: