maandelikse Argiewe: Januarie 2008

Cryoprobe

I thought some people might be interested in my blog’s statistics. You can use mine as a benchmark to compare your own.

I’m running my blog on windows live spaces. They collect stats for me and I don’t know any way to control that. It’s good as far as it goes, but it’s fairly limited in that I can’t do much actual analysis with it. I’d love, byvoorbeeld, to be able to generate a listing of my most frequently hit posts but I can’t do that without a prohibitive manual process. If someone knows better, asseblief vir my sê.

Live ruimtes status vertel my: Totale kere vir die dag, total hits for the week and total hits since day zero. It also tells me what people did to get to my blog (bijv. Google, MSDN forum skakel, ens.).

In sommige maniere, a "hit" is voor die hand liggend. As jy dit lees hierdie sin nou, jy het amper sekerlik geregistreer as 'n enkele treffer.

RSS is a little confusing. On one hand, I see individual RSS hits all day long. Maar, I also see RSS "sweeps". A sweep is when I see 20 of 30 RSS hits all within a one or two second window. I assume these are automated things like google checking in on my site, miskien ander mense se bruisers … not sure. They are definitely some kind of automated process. I cannot tell, egter, how many of my total hits are automated and how many have an actual human on the other side. I would guess at least 100 hits per dag is outomaties.

Op die nommers!

Ek het my eerste blog inskrywing op 27 Julie, 2007.

Ek het ongeveer geskryf 60 blog inskrywings sedertdien, meer as 50 wat direk verband hou met SharePoint.

Ek het begin om tred te hou van my treffers in 'n sigblad op 'n daaglikse basis aan die einde van September.

Maandelikse Vanaf:

Eerste week van: Totale kere
Oktober 1,234
November 2,162
Desember 3,071
Januarie 2008 4,253

Totale per maand

Maand Totale kere
Oktober 6,620
November 11,110
Desember 13,138

Hoë Water Marks

Tipe Totale kere
Beste dag 958
Beste Week 4,253
Totale kere Sedert Day Zero 42,438

Ek is geïnteresseerd in ander’ stats. If you care to share yours in the comments, doen asseblief!

</einde>

Technorati Tags:

Sondagoggend Funny: “Ja, ja, ja. Blah, blah, blah.”

Sowat ses jaar gelede, my vier-jarige seun en ek is bo kyk na 'n Discovery-kanaal "shark attacks" spesiale (moontlik hierdie een). He was very young at the point and I was always worried what he might see on a show like this and how he might take it. I didn’t want him to develop, byvoorbeeld, 'n spesiale vrese van die water of klappen iets onvanpas aan sy vriende en moontlik veroorsaak dat sy baba vriend netwerk te kom gekraak.

Discovery handles these kinds of subjects very well. It’s not about creating a vrees van iets, but rather to show how unusual it is for sharks to attack humans.

So, we’re watching it and there is this one particularly scary attack involving a small girl. As Discovery is building the drama of the attack, my klank (wat nog altyd baie senuweeagtig in elk geval), is getting very excited. I make some noises about how unusual it is for sharks to attack people, and how bad the poor girl must feel. I’m trying to explain that people recover from these events and become stronger for it. Egter, I had misinterpreted his excitement. He was not worried about the girl at all. In plaas daarvan, terwyl klap sy hande, Hy sê vir my, "The sharks love it! It’s terrific. It’s wonderful. Its a DREAM COME TRUE!"

Ek het gedink dit was hilarious, but also very disturbing. Aan die een kant, Ek was bly — selfs 'n bietjie trots — dat hy het 'n sterk empatiese gevoelens, cross-species though they may be. As humans, we need to develop our "empathic muscles" so praat, of jy sal uiteindelik soos hierdie man 🙂 Aan die ander kant, he was feeling cross-species empathy toward a species who was exhibiting behavior inimical to his own. I was really struggling with this when the narrator used the word "paradigm". My son picked up on that and asked me what that meant.

That’s not such an easy word to describe to a four year old, but I gave it a try. When I think of the word "paradigm", Thomas Kuhn is never far from my thoughts. Ek lees The Structure of Scientific Revolutions back at Lafayette and for better or for worse, the word "paradigm" is pregnant with extra meaning for me. (Sort of like the word "contact" after hearing a Movie Phone voice tell me where I could see that movie [I thought the book was better]; I always say to myself, "CONTACT!" whenever I see or hear someone say "contact").

