ყოველთვიური არქივი: იანვარი 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, გთხოვთ მითხრათ.

ცოცხალი ფართები სტატუსი მეუბნებოდა: სულ ნახვები დღისთვის, 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 ჰიტს დღეში არიან ავტომატიზებულია.

On to ნომრები!

მე დავწერე ჩემი პირველი ბლოგის შესვლის წლის 27 ივლისს, 2007.

მე არ წერია დაახლოებით 60 blog entries მას შემდეგ, ზე მეტი 50 რომლის პირდაპირ უკავშირდება SharePoint.

დავიწყე შენარჩუნება კვალს, ჩემი hits in ცხრილების ყოველდღიურად დასასრულს სექტემბერი.

ყოველთვიური სტარტები:

პირველ კვირას: ჯამური სტატისტიკა
ოქტომბერი 1,234
ნოემბერი 2,162
დეკემბერი 3,071
იანვარი 2008 4,253

სულ by თვე

თვე ჯამური სტატისტიკა
ოქტომბერი 6,620
ნოემბერი 11,110
დეკემბერი 13,138

მაღალი წყლის ნიშნების

გაცნობის ჯამური სტატისტიკა
საუკეთესო Day 958
საუკეთესო კვირა 4,253
ჯამური სტატისტიკა წლიდან Day Zero 42,438

მაინტერესებს სხვები’ stats. If you care to share yours in the comments, გთხოვთ,!

</ბოლო>

პროგრამები Tags:

კვირა დილა სასაცილო: “ჰო, yeah, yeah. Blah, წევრის, წევრის.”

დაახლოებით ექვსი წლის წინ, ჩემი ოთხი წლის შვილი მე და ფილმი თვალს დოკუმენტური "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, მაგალითად, ნებისმიერი სპეციალური შიში წყლის ან blab რაღაც შეუსაბამო მისი მეგობრები და შესაძლოა გამოიწვიოს მისი ბავშვი მეგობარს ქსელის მოვა crashing ქვემოთ.

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, yeah, yeah. 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.

</ბოლო>

პროგრამები Tags:

შეცვლა დათვალიერება ანკეტის საფუძველზე მომხმარებლის ID In InfoPath ფორმა

ჩვენ შემუშავებული InfoPath ფორმა მრავალი ჩვენებები მხარდასაჭერად ახალი დაქირავება / on-boarding process. When the company hires a new person, IT დეპარტამენტი და სხვა ჯგუფები უნდა მიიღონ ზომები (შეიქმნა სახელფასო, საშუალებას ხელმისაწვდომობის შესაბამისი განაცხადების, იქნებიან სამაგიდო, და ა.შ.). We use on form but a different view of the form for each of those functions.

ამ კომპანიის, ყველაზე მეტი ადამიანი ჩართული ბიზნეს პროცესის IT-savvy, ასე რომ, როდესაც ისინი წვდომის ფორმა, 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. სინამდვილეში, მან უნდა დაინახოს, მხოლოდ ერთი ხედი ფორმა და კი არ ვარიანტი, რომ ნახოთ სხვა შეხედულებების.

ჩვენს შემთხვევაში, რომ პირდაპირი მენეჯერის ანგარიშზე პირდაპირ უკავშირდება ფორმა გაცნობითი ხასიათის of დაუკავშირდით არჩევის (which I am always wanting to call a "people picker" რატომღაც).

ნაბიჯები შემდეგი რედაქციით:

1. In დიზაინის რეჟიმში, წასვლა ინსტრუმენტები -> ფორმა პარამეტრები -> ღია და შენახვა.

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 (ჩემს გარემოს მაინც) დააბრუნებს domain და მომხმარებლის 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 მყარი კოდირებული domain წინაშე ნიკი() ფუნქცია ჩვენს თანასწორობის შემოწმება და აღმოფხვრას რისკი ცრუ დადებითი შეიცავს ოპერატორი.

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?

</ბოლო>

პროგრამები Tags:

შემთხვევით დამატება კოდექსის 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. თუმცა, როდესაც მე შევეცადე აქვეყნებს ფორმით ცოტა ხნის შემდეგ კი, it required that I publish as an "Administrator-approved form template (გაფართოებული)". 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. ამჯერად, მე მქონდა ცოტა მეტი დრო ჩემს ხელში და აღმოჩნდა, რომ თქვენ შეგიძლიათ მარტივად გაუქმება ამ.

გადასვლა:

ინსტრუმენტები -> ფორმა პარამეტრები -> პროგრამირებაში: "Remove Code"

ეს არ მიიღოთ ბევრად უფრო ადვილია, ვიდრე,.

</ბოლო>

პროგრამები Tags: ,

მინიმალური უშიშროების საჭირო 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. (ეს არის ახალი აყვანის on-ინტერნატის ფორმა მიერ გამოყენებული ადამიანური რესურსების, რომ იწყებს workflow).

To meet that objective, I created created two new permission levels ("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. (If you feel a little shaky on SharePoint permissions, check out this 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, I did the following:

  1. Create a new permission level.
  2. Clear away all options.
  3. Selected only the following from "List permissions":
    • Edit Items
    • View Items
    • View Application Pages

Selecting these options allows a user to update a form, but not create it.

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, but turns out it is.

Create-and-Update was even stranger. I followed the same steps, 1 through 3 ზემოთ. I had to specifically add a "Site Permission" option: "Use client integration features". ისევ, the description there does not make it seem like it ought to be required for an InfoPath form, but there it is.

</ბოლო>

პროგრამები Tags: ,

ეს “შორის” ვაღიარებთ; შენიშვნები 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, 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; 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. თუმცა, 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.

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, და ა.შ.. 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. მაგრამ, 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 🙂 )

</ბოლო>

პროგრამები Tags:

კვირა სასაცილო: “ისინი, რომ ცუდი”

უკან ახლოს 1999, მე ხარჯვის ბევრი კვირის out სანტა ბარბარა, 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. სადღაც ხაზის გასწვრივ, 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."

</ბოლო>

პროგრამები Tags:

სწრაფი და მარტივი: ავტომატურად ღია 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.

</ბოლო>

პროგრამები Tags: