Штомесячны архіў: Студзень 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-статус прастор скажы мне: Усяго паказаў на працягу дня, 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, можа быць, чужыя браўзэры … not sure. 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.

Я пачаў сачыць за маёй хітоў у электронную табліцу на штодзённай аснове ў канцы верасня.

Штомесячныя Starts:

Першы тыдзень: Усяго запытаў
Кастрычнік 1,234
Лістапада 2,162
Снежань 3,071
Студзень 2008 4,253

Усяго па месяцах

Месяц Усяго запытаў
Кастрычнік 6,620
Лістапада 11,110
Снежань 13,138

Высокія ацэнкі вады

Тып Усяго запытаў
Лепшы дзень 958
Лепшая тыдзень 4,253
Усяго запытаў з нулявы дзень 42,438

Я зацікаўлены ў іншыя’ stats. If you care to share yours in the comments, калі ласка!

</канец>

Technorati Тэгі:

Sunday Morning Смешныя: “Так, ды, ды. Глупства, глупства, бла.”

Каля шасці гадоў таму, my four-year-old son and I were upstairs watching a Discovery channel "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, напрыклад, любы 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.

Так, 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. Аднак, I had misinterpreted his excitement. He was not worried about the girl at all. Замест, 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. З аднаго боку, 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. Я чытаю 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").

У любым выпадку, 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." Вядома, 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, ды, ды. Глупства, глупства, 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.

</канец>

Technorati Тэгі:

Пераключыць выгляд прадстаўлення на аснове ідэнтыфікатар карыстальніка ў формы 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.

У гэтай кампаніі, большасць людзей, якія ўдзельнічаюць у бізнес-працэсе з'яўляюцца IT-падкаваных, таму, калі яны атрымліваюць доступ да форме, 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. У рэжыме канструктара, перайдзіце ў меню Сэрвіс -> Параметры формы -> Адкрыць і Захаваць.

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 ўтрымлівае имя_пользователя().

Мы можам узяць яго, а таксама папярэдне залежаць жорстка дамена перад імем карыстальніка() функцыю, каб атрымаць нашу раўнавагу праверыць і выключыць рызыку ілжывых спрацоўванняў на аператара ўтрымлівае.

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 Form; Наўмысна выдалення яго

Пры працы з кнопкамі на форме, 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 Forms

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 Consulting

Сумна, 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, як звычайна 🙂 цяпер я паміж праектамі, адмысловае час для персаналу кансультантаў, як я, (у адрозненне ад незалежных, якія звычайна павінны жыць у пастаянным страху адзін ад аднаго ў часе 🙂 ). 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. Яшчэ, Вы ясьце абед з кліентам, узяць іх на вячэру і / або для напояў, купіць печыва для каманды, пайсці на каву трас, даць / атрымаць святочныя паштоўкі — 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, кансультанты не ведаюць імёнаў, the places or the client’s lingo. Most times, Кансультанты ніколі не пазнаць усё гэта.

Калі ўсё ідзе добра, 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, BDC рэалізацыі падлучэння да PeopleSoft, прадставіла даволі складаны працэс з SharePoint Designer, touched on basic KPI’s and more. A proper phase two would extend all of that with extensive, Амаль распаўсюджанай BDC, сапраўды добрых працоўных працэсаў, сапраўды вывераных і лепшага пошуку, Цэнтр запісаў, Службы Excel і, верагодна, самы важны, reaching out to other business units. Але, гэта не для мяне, and that’s sad.

Грунтуючыся на гэтым нядаўні вопыт, 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. Як я ўжо пісаў раней, 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, Вы можаце ўбачыць так шмат спосабаў, якімі SharePoint можа дапамагчы кампаніі стаць больш эфектыўнай, эканоміць час, зрабіць што-то лепш… but you don’t always get to do them.

Я часта ў думках вяртаюся да маёй першай працай з каледжа, 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, але адзін CAN блог на аўтобусе 🙂 )

</канец>

Technorati Тэгі:

Нядзеля Смешныя: “Яны не так ужо дрэнна”

Назад каля 1999, Я праводзіў шмат тыдняў у Санта-Барбары, Каліфорнія, працоўныя для кліента, 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", якія ёй не мухі або божыя кароўкі, 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, Я пстрыкнуў яго ў акно."

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 Email

АБНАЎЛЕННЕ: 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.

</канец>