In elk geval, Ek probeer om te verduidelik aan hom 'n Kuhniaanse definisie, that it’s "a historical movement of thought" and that it’s a "way of thinking with a number of built-in assumptions that are hard to escape for people living at that time." Natuurlik, jy kan nie praat soos met 'n vier-jaar oud, so I’m trying to successively define it to smaller pieces and feeling rather proud of myself as I do so. (Ek het net geweet dat iemand buite van die kollege sal sorg dat ek Kuhn het gelees!).

I’m just warming to the task when he interrupts me. Waving his hand in my algemene rigting en nooit om sy oë uit 'n ander wrede haai-aanval, Hy sê net, "Yeah, ja, ja. Blah, blah, blah.".

Soveel daarvoor 🙂

Op daardie stadium, I decided to run away, rhetorically speaking, sit back, and enjoy watching sharks attack humans with my son.

</einde>

Technorati Tags:

Skakel skerm op grond van gebruikers ID in 'n Path vorm

Ons het 'n ontwikkelde 'n Path vorm 'n nuwe huur met verskeie standpunte te ondersteun. / on-boarding process. When the company hires a new person, die IT-departement en ander groepe nodig om aksie te neem (op die betaalstaat, in staat stel om toegang tot toepaslike programme, soek 'n lessenaar, ens.). We use on form but a different view of the form for each of those functions.

Op hierdie maatskappy, Die meeste van die mense wat betrokke is in die besigheid is IT-vaardig, so wanneer hulle toegang tot die vorm, hulle op die regte pad is 'n "menu" view with buttons that direct them to their specific function. Egter, we needed to simplify things for the new hire’s direct manager. This person should not see any of the IT related stuff. In werklikheid, sy moet net een siening van die vorm en nie eens 'n opsie om die ander mening te sien.

In ons geval, dat direkte bestuurder se rekening word direk gekoppel aan die vergunning van 'n kontak selector (wat ek wil altyd 'n "mense picker te roep" vir een of ander rede).

Die stappe is soos volg:

1. In die ontwerp af, Gaan na Tools -> Vorm opsies -> Oopmaak en stoor.

2. Kies "reëls".

3. Skep 'n nuwe reël wie se optrede is "skakel om te sien" en wie se toestand maak gebruik van die gebruikersnaam() funksie.

gebruikersnaam() gee die "eenvoudige" user name without the domain. If I log into SharePoint with credentials "domain\pagalvin", gebruikersnaam() return "kussings".

The contact selector provides three bits of information for a contact. The "AccountID" portion is most useful for this scenario. The only thing that makes this even a little bit of challenge is that the contact selector (in elk geval in my omgewing) gee die domein en gebruikers ID, as in "domain\pagalvin". This prevents us from doing a straight-forward equality condition since AccountID ("Domain kussing") sal nooit gelyk gebruikersnaam() ("Pillow").

Ons kan kry om die gebruik van die "bevat" operateur: AccountID bevat gebruikersnaam().

Ons kan dit verder en pre-pend 'n harde-gekodeerde gebied in die voorkant van die gebruikersnaam() funksie te kry gaan ons gelykheid en elimineer die risiko van 'n vals positief op die bevat operateur.

We would have REALLY like to automatically switch view for other users based on their AD security group membership. Byvoorbeeld, Wanneer 'n lid van die "IT Analytics" groep toegang tot die vorm, automatically switch to the IT Analytics view. We didn’t have time to implement it, maar my eerste gedagte is om 'n web te skep wat 'n metode soos "IsMemberOfActiveDirectorySecurityGroup", slaag dit die gebruikersnaam() and return back true or false. Does anyone have any other, meer slim idee? Is there any SharePoint function we can leverage from InfoPath to make that determination?

</einde>

Technorati Tags:

Per ongeluk Voeg Kode aan 'n Path vorm; Doelbewus verwydering van

By die werk met knoppies op 'n vorm, we often add rules. You access the rules editor from the properties of the button.

Wanneer te kliek rond vinnig, it’s easy to accidentally click on "Edit Form Code" instead of "Rules …".

Die eerste keer dat ek dit gedoen het, I canceled out of the code editor. Egter, wanneer ek probeer om die vorm na 'n rukkie later publiseer, it required that I publish as an "Administrator-approved form template (gevorderde)". I didn’t actually do any programming and I absolutely didn’t want to go through an unnecessary approval process. I was in a bit of panic at the time due to time constraints. To get past it, I simply restored a previous backup and continued. I had recently seen some blog posts about people going into the form’s XML to tweak things and I was afraid I would have to do something similar.

Vandag, I did it again. Hierdie keer, Ek het 'n bietjie meer tyd op my hande en gevind dat jy dit maklik kan maak dit ongedaan.

Gaan na:

Gereedskap -> Vorm opsies -> Programmering: "Remove Code"

Dit raak nie veel makliker as dit.

</einde>

Technorati Tags: ,

Minimum vereiste sekerheid Path Vorms

I needed to meet a security requirement for an InfoPath form today. In this business situation, a relatively small number of individuals are allowed to create a new InfoPath form and a much wider audience are allowed to edit it. (Dit is 'n nuwe-huur op-koshuis te gebruik wat deur menslike hulpbronne wat begin met 'n workflow).

Daardie doel te voldoen, Ek het geskep twee nuwe toestemming vlakke ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, werk" user and a separate "update only" gebruiker. The mechanics all worked, but it turned out to be a little more involving than I expected. (As jy voel 'n bietjie wankelrig op SharePoint regte, check hierdie blog post). The required security configuration for the permission level was not the obvious set of granular permissions. To create an update-only permission level for an InfoPath form, Ek het die volgende:

  1. Skep 'n nuwe toestemming vlak.
  2. Duidelik weg alle opsies.
  3. Selected only the following from "List permissions":
    • Wysig Items
    • View Items
    • Sien Aansoek Pages

Kies hierdie opsies kan 'n gebruiker 'n vorm by te werk, maar nie skep dit.

The trick was to enable the "View Application Pages". There isn’t any verbage on the permission level that indicates that’s required for update-only InfoPath forms, maar blyk dit.

Create-and-Update was even stranger. I followed the same steps, 1 deur 3 bo. I had to specifically add a "Site Permission" opsie: "Use client integration features". Weer, Die beskrywing is daar nie maak dit lyk soos dit behoort te wees wat nodig is vir 'n Path vorm, maar daar is dit.

</einde>

Technorati Tags: ,

Dit “In-Between” Voel; Waarnemings op SharePoint Consulting

Ongelukkig, phase one of my last project has come to a close and the client has opted to move ahead by themselves on phase two. We did our job too well, as usual 🙂 I’m now between projects, 'n spesiale tyd vir personeel konsultante soos myself (as opposed to independents who must normally live in perpetual fear of in-between time 🙂 ). We staff consultants fill this time in various ways: Werk met verkope folk voorstelle te skryf; vul in vir iemand of back-up van 'n persoon op hierdie of wat vreemd werk; studying; Blogging :). It’s hard to plan more than a few days in advance. At times like this, terwyl ek 'n bietjie van die tyd op my hande, I like to reflect.

I’m almost always sad to leave a client’s campus for the last time. We consultants form a peculiar kind of relationship with our clients, unlike your typical co-worker relationship. There’s the money angle — everyone knows the consultant’s rate is double/triple or even more than the client staff. You’re a known temporary person. As a consultant, you’re a permanent outsider with a more or less known departure date. Tog, jy eet middagete saam met die kliënt, neem hulle uit vir ete en / of vir drankies, koop koekies vir die span, gaan op koffie lopies, gee / ontvang vakansie kaarte — all the kinds of things that co-workers do. On one hand, you’re the adult in the room. You’re an expert in the technology which puts you in a superior position. Aan die ander kant, you’re a baby. On day zero, konsultante ken nie die name, the places or the client’s lingo. Most times, konsultante nooit leer om dit alles.

Wanneer dinge goed gaan, you become very well integrated with the client’s project team. They treat you like a co-worker in one sense, and confidant in another. Since we don’t have a manager-style reporting relationship with the client, the project team often feels a little free to air their dirty laundry. They let their barriers down and can put the consultant into an awkward position, nooit besef dat hulle dit doen.

Consultants often don’t get to implement phase two and that never gets easy for me. I think this is especially hard with SharePoint. Phase one of of your typical SharePoint project covers setup/configuration, bestuur, taksonomie, basiese inhoud tipes, ens.. en in baie opsigte, neerkom op 'n lang, extremely detailed discovery. That’s how I view my last project. We did all the basic stuff as well as execute some nice mini-POC’s by extending CQWP, implementering van BDC verbindings te PeopleSoft, het 'n redelik komplekse workflow met SharePoint Designer, touched on basic KPI’s and more. A proper phase two would extend all of that with extensive, byna deurdringende BDC, baie mooi workflow, verfyn en beter soek, rekords sentrum, blink dienste en waarskynlik die belangrikste, reaching out to other business units. Maar, dit is nie vir my, and that’s sad.

