Минимум безбедност потребни за 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 Тагови:

Размислувајќи за комерцијални производи

I put up a SharePoint Designer extensions project up at CodePlex earlier this year and even though it’s really quite limited in scope, Јас се процени дека тоа е се преземени од страна на 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, што може да се претвори во добра количина пиво

My background is actually much more in product development and I know what is required to bring a top-notch product, as opposed to a CodePlex hobby project, to market. In my past life, I was responsible for product R&D for all software products. The difference between then and now is that I’m a consultant now working for an (excellent) consulting firm (Conchango). Претходно, I had an entire company behind me and in front of me, selling and supporting the products we brought to market. Денес, I’d be alone.

I have several product ideas in mind, 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 for an unlimited developer license and $500 per production web front end. I think I would also give away the source code.

If you have thoughts or experiences that you’re willing to share, Ве молиме оставете коментар или email me directly. I’d like to hear opinions like:

  • Is it all worthwhile?
  • Practical suggestions for marketing, collecting money, distributing.
  • Pricing.
  • Поддршка.
  • Any other comment you’d like to leave.

It’s "easy" to come up with product ideas and to implement them, 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 Неколку дена веќе поминаа before life returned to normal. Just before Floyd struck, ние направивме понуда за користени Volvo 850 GL и после Флојд погоди, возеше дома.

It was our first car with a CD player. Like most new car owners, отидовме малку ЦД луд, 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. Во нашиот случај, тоа беше Исус Христос Суперѕвезда.

Еден од (многу) брилијантен парчиња во тој рок операта е испеана од основањето религиозни типови, предводени од Кајафа, 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, мора да умре, мора да умре, this Jesus must die". You hear that refrain a lot in that piece.

Во времето, 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, во потрага преку пошта и сите мојата вообичаена прошетка-in-the-врата работи и јас одеднаш сфати дека тој е само велејќи, навистина не пее: "Jesus 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 — веројатно последна претстава тек со тоа бебе пријател.

We pulled that CD out of the Volvo after that 🙂

</крајот>

Google не го прифати мојот Live Spaces блог во програмата AdSense

Ажурирање: Како на 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.

This is not a SharePoint post, but might be of interest to bloggers generally.

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. Сепак, I was recently accepted into the program for my live spaces blog, so the policy has either changed or Google denied her for some other reason.

Се разбира, I don’t see any obvious way to integrate Google AdSense into my live space, but it’s a start 🙂

</крајот>

Technorati Тагови: ,

Спроведување на мајстор / Детали Врски Користејќи прилагодено Листи

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

> Здраво,
>
> Молам да ми кажете ако има било какви можности да се изгради сопствен список со
> господар и детали тип (како фактури) без користење на InfoPath.
>

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

Воопшто, 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:

  • Големина на поврзани пребарување листи vs. "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. На пример, SharePoint овозможува да креирате две сопствени листи, "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, SharePoint ни овозможува да се пополни овие празнини користење на алатки како што се:

  • Event handlers. Use them to enforce referential integrity.
  • Обичај колони: Create custom column types and use them in lieu of the default lookup column. Add paging, визуелниот и AJAX карактеристики за да ги направи одговора.
  • ЦРБ. 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.

    ЦРБ е карактеристика Мос (не се достапни во WSS) and is challenging to configure.

  • ASP.NET веб форма: Создаде целосно опремен AJAX-от форма која го користи објектот SharePoint модел и / или веб сервиси да потпора SharePoint листи истовремено обезбедувајќи многу одговора кориснички интерфејс.

На последната опција може да се чувствуваат како да сте почнувајќи од нула, но се разгледа на фактот дека на платформата SharePoint ви започнува со следниве клучни карактеристики:

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

Ако започнете со нов празен проект во Visual Studio, имате голем број на инфраструктурата и водовод за да се изгради пред да се доближиме до она што SharePoint нуди.

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, Ве молиме оставете коментар.

</крајот>

Брзо Совет: Содржината Пребарување Веб Дел, Пронајди колона вредност и XSL

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

That column is of type "lookup".

Имам пат е изменета <CommonViewFields> и ItemStyle.xsl да се покаже на колоната.

Едноставен <XSL:вредност на одберете =…> се враќа назад внатрешна вредност, која вклучува реден позиција на податоци, како што се:

1;#Мајами

За да се добие човек-пријателски вредност, го користите XSL подниза-по, како што е прикажано:

<XSL:value-of select="substring-after(@ Real_x005F_x0020_Estate_x005F_x0020_Location,'#')"></XSL:вредност на>

Use this technique whenever you are working with lookup values in XSL transforms and need to get the human-friendly value.

<крај />

Technorati Тагови: , ,

SharePoint Бигл декември прашање Up & Живеат

Многумина од вас знаат ова веќе, но во декемврискиот број на SharePoint Бигл е во живо.

Секоја статија е вредно да се прочита во моето мислење.

Сакам да им даде малку екстра судрат до мојот колега статија (Наталија Voskrensenskya). She provides a screen-shot extravaganza while describing how she used custom lists, работното, SharePoint Designer, 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.

</крајот>