Месечни архиви: Јануари 2008

Блог статистика

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, на пример, 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, молам да ми кажете.

Live Spaces статус кажи ми: вкупно хитови за ден, 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 форум линк, итн).

На некој начин, a "hit" Очигледно е. Ако ја читаш оваа реченица сега, сте речиси сигурно регистрираат како еден хит.

RSS is a little confusing. On one hand, I see individual RSS hits all day long. Но, I also see RSS "sweeps". A sweep is when I see 20 или 30 RSS hits all within a one or two second window. I assume these are automated things like google checking in on my site, можеби другите луѓе прелистувачи … не се сигурни. They are definitely some kind of automated process. I cannot tell, сепак, 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 хитови на ден се автоматизирани.

За да на броеви!

Напишав мојот прв блог запис на 27 јули, 2007.

Имам напишано околу 60 блог записи, бидејќи тогаш, повеќе од 50 од кои директно се однесуваат на SharePoint.

Почнав да ги пратите на на моите хитови во табела на дневна основа до крајот на септември.

Месечен Почеток:

Првата недела од: Вкупно Посети
Октомври 1,234
Ноември 2,162
Декември 3,071
Јануари 2008 4,253

Вкупно по месец

Месец Вкупно Посети
Октомври 6,620
Ноември 11,110
Декември 13,138

High Water марки

Тип Вкупно Посети
Најдобриот ден 958
Најдобра недела 4,253
Вкупно Посети Од Ден Нула 42,438

Јас сум заинтересиран во други’ stats. If you care to share yours in the comments, Ве молиме да!

</крајот>

Недела утро Смешни: “Да, Да, Да. Бла, бла, бла.”

За шест години, моите четири-годишен син и јас бевме горе гледа Дискавери канал "shark attacks" специјални (можеби ова). 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, на пример, било специјални стравувањата на вода или издавам тајна нешто несоодветно со неговите пријатели и евентуално да предизвика неговата бебе пријател мрежа да дојде паѓа надолу.

Discovery handles these kinds of subjects very well. It’s not about creating a страв од нешто, but rather to show how unusual it is for sharks to attack humans.

Така, 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, мојот звук (кој секогаш бил исклучително напнат и онака), 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. Сепак, I had misinterpreted his excitement. He was not worried about the girl at all. Наместо, додека плескање со рацете, тој ми кажува, "The sharks love it! It’s terrific. It’s wonderful. Its a DREAM COME TRUE!"

Мислев дека ова беше смешен, but also very disturbing. Од една страна, Ми беше мило — дури и малку горд — дека би можеле да имаат силна емпатичен чувства, cross-species though they may be. As humans, we need to develop our "empathic muscles" така зборуваат или ќе заврши како овој човек 🙂 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.

Тоа не е толку лесен збор да се опише на четири години, but I gave it a try. When I think of the word "paradigm", Томас Кун is never far from my thoughts. I read Структура на научна револуција назад во Лафајет и за подобро или за полошо, the word "paradigm" is pregnant with extra meaning for me. (Sort of like the word "contact" по сослушувањето на филм Телефон глас да ми кажете каде можам да видам тој филм [Мислев дека книгата е подобро]; Јас секогаш велам, "CONTACT!" whenever I see or hear someone say "contact").

Како и да е, Се обидувам да се објасни му на 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." Се разбира, не можете да зборувате како на четири-годишен, so I’m trying to successively define it to smaller pieces and feeling rather proud of myself as I do so. (Јас само знаеше дека некој надвор од колеџ би се грижеле што сум ја прочитал Кун!).

I’m just warming to the task when he interrupts me. Waving his hand во мојата општа насока и никогаш не земајќи ги неговите очи излета уште еден брутален ајкула напад, тој само вели, "Yeah, Да, Да. Бла, бла, blah.".

So much for that 🙂

Во тој момент, Решив да бега, реторички зборува, седат назад, и уживајте во гледањето ајкули напад луѓето со мојот син.

</крајот>

Technorati Тагови:

Се префрлат Види Види Врз основа User ID во Еден InfoPath формулар

Ние имавме развиено InfoPath формулар со повеќе пати да ја поддржи новиот вработен / on-boarding process. When the company hires a new person, Секторот за ИТ и други групи треба да преземат акција (постави платен список, овозможи пристап до соодветни апликации, лоцирање на маса, итн). We use on form but a different view of the form for each of those functions.

Во оваа фирма, повеќето од луѓето вклучени во бизнисот процес се ИТ-чувство, па кога тие пристапите на форма, their default view is a "menu" view with buttons that direct them to their specific function. Сепак, we needed to simplify things for the new hire’s direct manager. This person should not see any of the IT related stuff. Всушност, таа треба да се види само еден поглед на формата, а не дури и да има опција да се види другата пати.

Во нашиот случај, таа сметка директен менаџер е директно поврзана со форма учтивост на контактирајте селектор (which I am always wanting to call a "people picker" поради некоја причина).