Op grond van hierdie onlangse ondervinding, I think it’s fair to say that a proper enterprise SharePoint implementation is a one year process. It could probably legitimately run two years before reaching a point of diminishing returns. Details matter, natuurlik.

That’s the consultant’s life and all of these little complaints are even worse in a SharePoint engagement. Soos ek geskryf het voordat, SharePoint’s horizontal nature brings you into contact with a wide array of people and business units. When you’re working with so many people, kan jy sien so baie maniere wat SharePoint kan help om die maatskappy meer doeltreffend, tyd bespaar, dinge beter te doen… but you don’t always get to do them.

Ek het dikwels kyk terug na my eerste werk van die kollege, before starting a consulting career 1995. We did get to do a phase two and even a phase three. Those were nice times. On the downside, egter, that means that that would mean a lot of routine stuff too. Managing site security. Tweaking content types. Creating views and changing views. Dealing with IE security settings. Restoring lost documents. Blech! 🙂

Ten spyte van my melancholie stemming, Ek kan nie dink aan 'n plek waar ek wil eerder (behalwe op 'n warm strand met 'n mooi aanbod van geeste).

Ek kan nie wag om te begin geïmplementeer om die volgende onderneming SharePoint projek.

(Na aanleiding van niks, Ek het die meeste van hierdie blog inskrywing op 'n NJ Transit bus. I don’t think I made any friends, but one CAN blog on the bus 🙂 )

</einde>

Technorati Tags:

Sondag Funny: “Hulle is nie so sleg nie”

Terug naby 1999, Ek het spandeer baie weke in Santa Barbara, CA, werk vir 'n kliënt, leaving my poor wife back here in New Jersey alone. I dearly love my wife. I love her just as much today as I did when she foolishly married me 1,000 years or so ago. Iewers langs die lyn, Ek geskep om 'n frase, "special fear", as in "Samantha has special fears." She as a special fear of "bugs", wat aan haar is nie vlieë of ladybugs, but rather microbes. She’s afraid of this or that virus or unusual bacteria afflicting our son, of my, but never really herself. (Sy is ook spesiaal bang vampiere, miniatuur bose poppe (veral narre) en ondersese ongelukke; Sy het uit-gegroei haar spesiale vrees vir mense geklee in Santa Claus uitrustings).

Een dag, my co-worker and I decided to drive up into the nearby mountains near Ohai. At one point, we got out of the car to take in the scene. When we got back into the car, I noticed that a tick was on my shoulder. I flicked out the window and that was it.

Daardie aand, I told her about our drive and mentioned the tick. The conversation went something like this:

S: "Oooo! Those are bad. They carry diseases."

P: "Well, Ek gewip dit by die venster uit."

S: "They are really bad though. They can get under your skin and suck blood and transfer bugs. You better check your hair and make sure there aren’t any in your head!"

P: In 'n groot stem: "My God! CAN THEY TAKE OVER YOUR MIND???"

S: Letterlik my gerus te stel: "No, hulle is nie so sleg nie."

</einde>

Technorati Tags:

Vinnige en maklike: Outomaties oopmaak Path Vorm Van SharePoint Designer E-pos

UPDATE: Madjur ahuja punte uit hierdie skakel vanaf 'n nuusgroep bespreking: http://msdn2.microsoft.com/en-us/library/ms772417.aspx. It’s pretty definitive.

===

We often want to embed hyperlinks to InfoPath forms in emails sent from SharePoint Designer workflows. When users receive these emails, hulle kan op die skakel van die e-pos en gaan direk na die Path vorm.

Hierdie monster URL konstruksie werk vir my:

http://server/sites/departments/Technical Services/InformationTechnology/HelpDesk/_layouts/FormServer.aspx?XmlLocation=/sites/departments/Technical Services/InformationTechnology/HelpDesk/REC REM RED Forms/REC2007-12-18T11_33_48.xml&Source=http://server.corp.domain.com/sites/departments/Technical%20Services/InformationTechnology/HelpDesk/REC%20REM%20RED%20Forms/Forms/AllItems.aspx&DefaultItemOpen = 1

Vervang die vetgedrukt rooi teks met die naam van die vorm, soos in die volgende kiekie:

beeld

Let daarop dat daar is 'n baie harde-gekodeerde pad in die URL, as well as a URL-encoded component. If this is too hard to translate to your specific situation, try turning on alerts for the form library. Post a form and when you get the email, sien die bron van die e-pos en jy alles wat jy nodig het om te sluit sien.

Astute readers may notice that the above email body also shows a link that directly accesses the task via a filtered view. I plan to explain that in greater detail in a future post.

</einde>

Technorati Tags: