arquivos mensuais: Xaneiro 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, por exemplo, 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, por favor me diga.

Estado Live Spaces dicirme: hits total para o día, 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 enlace do foro, etc).

Nalgúns aspectos, a "hit" É obvio. Se estás lendo esta frase agora, vostede case certamente rexistrado como un único hit.

RSS is a little confusing. On one hand, I see individual RSS hits all day long. Pero, I also see RSS "sweeps". A sweep is when I see 20 ou 30 RSS hits all within a one or two second window. I assume these are automated things like google checking in on my site, navegadores quizais outros … non estou seguro. They are definitely some kind of automated process. I cannot tell, con todo, 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 accesos por día son automatizadas.

En aos números!

Eu escribín o meu primeiro blog en 27 de xullo, 2007.

Escribín aproximadamente 60 entradas de blog, desde entón,, máis do que 50 que se relacionan directamente co SharePoint.

Comecei a seguir os meus acertos nunha folla nunha base diaria, a finais de setembro.

Comeza mensuais:

Primeira semana de: Total de Accesos
Outubro 1,234
Novembro 2,162
Decembro 3,071
Xaneiro 2008 4,253

Total por mes

Mes Total de Accesos
Outubro 6,620
Novembro 11,110
Decembro 13,138

Marcas de auga de alta

Tipo Total de Accesos
Best Day 958
Best Week 4,253
Total de Accesos desde o día cero 42,438

Estou interesado en outros’ stats. If you care to share yours in the comments, por favor, faga!

</final>

Technorati Tags:

Domingo Morning divertido: “Si, si, si. Blah, blah, bla.”

Preto de seis anos, os meus catro anos de idade, fillo e eu estabamos alí enriba asistir a unha Discovery Channel "shark attacks" especial (posiblemente esta). 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, por exemplo, calquera medos especiais da auga ou tagarela algo impropio aos seus amigos e, finalmente, causar a súa rede de amigos bebé para derrubar.

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

Así, 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, meu fillo (que sempre foi moi axitado calquera maneira), 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. Con todo, I had misinterpreted his excitement. He was not worried about the girl at all. Pola, mentres a aplaudir, el me di, "The sharks love it! It’s terrific. It’s wonderful. Its a DREAM COME TRUE!"

Eu pensaba que iso era Hilario, but also very disturbing. Por unha banda, Quedei contento — ata un pouco orgulloso — que podería ter fortes sentimentos de empatía, cross-species though they may be. As humans, we need to develop our "empathic muscles" para falar ou vai acabar como este cara 🙂 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.

Isto non é unha palabra tan fácil de describir a un neno de catro anos, but I gave it a try. When I think of the word "paradigm", Thomas Kuhn is never far from my thoughts. I read A Estrutura das Revolucións Científicas de volta ao Lafayette e para mellor ou para peor, the word "paradigm" is pregnant with extra meaning for me. (Sort of like the word "contact" despois de escoitar unha voz Teléfono película me onde eu podía ver que dicir esta película [Eu penso que o libro era mellor]; Sempre digo para min mesmo, "CONTACT!" whenever I see or hear someone say "contact").

De calquera xeito, Estou tentando explicar a el unha definición kuhniana, 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." Por suposto, non se pode falar así dun neno de catro anos, so I’m trying to successively define it to smaller pieces and feeling rather proud of myself as I do so. (Eu só Sabía que alguén de fóra da facultade lle importaría que eu lera Kuhn!).

I’m just warming to the task when he interrupts me. Waving his hand na miña dirección xeral e nunca tirar os ollos doutro ataque de quenlla brutal, el só di, "Yeah, si, si. Blah, blah, blah.".

So much for that 🙂

Nese punto, Decidín fuxir, retoricamente fala, sentir-se, e divírtete asistir tiburóns atacan o ser humano co meu fillo.

</final>

Technorati Tags:

Cambiar Ver en base á identificación do usuario nun formulario do InfoPath

Nós tiñamos un país desenvolvido unha forma de InfoPath con varias exhibicións para apoiar unha nova contratación / on-boarding process. When the company hires a new person, o departamento de TI e outros grupos teñen que tomar medidas (configurar folla de pagamento, permitir o acceso a aplicacións axeitados, atopar un balcón, etc). We use on form but a different view of the form for each of those functions.

Nesta empresa, a maioría das persoas implicadas no proceso de negocio son IT-savvy, así cando acceder ao formulario, their default view is a "menu" view with buttons that direct them to their specific function. Con todo, we needed to simplify things for the new hire’s direct manager. This person should not see any of the IT related stuff. En realidade, debe ver só unha vista da forma e nin sequera ten a posibilidade de ver os outros puntos de vista.

No noso caso, que o relato de director directo está directamente ligada á forma como cortesía dun contacto co selector (which I am always wanting to call a "people picker" por algunha razón).

Os pasos son os seguintes:

1. No modo de deseño, vaia a Ferramentas -> Opcións de Formulario -> Abrir e Gardar.

2. Select "rules".

3. Create a new rule whose action is "switch to view" e cuxa condición aproveita o nome de usuario() función.

Nome de usuario() returns the "simple" user name without the domain. If I log into SharePoint with credentials "domain\pagalvin", Nome de usuario() 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 (no meu ambiente de calquera maneira) devolve o dominio e ID de usuario, as in "domain\pagalvin". This prevents us from doing a straight-forward equality condition since AccountID ("domain\pagalvin") nunca será igual usuario() ("pagalvin").

We can get around this using the "contains" operador: AccountID contén usuario().

Podemos ir máis aló e pre-pende dun dominio hard-Coded diante do nome do usuario() función para comprobar a nosa igualdade e eliminar o risco dun falso positivo do operador contén.

We would have REALLY like to automatically switch view for other users based on their AD security group membership. Por exemplo, when a member of the "IT Analytics" grupo accede ao formulario, 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", pasalo a usuario() and return back true or false. Does anyone have any other, idea máis intelixente? Is there any SharePoint function we can leverage from InfoPath to make that determination?

</final>

Technorati Tags:

Accidentalmente Engadido código para unha forma de InfoPath; Eliminar-lo deliberadamente

Ao traballar con botóns nun formulario, we often add rules. You access the rules editor from the properties of the button.

Ao premer en volta rapidamente, it’s easy to accidentally click on "Edit Form Code" instead of "Rules …".

A primeira vez que fixen este, I canceled out of the code editor. Con todo, cando intento publicar o xeito un pouco máis tarde, it required that I publish as an "Administrator-approved form template (avanzado)". 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.

Hoxe, I did it again. Este tempo, Eu tiña un pouco máis de tempo nas miñas mans e descubrín que pode facilmente desfacer esta.

Ir a:

Ferramentas -> Opcións de Formulario -> Programación: "Remove Code"

Ela non queda moito máis fácil do que.

</final>

Technorati Tags: ,

Seguridade mínima esixida para formularios do 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. (Esta é a nova contratación en boarding forma utilizada pola área de recursos humanos, que lanza un fluxo de traballo).

Para alcanzar este obxectivo, Eu creei creou dous novos niveis de permiso ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, actualizar" user and a separate "update only" usuario. 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, Eu fixen o seguinte:

  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 arriba. I had to specifically add a "Site Permission" option: "Use client integration features". De novo, the description there does not make it seem like it ought to be required for an InfoPath form, but there it is.

</final>

Que “Intermedio” Sentimento; Observacións sobre SharePoint Consulting

Desafortunadamente, 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, un momento especial para consultores persoal como eu (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; Blogs :). 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. Aínda, 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. Por outra banda, 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.

Cando as cousas van ben, 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, nunca entender que eles están a facer iso.

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, Goberno, taxonomía, básicas de tipos de contido, etc. e en moitos aspectos, elévase a unha longa, 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, implementación de conexións BDC para PeopleSoft, introduciu un fluxo de traballo moi complexo co SharePoint Deseño, touched on basic KPI’s and more. A proper phase two would extend all of that with extensive, case xeneralizada BDC, moi bo fluxo de traballo, ben afinado e busca mellor, Centro de Rexistros, Servizos de Excel e, probablemente, máis importante, reaching out to other business units. Pero, non é ser para min, and that’s sad.

Con base nesa experiencia recente, 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, claro.

That’s the consultant’s life and all of these little complaints are even worse in a SharePoint engagement. Como xa escribín antes, 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, con todo, 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 🙂 )

</final>

Technorati Tags:

Domingo divertido: “Eles non son tan malo”

Volver preto 1999, Eu estaba gastan moito de semana en Santa Barbara, CA, traballando a un cliente, 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. Nalgún lugar ao longo da liña, 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).

Un día, 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."

</final>

Technorati Tags:

Fácil e rápida: Formulario InfoPath automaticamente Aberto de SharePoint Design Correo-e

Actualización: Madjur Ahuja apunta este enlace dun discusión 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, poden premer na ligazón do correo-e e ir directamente ao formulario do InfoPath.

Este URL construción monstro funciona para min:

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

Substituír o texto en negra vermello co nome do formulario, como se mostra na imaxe seguinte:

imaxe

Teña en conta que hai unha morea de camiño hard-Coded ese 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, ver o código fonte do correo electrónico e vai ver todo o que ten que incluír.

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.

</final>