Arkivji ta 'Kull Xahar: Jannar 2008

Blog Stats

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, per eżempju, 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, jekk jogħġbok għidli.

Status spazji Live tell me: hits totali għall-jum, total hits for the week and total hits since day zero. It also tells me what people did to get to my blog (e.g. google, MSDN link forum, eċċ).

F'xi metodi, a "hit" huwa ovvju. Jekk qed taqra dan sentenza dritt issa, inti stajt kważi ċertament reġistrat bħala hit waħda.

RSS is a little confusing. On one hand, I see individual RSS hits all day long. Iżda, I also see RSS "sweeps". A sweep is when I see 20 jew 30 RSS hits all within a one or two second window. I assume these are automated things like google checking in on my site, maybe other people’s browsers … mhux ċert. They are definitely some kind of automated process. I cannot tell, madankollu, 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 kuljum huma awtomatizzati.

Fuq in-numri!

I kiteb l-ewwel dħul blog tiegħi fuq Lulju 27, 2007.

Ktibtu madwar 60 blog entries minn dakinhar, aktar minn 50 li direttament relatati ma SharePoint.

I bdew li jżommu rekord ta 'hits tiegħi spreadsheet fuq bażi ta' kuljum fl-aħħar ta 'Settembru.

Tibda kull xahar:

Ewwel ġimgħa ta ': Hits Total
Ottubru 1,234
Novembru 2,162
Diċembru 3,071
Jannar 2008 4,253

Totali bil-Xahar

Xahar Hits Total
Ottubru 6,620
Novembru 11,110
Diċembru 13,138

Marks Ilma għolja

Tip Hits Total
Best Jum 958
Best Ġimgħa 4,253
Hits totali Peress Jum Zero 42,438

Jien interessat li f'oħrajn’ stats. If you care to share yours in the comments, jekk jogħġbok do!

</aħħar>

Tags:

Ħadd filgħodu Funny: “Yeah, yeah, yeah. Blah, blah, blah.”

Madwar sitt snin ilu, my four-year-old son and I were upstairs watching a Discovery channel "shark attacks" speċjali (possibilment dan wieħed). 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, per eżempju, kwalunkwe special fears of the water or blab something inappropriate to his friends and possibly cause his baby friend network to come crashing down.

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

Allura, 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 son (who has always been extremely jumpy anyway), 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. Madankollu, I had misinterpreted his excitement. He was not worried about the girl at all. Minflok, while clapping his hands, he tells me, "The sharks love it! It’s terrific. It’s wonderful. Its a DREAM COME TRUE!"

I thought this was hilarious, but also very disturbing. On the one hand, I was glad — even a little proud — that he could have strong empathic feelings, cross-species though they may be. As humans, we need to develop our "empathic muscles" so speak or you’ll end up like this guy 🙂 On the other hand, 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. Naqra 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").

Xorta waħda, I’m trying to explain to him a Kuhnian definition, 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." Of course, you can’t talk like to a four-year old, so I’m trying to successively define it to smaller pieces and feeling rather proud of myself as I do so. (I just knew that someone outside of college would care that I had read Kuhn!).

I’m just warming to the task when he interrupts me. Waving his hand in my general direction and never taking his eyes off another brutal shark attack, he just says, "Yeah, yeah, yeah. Blah, blah, blah.".

So much for that 🙂

At that point, I decided to run away, rhetorically speaking, sit back, and enjoy watching sharks attack humans with my son.

</aħħar>

Tags:

Jaqilbu View View Ibbażat fuq User ID f'forma InfoPath

Kellna żviluppat formola InfoPath bl-opinjonijiet multipli biex tappoġġja kiri ġdida / on-boarding process. When the company hires a new person, IT dipartiment u gruppi oħra jeħtieġu li jieħdu azzjoni (stabbilit payroll, jippermettu aċċess għall-applikazzjonijiet xierqa, jillokalizza desk, eċċ). We use on form but a different view of the form for each of those functions.

Fuq din il-kumpanija, maġġoranza tal-persuni involuti fil-proċess tan-negozju IT-sofistikati, hekk meta jaċċessaw il-formola, their default view is a "menu" view with buttons that direct them to their specific function. Madankollu, we needed to simplify things for the new hire’s direct manager. This person should not see any of the IT related stuff. Fil-fatt, hi għandha tara wieħed biss minħabba l-forma u lanqas l-għażla li tara l-opinjonijiet l-oħra.

Fil-każ tagħna, dak il-kont manager dirett huwa direttament marbut ma l-forma korteżija ta ' kuntatt selettur (which I am always wanting to call a "people picker" għal xi raġuni).

Il-passi huma li ġejjin:

1. Fil-modalità disinn, mur Tools -> Formola Għażliet -> Open u Save.

2. Select "rules".

3. Create a new rule whose action is "switch to view" u li l-kondizzjoni tiggwida l-Username() funzjoni.

Username() returns the "simple" user name without the domain. If I log into SharePoint with credentials "domain\pagalvin", Username() returns "pagalvin".

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 (fl-ambjent tiegħi xorta) jirritorna l-dominju u user ID, as in "domain\pagalvin". This prevents us from doing a straight-forward equality condition since AccountID ("domain\pagalvin") qatt se ugwali username() ("pagalvin").

We can get around this using the "contains" operatur: AccountID fih Username().

Aħna tista 'tieħu aktar u pre-pend domain hard-kodifikati quddiem il-username() jiffunzjonaw biex tikseb l-ugwaljanza tagħna kontroll u jeliminaw ir-riskju ta 'pożittiv falz fuq l-operatur fih.

We would have REALLY like to automatically switch view for other users based on their AD security group membership. Per eżempju, when a member of the "IT Analytics" grupp aċċessi l-forma, automatically switch to the IT Analytics view. We didn’t have time to implement it, but my first thought is to create a web service that would have a method like "IsMemberOfActiveDirectorySecurityGroup", tgħaddiha l-Username() and return back true or false. Does anyone have any other, aktar idea għaqlija? Is there any SharePoint function we can leverage from InfoPath to make that determination?

</aħħar>

Aċċidentalment Żieda Kodiċi li Formola InfoPath; Deliberatament tneħħih

Meta taħdem bl-buttuni fuq formola, we often add rules. You access the rules editor from the properties of the button.

Meta tikklikkja madwar malajr, it’s easy to accidentally click on "Edit Form Code" instead of "Rules …".

L-ewwel darba I ma 'dan, I canceled out of the code editor. Madankollu, meta I ppruvaw li tippubblika l-forma filwaqt li ftit aktar tard, it required that I publish as an "Administrator-approved form template (avvanzat)". 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.

Illum, I did it again. Din id-darba, I kellhom ftit aktar ħin fuq l-idejn tiegħi u sabet li inti tista 'faċilment teqred dan.

Mur:

Tools -> Formola Għażliet -> Programmazzjoni: "Remove Code"

Hija ma jiksbu ħafna eħfef minn dak.

</aħħar>

Sigurtà minima meħtieġa għall Formoli InfoPath

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. (Dan huwa ġdid-kiri forma on-imbark użata minn riżorsi umani li tniedi workflow).

Biex jintlaħqu dan l-għan, I ħolqot ħolqot żewġ livelli permess ġdid ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, jaġġornaw" user and a separate "update only" utent. The mechanics all worked, but it turned out to be a little more involving than I expected. (Jekk inti tħoss ftit dgħajfa fuq permessi SharePoint, check out dan 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, Jien għamilt dan li ġej:

  1. Oħloq livell permess ġdid.
  2. Ċar bogħod għażliet kollha.
  3. Selected only the following from "List permissions":
    • Edit Punti
    • View Partiti
    • Ara Pages Applikazzjoni

Għażla ta 'dawn l-għażliet jippermetti utent li taġġorna forma, iżda mhux joħolqu dan.

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, iżda jinstabx huwa.

Create-and-Update was even stranger. I followed the same steps, 1 permezz 3 hawn fuq. I had to specifically add a "Site Permission" għażla: "Use client integration features". Għal darb'oħra, id-deskrizzjoni hemm ma jagħmilha jidhru simili hi jmissha tkun meħtieġa għal forma InfoPath, iżda hemm hu.

</aħħar>

Li “Fil-Bejn” Tħossok; Osservazzjonijiet dwar SharePoint Consulting

Sfortunatament, 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, bħas-soltu 🙂 jien issa bejn il-proġetti, żmien speċjali għall-konsulenti persunal bħal myself (għall-kuntrarju indipendenti li normalment ikollu jgħixu fil-biża perpetwu ta fin-nofs żmien 🙂 ). We staff consultants fill this time in various ways: Working with sales folk to write proposals; filling in for someone or backing up a person on this or that odd job; studying; Blogging :). It’s hard to plan more than a few days in advance. At times like this, while I have a bit of time on my hands, 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. Madankollu, you eat lunch with the client, take them out to dinner and/or for drinks, buy cookies for the team, go on coffee runs, give/receive holiday cards — 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. Min-naħa l-oħra, you’re a baby. On day zero, consultants don’t know the names, the places or the client’s lingo. Most times, consultants never learn it all.

When things go well, 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, never realizing they are doing it.

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, governance, taxonomy, basic content types, eċċ. and in many respects, amounts to a lengthy, 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, implementing BDC connections to PeopleSoft, introduced a fairly complex workflow with SharePoint Designer, touched on basic KPI’s and more. A proper phase two would extend all of that with extensive, almost pervasive BDC, really nice workflow, fine tuned and better search, records center, excel services and probably most important, reaching out to other business units. Iżda, it’s not to be for me, and that’s sad.

Based on this recent experience, 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, tal-kors.

That’s the consultant’s life and all of these little complaints are even worse in a SharePoint engagement. As I’ve written before, 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, you can see so many ways that SharePoint can help the company become more efficient, save time, do things better… but you don’t always get to do them.

I often look back to my first job out of college, 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, madankollu, 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! 🙂

Despite my melancholy mood, I can’t imagine a place I’d rather be (except at a warm beach with a goodly supply of spirits).

I can’t wait to get started implemented the next enterprise SharePoint project.

(Apropos of nothing, I wrote most of this blog entry on an NJ Transit bus. I don’t think I made any friends, iżda wieħed CAN blog fuq ix-xarabank 🙂 )

</aħħar>

IL-ĦADD Funny: “Huma qed mhux ħażin”

Back qrib 1999, I kien infiq ħafna ġimgħat fl Santa Barbara, CA, jaħdmu għal klijent, 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. X'imkien matul il-linja, I maħluqa frażi, "special fear", as in "Samantha has special fears." She as a special fear of "bugs", li lilha mhumiex dubbien jew ladybugs, but rather microbes. She’s afraid of this or that virus or unusual bacteria afflicting our son, jew me, but never really herself. (Hija wkoll apposta jibża 'Vampires, pupi ħażen minjatura (speċjalment buffi) u inċidenti taħt il-baħar; hi l-kibret biża speċjali tagħha ta 'nies lebsin Santa Claus ħwejjeġ).

Ġurnata waħda, 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.

Dak il-lejl, 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, I flicked l-tieqa."

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: Fil b'leħen qawwi: "My God! CAN THEY TAKE OVER YOUR MIND???"

S: Litteralment rassikuranti me: "No, dawn mhux qed dik ħażina."

</aħħar>

Tags:

Quick u Easy: Formola InfoPath Awtomatikament Open Mill SharePoint Designer Email

UPDATE: Madjur Ahuja jirrimarka din ir-rabta minn diskussjoni newsgroup: 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, huma jistgħu ikklikkja fuq il-link tal-email u jmorru direttament għall-forma InfoPath.

Din il-kostruzzjoni URL monster jaħdem għalija:

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

Ibdel it-test aħmar bolded bl-isem tal-formola, kif muri fil-screenshot li ġejjin:

immaġni

Innota li hemm ħafna ta 'passaġġ hard-coded f'dak 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, tara l-sors ta 'l-email u tkun taf tara dak kollu li għandek bżonn biex tinkludi.

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.

</aħħar>