Category Archives: Iter 2008

Determinare GRAVITER QRServer Port

1 Respondere

Ut, per eius API communicábo cum ieiunium Quaerere, Scire oportet, quo ex portu currit QRServer.

Secutus est illos gradus collocare:

  1. Log in situ ieiunium admin (http://server:port/admin).
  2. Some Overview System.
  3. Locate "Search Dispatcher" click in icon spyglass:

    imaginem

  4. Ego feliciter usus valor, 15100 for "Info Name" = "http":

    imaginem

Notes:

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

2. Uti huius Codicis similis ad sequentes ad instantiate connexionem ad ieiunium:

     ISearchFactory searchFactory;

    NameValueCollection nameValueCollection = novum 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. Si recte colligunt a portu bacchatur, vos adepto a benevolens erroris nuntius:

imaginem

4. Autem, si colligunt prodigium numerus recensentur in overview (15102) you don’t get that helpful error message. Pro, postea cum conantur ut obvius ullus notitia inquisitionem vel per visum Pomponius jejunium, 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".

</finem>

Technorati Tags:

Scribet ad mea blog.

Technical consilium exemplaria ad SharePoint: SharePoint amet Workflow + Maximum eventus Receptor = potentia Cocktail

Aliquam responsum

Unus de emergentes exemplaria invenio in innectis SharePoint solutiones leverages SharePoint Designer workflow, et opus Receptorem.

Hic est a negotio missionis ponerent in context:

  • Ego upload a tabellae ut a doc lib.
  • Ego calcitrare off multi-step usura workflow creavit SharePoint Designer.
  • Ad punctum in quod processus, workflow assignat officium alicui (per colligere notitia de user negotium vel assignare).
  • 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.
  • Hic 'CALCITRO: Volo diem festum esse qui pellit quod KPI-Conscius.

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. Autem, 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".
  • Ut falsum illud Initialize.
  • In tempore opportuno workflow (e.g. just before the "collect data" Actio), quod ad verum valorem assignaret.
  • An ItemUpdate() event receiver looks to see if "DoCalculateDueDate" is true. Since the event receiver runs on every update, "DoCalculateDueDate" falsum est normaliter.
  • Cum workflow assignat veram DoCalculateDueDate, Receptorem Supputat eventus feriae-date debitum conscia.
  • Ubi ad rem facit accipientis Calculo, Nuntium ad hoc ponit falsam DoCalculateDueDate.

In finem, 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.

</finem>

Scribet ad mea blog.

Moribus observatum: Movens SPD Workflows intra Collection Site

Aliquam responsum

UPDATE: I’ve been researching how to embed a SPD workflow into a site definition. Haec forum MSDN catenam notitia aliqua interesting. It’s not conclusive, sed puncta ad viam per truncatis.

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 … temperamental.

Populus saepe interrogat / Mirantes / fretting over moving SPD workflows from one place to another. Hodie, Et ego post hos gradus facti, haec observamus:

  • Workflow creata sum usura a SharePoint Designer in situ attachiatus ad documentum bibliotheca.
  • Bibliothecam jam socius tabellae est tere pluribus documenta.
  • Lorem ipsum dolor sit amet, ut servatum a me.
  • Cum ego, ut salvos situm template, Tam contentus sim salvus.
  • Ego novum situ in eodem collection site usura id template.

Ad hoc, 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.

Dixique:

  • Aperuit in situ SharePoint Designer.
  • Had a peek at the workflow. It seemed fine.
  • I clicked "Finish".
  • Cucúrri in workflow.

Hoc tempore, id operato simila.

I’ll add that this workflow used the "collect data from user" Sed actio quae est multiplex secundum actionem sub cucullo.

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.

Quid hoc? 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, Novus omnis firmis (e.g. Dev ad scaenam FODICO).

Si hoc legere scis inclinatus, consectetur adipiscing elit velit vel email me your SharePoint Designer migration story. I’ll gladly update this posting with any insights thus offered.

</finem>

Scribet ad mea blog.

Technorati Tags:

Vivos et Simplex: Workflow tantum Update Field

1 Respondere

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.

Uti typus euismod / agmine consequi effectum.

Partum a situ contentus cum status column type ut ostensum:

imaginem

Note the "Status (nam Demo)" agro ad imum.

Postero, click on the column name to access the column’s properties. Select "Hidden (Non apparent in formis,)" Column Occasus ut ostendo in sectione:

imaginem

This removes the field from the standard edit/update forms. Autem, tamen est available in views, KPIs, et id quod alibi uti velis, including SPD workflow.

</finem>

Scribet ad mea blog.

Dominica Funny: “Suspendisse lacus supponitur esse putabam”

1 Respondere

Paulo super tres annos, uxorem et signati mea filius pro a aestate actio, 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.

Nescio si cuivis puero hoc, 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. Ita, ut naturam ipsam vinceret invitus, nos ei mane et fecit optimum ut sonus fun, etc. Even with a multi-month advertising campaign, he still wasn’t convinced. We forced him to do, licet, et ut est saepe causa, he had a great time.

Tempus per annum secundum volutabatur, he had once again convinced himself that he didn’t want to participate. Sed, nos signati eum et in nulla hodie, I dropped him off one morning at the high school where they practice. When I went to pick him up after lunch, erat ipsum excitatur, omnes rident et nuntiatum, "Est fabula in Velveteen Rabbit and I want to be the Rabbit". He had spent literally months carrying on (aliquando hysterically) Quomodo noluit habere cum dies et justo Players, he wants to be the lead role in the play. We’ve seen this pattern before.

(Nostra admiratio, fecit adepto Rabbit munus et erat miris.)

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. Interea, ipse suus tandem persuasum nobis vere 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, eius scholis offerre magis progressio pro haedos, etc. My wife grew up in that town and her parents live there, sic sunt "aduncum 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: "Veneris noctibus sunt prima noctes somno overs!" Stage Right was going to interfere with his weekend socials.

Die venit, ferimus, et ibi eum cædere, et cetera, Amor naturalis est vivere sed valere eros et accepit eam cum tempus.

Volutpat vestibulum dixisset praeterita et primum uxorem, 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: "Ego hanc urbem opulentam ponebatur."

Omnibus annis, I never really thought that he was hearing or understanding anything as it related to the "rich town". Autem, vertit ex erat.

</finem>

Scribet ad mea blog.

Technorati Tags:

SharePoint Non providentes Calendar rotulo-ups; Potentia Solutions

4 Restituo

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

Forum users saepe interrogare sicut hoc:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, users in subsites erit creare calendarium eventus, 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."

Est WSS 3.0 vel MUSCUS 2007, est non posse directe configurare a "volumen-usque" calendar. Calendars exist on their own, independens alterius calendarium.

Creare volumen-usque calendarium, sequitur ex his semitas:

  1. Use a Content Query Web Part. This is the easiest solution for MOSS users (WSS non providere CQWP). CQWP, infeliciter, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (hic enim uno) sed per default, shows its results in simple list format. In many cases, CQWP probabiliter bonum electio.
  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 et MUSCUS.

There are probably other clever solutions to this problem. If you have one or know of one, placere relinquat comment vel email me et update hoc post.

</finem>

Technorati Tags: ,

Scribet ad mea blog.

Creare Sites (SPWeb) per SharePoint amet Workflow

Aliquam responsum

Vestibulum turpis est de "in regnum posset" introitu nobis. concretum info.

We have a technical design that calls for us to create a site in a site collection via a manually launched workflow process. Basically, users intrare notitia in "novum Lorem" consuetudinem album et cum consummavi et convalidatur notitia introitu processus, opus ad partum a site quod Lorem.

Sum tam a magnus fan de enuntiativum workflow ut a infirmus visivae Studio workflow programmator, sic voluit ad exigentiam usura SharePoint amet.

EGO intentio scribo hic uberius (Morbi convallis neque et spe praesens annus duo), sed hic altiore solutio:

  • Creare consuetudo actio quod integrates cum SPD.
  • Consuetudinem actio permittit SPD invocare telam ministerium et transire filo XML.
  • Meaning ministerium locat versu in consuetudinem album et creat novum site ut per notitia quod novum client usura consuetudo site definitio.
  • Meaning ministerium ergo updates consuetudinem album cum notitia ut a link ad novum site.

Nos considerari alia aditus, such as event handlers and visual studio based workflow. The SPD approach gives our end users a little more control over the process. Granted, Solutio in C # augue mattis wisi, sed suus involvit intus enuntiativum workflow, ita nos aliquam de beneficia enuntiativum workflow dum hooking in site-creationis ministerium.

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.

</finem>

Scribet ad mea blog.

Technorati Tags: ,

Vivos et Simplex: Praescripto a Web Site Usura SharePoint Object Model In C #

3 Restituo

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.

Hoc codice creat novum Wiki site:

 SPSite siteCollection;

    siteCollection = novum SPSite("Http://conchang-o9l8qi");

    SPWeb w = siteCollection.OpenWeb();

    w.Webs.Add("Xyzzy", "Xyzzy Title",
        "Xyzzy description", 1033, SPWebTemplate.WebTemplateWIKI, falsum, falsum);

Mea initialis searches defecit quia est vultus pro phrases sicut "praescripto a situ usura sharepoint obiectum exemplar" and the like.

Si quaerere enim "Webs.Add()", scies plura utilis Blog, MSDN articles and SDK documentation that go into depth on this subject. I definitely recommend hoc site.

</finem>

Scribet ad mea blog.

Technorati Tags:

Integrare SharePoint amet Workflows cum Web Services

2 Restituo

Ego fuerit ludens circa cum consuetudinem actus SharePoint amet enim tempus (hic enim detailed effercio, si quod utilitatis vobis).

In current project, we need to do some fairly heavy lifting and we want to use declarative SPD workflow to manage the associated business process.

Longum brevi, 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.

Hic in signature:

 publica filum Dispatcher(
        Manuductione WebID, // Transierunt per runtime environment
        Manuductione SiteID, // Transierunt per runtime environment
        filum ListID, // Transierunt per RTE (Cur hoc filum, non a manuductione)
        int ListItemID, // Transierunt per RTE.
        filum XmlMessage) // Transierunt per user ut declaravit in SPD.

Hoc Aenean quod nos possit ad momenti workflow notitia, sicut site, album ID, etc. 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!

Miserabile, hoc est scilicet unum modo tessera ad "Loosey Goosey" anti-exemplar terra, but it’s better than hitting a brick wall 🙂

Est an anti-exemplar si facere etiam licet scire suus an anti-exemplar?

I hope to wrap this inside Codeplex in the near future. If you’re interested in me doing so, dare me MOVEO (email aut relinquat comment) and I’ll be that more enthusiastic about doing it 🙂

</finem>

Scribet ad mea blog.

Technorati Tags: ,

Dominica Funny: “Miror si password est …”

1 Respondere

Nuper emit prandium frater (more) and we ended up talking about funny things that we did at our respective colleges. At my alma mater, Mollis 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.

Duo meus ventus memorias referre ad meum bonum amicus, Gabe. He had made the terrible mistake of telling people his freshman year that "I’m a freshman, sed mihi Sophomore stantem" debitum ad variis proficiebat collocatione classes ipse erat, etc. Many of us were similarly situated but we didn’t talk about it so much. His senior year, cum introduxit eum ad populum, we’d say "This is Gabe. He’s a Senior, sed habet Sophomore stantem ".

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, utique, ludere.

Nos non sicut computer-inops veniam ad tantum nostrum ventus quae ad esset ad telnet ad buxum sunt in et currere X-oculus 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. Conare non clare ridere cum fectum miserum X oculum claudere conatur post X oculum et sub eius flatu murmurans.

We also played X-trek on those boxes. Id, tibi ad download principium, 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, re-aedificavit et tunc perdidit Gabe altera tempore lusimus.

Gabe etiam a ingens fan de a TV ostende dicitur Blake scriptor 7. I had never seen it, Sed non dui a libero asseverantes. Who is the superior show. Argumenta nonnumquam calefieri

Unum die, 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, "Ego ad coniecto vestri password nunc, Gabe." "Yeah, ius" was his answer. I then logged in, ingressus eius user id, conversus ad coram, dactylographabam et dixit ex magna, "Miror si scriptor B-L-A-K-E-VII" ? Touch typing has never paid off as handsomely as it did that day.

Proxima septimana (aut mox): More computer room antics from college.

Tu quis ad participes? Leave a comment or email me and I’ll publish them here.

</finem>

Scribet ad mea blog.

Technorati Tags: