Минимална безбедности Обавезно за ИнфоПатх Формс

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. (Ово је нови-запосли на укрцавање форма користи кадрове који покреће ток посла).

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, update" 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, Сам урадио следеће:

  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.

</крај>

Да “Између” Осећај; Запажања о СхареПоинт Цонсултинг

Нажалост, 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: Рад са фолк продаје за писање предлога; попуњавање за некога или бекаповање особу на овај или онај чудан посао; studying; Блоггинг :). It’s hard to plan more than a few days in advance. At times like this, док имам мало времена на мојим рукама, 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, спровођење БДЦ везе са ПеоплеСофт, увео прилично сложен ток посла са СхареПоинт Десигнер, touched on basic KPI’s and more. A proper phase two would extend all of that with extensive, прожима готово БДЦ, стварно лепо тока, фино подешени и боље претраживање, Центар за записе, Екцел Сервицес и вероватно најважнији, 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, можете видети толико много начина на које може да помогне СхареПоинт компанија постати ефикаснији, уштедите време, раде ствари боље… 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! 🙂

Упркос мом меланхолија расположења, Не могу да замислим место бих радије био (осим у топлој плажи са повећи снабдевање духова).

Једва чекам да почнемо реализује наредних подухвата СхареПоинт пројект.

(Поводом ничега, Написао сам већину тог блогу на Њ Трансит аутобус. I don’t think I made any friends, but one CAN blog on the bus 🙂 )

</крај>

Тецхнорати Тагс:

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

Назад у близини 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. Негде дуж линије, 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).

Једног дана, 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:

С: "Oooo! Those are bad. They carry diseases."

П: "Well, I flicked it out the window."

С: "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!"

П: In a loud voice: "My God! CAN THEY TAKE OVER YOUR MIND???"

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

</крај>

Тецхнорати Тагс:

Брзо и лако: Аутоматски отвара ИнфоПатх обрасцу из СхареПоинт Десигнер Емаил

УПДАТЕ: 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, они могу да кликну на линк из е-поште и иду директно на ИнфоПатх обрасцу.

This monster URL construction works for me:

хттп://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.КСМЛ&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.

</крај>

Тецхнорати Тагс:

Размишљање о комерцијалних производа

Трпим СхареПоинт Ектенсионс Десигнер пројекат горе у ЦодеПлек раније ове године и иако је стварно прилично ограничене у обиму, Процењујем да је било преузето од стране 40 на 60 (можда чак и 100) companies in just about two months. That indicates to me that there’s a market for that solution and if I were to successfully commercialize it, that could translate into a goodly amount of beer 🙂

Моја позадина је заправо много више у развој производа и знам шта је потребно да би врхунски производ, за разлику од ЦодеПлек хоби пројекат, to market. In my Прошли живот, Ја сам био задужен за производ А&D for all software products. The difference between then and now is that I’m a consultant now working for an (одличан) Консултантска фирма (Цонцханго). Раније, Имао сам целу компанију иза мене и испред мене, selling and supporting the products we brought to market. Данас, Ја бих сама.

Имам неколико идеја у виду производа, but I think the easiest would be to create a commercial version of the above-mentioned CodePlex project that uses that as a starting point and extends it further. My fuzzy off-the-cuff thinking is to charge something like $100 неограниченог програмера лиценци и $500 per production web front end. I think I would also give away the source code.

Ако имате искуства или мисли да сте спремни да делите, оставите коментар или емаил ме директно. I’d like to hear opinions like:

  • Да ли је то све вредно?
  • Практични предлози за маркетинг, прикупљање новца, расподела.
  • Цене.
  • Подржати.
  • Сваки други коментар желите да оставите.

It’s "easy" да дођу до производа идеја и да их примени, though many dozens of hours of work are required. The other stuff is not as easy for me.

</крај>

Тецхнорати Тагс:

Сундаи Морнинг Фунни: “Исус Муст Дие”

Купили смо наш први (и само) "luxury" car back when hurricane Floyd nailed the east coast of the U.S. We got a LOT of rain here in New Jersey and several days passed before life returned to normal. Just before Floyd struck, смо направили понуду за Волво користи 850 GL and after Floyd struck, drove it home.

It was our first car with a CD player. Like most new car owners, we went a little CD crazy, revived our dormant CD collection and went on long drives just to listen to CD’s in the car. Like all fads, this passed for us and we ended listening to the same CD over and over again. У нашем случају, it was Jesus Christ Superstar.

Једно од (многи) brilliant pieces in that rock opera is sung by the establishment religious types, led by Caiaphas, the "High Priest". They sing their way into deciding how to handle the "Jesus problem" and Caiaphas directs them to the conclusion that "Jesus must die". The refrain on the song is "Just must die, must die, must die, this Jesus must die". You hear that refrain a lot in that piece.

At the time, my son was about three years old. You can probably see where this is going.

I came home from work one day and my son is in the living room playing with toys and humming to himself. I’m taking off my jacket, looking through the mail and all my usual walk-in-the-door stuff and I suddenly realize that he’s just saying, not really singing: "Jesus must die, must die, must die." I was mortified. I could just see him doing that while on one of his baby play dates at a friend’s house — probably the last play date with that baby friend.

We pulled that CD out of the Volvo after that 🙂

</крај>

Тецхнорати Тагс: ,

Прихвати ли Гоогле Ми Ливе Спацес блог у програму АдСенсе

УПДАТЕ: Од 03/09, I have found no way to integrate my live spaces account with Google Adsense. Microsoft’s system here seems to prevent all of the technical mechanisms that Google provides would-be adsense hosters. I tend to believe this is mainly a side effect of the security they’ve built into live spaces, not a direct effort to disable Adsense.

Ово није СхареПоинт порука, али може бити од интереса за блогера генерално.

Someone commented on their Windows Live Spaces blog that Google affirmatively denied their application to participate in AdSense. She theorized that Google denied her because Windows Live Spaces hosts her blog. Међутим, Недавно сам примљена у програм за моје Ливе Спацес блог, па политика је или промењен или Гоогле је одбијен због неког другог разлога.

Наравно, Ја не видим никакву очигледан начин да се интегришу Гоогле АдСенсе у мој Простор, but it’s a start 🙂

</крај>

Тецхнорати Тагс: ,

Имплементација Мастер / Детаил Односи Коришћење прилагођене листе

Форум корисници често као оваква питања:

> Здраво,
>
> Молим вас реците ми да ли постоје могућности за изградњу прилагођене листе са
> мастер и детаљ типа (као фактура) без употребе ИнфоПатх.
>

СхареПоинт пружа неке из кутије функција које подржавају врсте пословним захтевима као што је тај.

У глобалу, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Користите додатне листе за одржавање бројева купаца, бројеви производа, итд.

Користите Веб сегмент упита садржаја (у МОСС само) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (СРС) је такође доступан за извештајни стране њега.

Међутим, there are some important limitations that will make it difficult to use pure out-of-the-box features for anything that is even moderately complex. These include:

  • Величина вези листе проналажење вс. "smartness" of the lookup column type. A lookup column type presents itself on the UI differently depending on whether you’ve enabled multi-select or not. In either case, the out-of-the-box control shows all available items from the source list. If the source list has 1,000 ставке, that’s going to be a problem. The lookup control does not page through those items. Уместо тога, it pulls all of them into the control. That makes for a very awkward user interface both in terms of data entry and performance.
  • Lookups "pull back" one column of information. You can never pull back more than one column of information from the source list. На пример, you cannot select a customer "12345" and display the number as well as the customer’s name and address at the same time. The lookup only shows the customer number and nothing else. This makes for an awkward and difficult user interface.
  • No intra-form communication. Писао сам о томе овде. You can’t implement cascading drop-downs, условно омогућите / онемогућите поља, итд.
  • No cascading deletes or built-in referential integrity. SharePoint treats custom lists as independent entities and does not allow you to link them to each other in a traditional ERD sense. На пример, СхареПоинт вам омогућава да креирате две прилагођене листе, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Онда, you can delete the customer from the list. Оут оф тхе бок, there is no way to prevent this. To solve this kind of problem, што то обично користите за претовар догађаја.

То може да изгледа суморно, but I would still use SharePoint as a starting point for building this kind of functionality. Though there are gaps between what you need in a solution, СхареПоинт нам омогућава да попуни те празнине коришћењем алата као што су:

  • Event handlers. Use them to enforce referential integrity.
  • Прилагођене колоне: Create custom column types and use them in lieu of the default lookup column. Add paging, баферовање и АЈАКС функције да их одговоре.
  • БДД. This MOSS-only feature enables us to query other SharePoint lists with a superior user interface to the usual lookup column. BDC can also reach out to a back end server application. Use BDC to avoid replication. Rather than replicating customer information from a back end ERP system, use BDC instead. BDC features provide a nice user interface to pull that information directly from the ERP system where it belongs and avoids the hassle of maintaining a replication solution.

    БДД је МОСС функција (није доступна у ВСС) and is challenging to configure.

  • АСП.НЕТ Веб Форм: Направите потпуно функционалан АЈАКС омогућен образац који користи СхареПоинт објектни модел и / или веб сервисима СхареПоинт листама искористи док пружа веома брз кориснички интерфејс.

Последња опција може да се осећате као да почињете од нуле, али у обзир чињеницу да је СхареПоинт платформа вам се полази од следећих кључних карактеристика:

  • Безбедност модел са одржавањем.
  • Мени систем са одржавањем.
  • "Master table" (и.е. Прилагођене листе) са обезбеђењем, уграђене одржавање и ревизија.
  • Претражи.
  • Назад крај алата интеграције (БДД).

Ако почнете са новом празном пројекта у Висуал Студио, имате пуно инфраструктуре и водовод за изградњу пре него што дођете близу оно СхареПоинт нуди.

I do believe that Microsoft intends to extend SharePoint in this direction of application development. It seems like a natural extension to the existing SharePoint base. Microsoft’s CRM application provides a great deal of extensibility of the types needed to support header/detail application development. Although those features are in CRM, the technology is obviously available to the SharePoint development team and I expect that it will make its way into the SharePoint product by end of 2008. If anyone has an knowledge or insight into this, оставите коментар.

</крај>

Тецхнорати Тагс:

Брзо Савет: Веб сегмент за упит садржаја, Проналажење вредности колоне и КССЛ

I have a column name in a content type named "Real Estate Location".

That column is of type "lookup".

Променили сам <ЦоммонВиевФиелдс> и ИтемСтиле.ксл да покаже колону.

Једноставан <клс:вредности од изаберите =…> враћа унутрашњу вредност која садржи податке о положају редни, као такав:

1;#Мајами

Да бисте добили људски пријатељски вредност, користите КССЛ-подстрока после, као што је приказано:

<клс:value-of select="substring-after(@ Реал_к005Ф_к0020_Естате_к005Ф_к0020_Лоцатион,'#')"></клс:вредности од>

Користите ову технику сваки пут када радите са проналажење вредности у КССЛ трансформација и треба да се људски пријатељски вредност.

<крај />

Тецхнорати Тагс: , ,

СхареПоинт Бигл децембарском броју Горе & Живети

Многи од вас већ знају, али децембра издање СхареПоинт Беагле је уживо.

Сваки чланак је вредан читања, по мом мишљењу.

Желим да дам мало више налетети на Мој колега је чланак (Наталија Воскренсенскиа). She provides a screen-shot extravaganza while describing how she used custom lists, тока, СхареПоинт Десигнер, data views and other elements to implement a self-service training feature in MOSS. She describes techniques that can be applied in many different business scenarios. Check out Њен блог док си у томе.

Не заборавите да проверите мој чланак as well 🙂 I wrote about using MOSS to help an HR department manage open positions.

</крај>