Чекорите се како што следува:

1. Во дизајнот на владата, одете на Tools -> Форма Опции -> Отворете и Save.

2. Select "rules".

3. Create a new rule whose action is "switch to view" и чија состојба Нотингем корисничкото име() функција.

корисничко име() returns the "simple" user name without the domain. If I log into SharePoint with credentials "domain\pagalvin", корисничко име() 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 (во мојата средина во секој случај) враќа на доменот и кориснички ID, as in "domain\pagalvin". This prevents us from doing a straight-forward equality condition since AccountID ("domain\pagalvin") никогаш не ќе се изедначи корисничко име() ("pagalvin").

We can get around this using the "contains" оператор: AccountID содржи корисничко име().

Ние може да потрае понатаму и пред-Pend хард-кодирани домен во предниот дел на корисничко име() функција да добие нашата еднаквост провери и да ги елиминираат ризикот од лажно позитивни на содржи операторот.

We would have REALLY like to automatically switch view for other users based on their AD security group membership. На пример, when a member of the "IT Analytics" група пристапи форма, 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", Поминете го корисничкото име() and return back true or false. Does anyone have any other, повеќе умна идеја? Is there any SharePoint function we can leverage from InfoPath to make that determination?

</крајот>

Technorati Тагови:

Случајно Додавање законик до InfoPath формулар; Намерно Тоа Отстранување

Кога работите со копчињата на образец, we often add rules. You access the rules editor from the properties of the button.

Кога кликнување околу брзо, it’s easy to accidentally click on "Edit Form Code" instead of "Rules …".

Прв пат Го направив ова, I canceled out of the code editor. Сепак, when I tried to publish the form a little while later, it required that I publish as an "Administrator-approved form template (advanced)". 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.

Денес, I did it again. Овој пат, I had a little more time on my hands and found that you can easily undo this.

Оди до:

Tools -> Форма Опции -> Програмирање: "Remove Code"

It does not get much easier than that.

</крајот>

Technorati Тагови: ,

Минимум безбедност потребни за 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. (Ова е новиот вработи он-интернат форма се користи од страна на човечките ресурси кои започна работното).

Да ја исполнат таа цел, Јас создаде создал две нови нивоа на дозвола ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, ажурирање" user and a separate "update only" корисникот. The mechanics all worked, but it turned out to be a little more involving than I expected. (Ако сметаш дека малку несигурни на SharePoint дозволи, проверете го овој блог пост). 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, Го направив следниве:

  1. Се создаде нов ниво на дозволи.
  2. Расчистуваме сите опции.
  3. Selected only the following from "List permissions":
    • Измени Теми
    • Прикажи Теми
    • Прикажи ги Примена страници

Изборот овие опции овозможува на корисникот да се ажурира форма, но не го создаде.

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, но излезе дека е.

Create-and-Update was even stranger. I followed the same steps, 1 преку 3 погоре. I had to specifically add a "Site Permission" опција: "Use client integration features". Повторно, описот таму не направи да изгледа како тоа треба да се бара за InfoPath формулар, но тоа е.

</крајот>

Technorati Тагови: ,

Дека “Во-помеѓу” Чувство; Набљудувања на SharePoint Консалтинг

За жал, 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, посебно време за вработените консултанти како мене (as opposed to independents who must normally live in perpetual fear of in-between time 🙂 ). 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; Блогирањето :). 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. Сепак,, 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. Од друга страна, 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.

Кога работите одат добро, 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, никогаш не сфаќајќи тие тоа го прават.

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, владеење, таксономија, основни типови содржини, итн. и во многу аспекти, количини на долгите, 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. Но, 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, се разбира.

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, сепак, 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, but one CAN blog on the bus 🙂 )

</крајот>

Technorati Тагови:

Недела Смешни: “Тие не се толку лош”

Назад во близина 1999, Јас бев трошење многу недели надвор во Санта Барбара, CA, работи за клиент, 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. Некаде по должината на линијата, Јас скова фразата, "special fear", as in "Samantha has special fears." She as a special fear of "bugs", што со неа не се лета или Ladybugs, but rather microbes. She’s afraid of this or that virus or unusual bacteria afflicting our son, или ме, but never really herself. (Таа е, исто така, специјално плаши од вампири, минијатурни зло кукли (особено кловнови) и подморница несреќи; таа е надвор порасна нејзиниот посебен страв од луѓе облечени во Дедо Мраз облека).

Еден ден, 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.

Таа ноќ, 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, Јас го flicked низ прозорецот."

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: Со повишен глас: "My God! CAN THEY TAKE OVER YOUR MIND???"

S: Буквално ме убедува: "No, тие не се толку лоши."

</крајот>

Technorati Тагови:

Брз и лесен: Отвори го автоматски InfoPath формулар Од SharePoint Designer-пошта

Ажурирање: 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, тие можат да кликнат на линкот од пораката и одат директно на 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:

сликата

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.

</крајот>

Technorati Тагови: