Nyaraka za kila mwezi: Januari 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, kwa mfano, 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, tafadhali niambie.

Kuishi maeneo ya hali ya kuwaambia mimi: taarifa hits kwa siku, 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 jukwaa kiungo, nk).

Katika baadhi ya njia, a "hit" ni dhahiri. Kama wewe ni kusoma sentensi hii sasa hivi, umefanya karibu shaka kusajiliwa kama wimbo.

RSS is a little confusing. On one hand, I see individual RSS hits all day long. Lakini, I also see RSS "sweeps". A sweep is when I see 20 au 30 RSS hits all within a one or two second window. I assume these are automated things like google checking in on my site, labda watu wengine browsers … not sure. They are definitely some kind of automated process. I cannot tell, hata hivyo, 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 kwa siku ni automatiska.

Juu ya idadi!

Niliandika blog yangu ya kwanza kuingia kwenye Julai 27, 2007.

Nimeandika takriban 60 blog entries tangu hapo, zaidi ya 50 ambayo moja kwa moja kuhusiana na SharePoint.

Nilianza kuweka wimbo wa ya hits yangu katika spreadsheet ya kila siku katika mwisho wa Septemba.

Kila mwezi Huanza:

Wiki ya kwanza ya: Jumla ya Hits
Oktoba 1,234
Novemba 2,162
Desemba 3,071
Januari 2008 4,253

Jumla kwa Mwezi

Mwezi Jumla ya Hits
Oktoba 6,620
Novemba 11,110
Desemba 13,138

High Maji Marks

Aina Jumla ya Hits
Bora ya Siku 958
Bora Wiki 4,253
Jumla ya Hits Tangu Siku sifuri 42,438

Nina nia ya wengine’ stats. If you care to share yours in the comments, tafadhali kufanya!

</mwisho>

Tags technorati:

Sunday Morning Mapenzi: “Yeah, yeah, yeah. Blah, blah, blah.”

Kuhusu miaka sita iliyopita, zangu nne mwenye umri wa miaka mwana na mimi walikuwa ghorofani kuangalia Ugunduzi hisa "shark attacks" maalum (pengine hii moja). 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, kwa mfano, yoyote maalum hofu ya maji au payuka kitu muafaka kwa marafiki zake na pengine kusababisha mtoto rafiki yake wa mtandao kuja crashing chini.

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

Hivyo, 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, yangu sauti (ambao daima imekuwa sana 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. Hata hivyo, I had misinterpreted his excitement. He was not worried about the girl at all. Badala yake, wakati kupiga makofi mikono yake, yeye anasema mimi, "The sharks love it! It’s terrific. It’s wonderful. Its a DREAM COME TRUE!"

Nilidhani hii ilikuwa hilarious, but also very disturbing. Kwa upande mmoja, Nilifurahi — hata kiburi kidogo — kwamba angeweza kuwa na hisia kali empathic, cross-species though they may be. As humans, we need to develop our "empathic muscles" hivyo kusema au utasikia kuishia kama hii 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.

Hiyo si neno vile rahisi kuelezea kwa miaka minne ya zamani, but I gave it a try. When I think of the word "paradigm", Thomas Kuhn is never far from my thoughts. Mimi kusoma Muundo wa mapinduzi ya kisayansi nyuma katika Lafayette na kwa bora au mbaya, the word "paradigm" is pregnant with extra meaning for me. (Sort of like the word "contact" baada ya kusikia Simu Kisasa sauti niambie ambapo mimi naweza kuona kwamba movie [Nilidhani kitabu ilikuwa bora]; Mimi siku zote kusema kwa mwenyewe, "CONTACT!" whenever I see or hear someone say "contact").

Anyway, Mimi kujaribu kueleza kwake ufafanuzi Kuhnian, 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." Bila shaka, huwezi kuzungumza kama na umri wa miaka minne, so I’m trying to successively define it to smaller pieces and feeling rather proud of myself as I do so. (Mimi tu alijua kwamba mtu nje ya chuo bila huduma ya kwamba nilikuwa kusoma Kuhn!).

I’m just warming to the task when he interrupts me. Waving his hand katika mwelekeo yangu ya jumla na kamwe kuchukua macho yake mbali ya mashambulizi ya kikatili mwingine shark, yeye tu anasema, "Yeah, yeah, yeah. Blah, blah, blah.".

So much for that 🙂

Katika hatua hiyo, Niliamua kukimbia, rhetorically akizungumza, kukaa nyuma, na kufurahia kuangalia binadamu mashambulizi papa na mtoto wangu.

</mwisho>

Tags technorati:

Kubadili View View Kulingana na ID mtumiaji Katika kidato InfoPath

Tulikuwa na maendeleo ya fomu InfoPath pamoja na maoni mbalimbali ya kusaidia kukodisha mpya / on-boarding process. When the company hires a new person, Idara ya IT na makundi mengine ya haja ya kuchukua hatua (kuanzisha mishahara, kuwawezesha kupata maombi ya mwafaka, Machapisho ya dawati, nk). We use on form but a different view of the form for each of those functions.

Wakati kampuni hii, zaidi ya watu waliohusika katika mchakato wa biashara ni IT-savvy, hivyo wakati wao kupata fomu, their default view is a "menu" view with buttons that direct them to their specific function. Hata hivyo, we needed to simplify things for the new hire’s direct manager. This person should not see any of the IT related stuff. Kwa kweli, yeye anapaswa kuona moja tu mtazamo wa fomu na hata kuwa na chaguo kuona maoni ya wengine.

Katika kesi yetu, kwamba akaunti ya moja kwa moja meneja wa moja kwa moja amefungwa kwa hisani fomu ya kuwasiliana selector (which I am always wanting to call a "people picker" kwa sababu baadhi ya).

hatua ni kama ifuatavyo:

1. Katika hali ya kubuni, kwenda Tools -> Fomu Chaguzi -> Kufungua na Ila.

2. Select "rules".

3. Create a new rule whose action is "switch to view" na ambao hali leverages jina la Mtumiaji() kazi.

jina la Mtumiaji() returns the "simple" user name without the domain. If I log into SharePoint with credentials "domain\pagalvin", jina la Mtumiaji() 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 (katika mazingira yangu anyway) anarudi domain na user ID, as in "domain\pagalvin". This prevents us from doing a straight-forward equality condition since AccountID ("domain\pagalvin") kamwe sawa na jina la Mtumiaji() ("pagalvin").

We can get around this using the "contains" operator: AccountID ina jina la Mtumiaji().

Tunaweza kuchukua ni zaidi na kabla ya pend uwanja ngumu-coded mbele ya jina la Mtumiaji() kazi ya kupata usawa wetu kuangalia na kuondokana na hatari ya chanya ya uongo juu ina operator.

We would have REALLY like to automatically switch view for other users based on their AD security group membership. Kwa mfano, when a member of the "IT Analytics" kikundi wanapata fomu, 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", kupita ni jina la Mtumiaji() and return back true or false. Does anyone have any other, wajanja zaidi wazo? Is there any SharePoint function we can leverage from InfoPath to make that determination?

</mwisho>

Tags technorati:

Ajali Kuongeza Kanuni ya kidato InfoPath; Makusudi Kuondoa Ni

Wakati wa kufanya kazi na vifungo kwenye fomu, we often add rules. You access the rules editor from the properties of the button.

Wakati kubonyeza kuzunguka haraka, it’s easy to accidentally click on "Edit Form Code" instead of "Rules …".

mara ya kwanza mimi hii, I canceled out of the code editor. Hata hivyo, wakati nilijaribu kuchapisha fomu wakati baadaye kidogo, it required that I publish as an "Administrator-approved form template (juu)". 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.

Leo, I did it again. Wakati huu, Mimi nilikuwa na muda kidogo zaidi juu ya mikono yangu na kugundua kwamba unaweza kwa urahisi tengua hii.

Kwenda:

Zana -> Fomu Chaguzi -> Programu: "Remove Code"

Haina kupata rahisi zaidi kuliko kwamba.

</mwisho>

Tags technorati: ,

Kima cha chini cha Usalama Required Kwa Fomu 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. (Hii ni mpya-kuajiri juu-bweni fomu kutumiwa na Rasilimali kwamba yazindua workflow).

Kufikia lengo, Mimi umba kuundwa mbili ngazi ruhusa mpya ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, update" user and a separate "update only" mtumiaji. The mechanics all worked, but it turned out to be a little more involving than I expected. (Kama wewe kujisikia shaky kidogo juu ya SharePoint ruhusa, angalia hii baada ya blog). 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, Nilifanya zifuatazo:

  1. Kujenga mpya ruhusa ngazi.
  2. Wazi mbali chaguzi zote.
  3. Selected only the following from "List permissions":
    • Hariri Items
    • View Items
    • View za Maombi

Kuchagua njia hizo inaruhusu mtumiaji update fomu, lakini si kujenga.

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, lakini zinageuka ni.

Create-and-Update was even stranger. I followed the same steps, 1 kupitia 3 juu ya. I had to specifically add a "Site Permission" chaguo: "Use client integration features". Tena, maelezo kuna haina kufanya hivyo kuonekana kama inavyopaswa zinazohitajika kwa ajili ya fomu InfoPath, lakini kuna ni.

</mwisho>

Tags technorati: ,

Kwamba “Katika-Kati” Hisia; Uchunguzi juu ya SharePoint Consulting

Cha kusikitisha, 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, kama kawaida 🙂 Sasa mimi ni kati ya miradi, muda maalum kwa ajili ya wafanyakazi washauri kama mwenyewe (kinyume na wagombea binafsi ambaye ni lazima kwa kawaida wanaishi katika hofu ya daima ya in-kati ya wakati 🙂 ). We staff consultants fill this time in various ways: Kufanya kazi na watu mauzo ya kuandika mapendekezo; kujaza kwa mtu au inaunga mkono juu ya mtu juu ya kazi hii au isiyo ya kawaida; studying; Mabalozi :). It’s hard to plan more than a few days in advance. At times like this, wakati mimi kuwa na kidogo ya muda juu ya mikono yangu, 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. Hata hivyo, wewe kula chakula cha mchana na mteja, kuchukua nje kwa chakula cha jioni na / au kwa ajili ya vinywaji, kununua cookies kwa ajili ya timu ya, kwenda kwenye anaendesha kahawa, kutoa / kupokea kadi likizo — 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. Kwa upande mwingine, you’re a baby. On day zero, washauri hawajui majina, the places or the client’s lingo. Most times, washauri kamwe kujifunza yote.

Wakati mambo kwenda vizuri, 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, kamwe kutambua wao ni kufanya hivyo.

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, utawala, Jamii, msingi maudhui aina, nk. na katika mambo mengi, kiasi na ya muda mrefu, 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, kutekeleza uhusiano BDC kwa PeopleSoft, ilianzisha workflow haki tata na SharePoint Designer, touched on basic KPI’s and more. A proper phase two would extend all of that with extensive, karibu kuenea BDC, kweli nice workflow, faini tuned na bora tafuta, kumbukumbu za kituo cha, kuutumia huduma na pengine muhimu zaidi, reaching out to other business units. Lakini, siyo kuwa kwa ajili yangu, and that’s sad.

Kulingana na uzoefu huu wa hivi karibuni, 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, bila shaka.

That’s the consultant’s life and all of these little complaints are even worse in a SharePoint engagement. Kama nimepata iliyoandikwa kabla ya, 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, unaweza kuona njia nyingi kwamba SharePoint inaweza kusaidia kampuni ya kuwa na ufanisi zaidi, kuokoa muda, kufanya mambo vizuri… but you don’t always get to do them.

Mimi mara nyingi kuangalia nyuma kwa kazi yangu ya kwanza nje ya chuo, 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, hata hivyo, 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! 🙂

Licha ya mood yangu soda, Siwezi kufikiria mahali nisingependa kuwa (isipokuwa katika pwani ya joto na usambazaji mzuri wa roho).

Siwezi kusubiri kupata ilianza kutekelezwa ijayo biashara SharePoint mradi.

(Apropos ya kitu chochote, Mimi aliandika zaidi ya kuingia hii blog juu ya NJ Transit basi. I don’t think I made any friends, lakini moja UNAWEZA blogu kwenye basi 🙂 )

</mwisho>

Tags technorati:

Jumapili Mapenzi: “Wao uko Si KWAMBA Bad”

Nyuma karibu 1999, Mimi mara matumizi mengi ya wiki nje katika Santa Barbara, CA, kufanya kazi kwa ajili ya mteja, 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. Mahali fulani kwenye mstari, I coined a phrase, "special fear", as in "Samantha has special fears." She as a special fear of "bugs", which to her are not flies or ladybugs, but rather microbes. She’s afraid of this or that virus or unusual bacteria afflicting our son, or me, but never really herself. (She is also specially afraid of vampires, miniature evil dolls (especially clowns) and submarine accidents; she has out-grown her special fear of people dressed in Santa Claus outfits).

One day, 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.

That night, 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 it out the window."

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 a loud voice: "My God! CAN THEY TAKE OVER YOUR MIND???"

S: Literally reassuring me: "No, they’re not THAT bad."

</mwisho>

Tags technorati:

Haraka na Easy: Moja kwa moja Open InfoPath kidato Kutoka SharePoint Designer Email

UPDATE: Madjur Ahuja points out this link from a newsgroup discussion: 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, wanaweza bonyeza kiungo kutoka email na kwenda moja kwa ajili ya InfoPath.

This monster URL construction works for me:

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

Replace the bolded red text with the name of the form, as shown in the following screenshot:

picha

Note that there is a lot of hard-coded path in that 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, view the source of the email and you’ll see everything you need to include.

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.

</mwisho>

Tags technorati: