Minimum Təhlükəsizlik InfoPath formaları tələb

Bir cavab buraxın

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. (Bu, yeni işə bir iş edib ki, İnsan Resursları istifadə üzrə internat forması).

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, güncelleyin" user and a separate "update only" istifadəçi. 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, Mən aşağıdakı etdi:

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

</son>

O “In-arasında” Hiss; SharePoint Consulting dair müşahidələr

2 Cavablar

Qubarlı, 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, özüm kimi heyəti məsləhətçilər üçün xüsusi vaxt (as opposed to independents who must normally live in perpetual fear of in-between time 🙂 ). We staff consultants fill this time in various ways: Təkliflər yazmaq üçün satış xalq İş; kimsə üçün doldurulması və ya bu və ya qəribə iş bir şəxs qədər dəstək; studying; Blogging :). It’s hard to plan more than a few days in advance. At times like this, Mən əlləri vaxt bir az zamanı, 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. Hələ, Siz müştəri ilə nahar yemək, nahar onları çıxarmaq və / və ya içkilər üçün, komanda üçün çerezleri almaq, qəhvə çalışır getmək, bayram kartları vermək / almaq — 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. Digər tərəfdən, you’re a baby. On day zero, məsləhətçilər adlarını bilmirəm, the places or the client’s lingo. Most times, məsləhətçilər bütün öyrənmək heç vaxt.

Şeyi də getmək zaman, 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, Onlar bunu həyata heç vaxt.

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, idarəetmə, taksonomisi, əsas məzmun növləri, və s.. və bir çox cəhətdən, uzun bərabərdir, 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, PeopleSoft üçün BDC əlaqələri həyata, SharePoint Designer ilə olduqca kompleks iş təqdim, touched on basic KPI’s and more. A proper phase two would extend all of that with extensive, demək olar ki, yayılan BDC, həqiqətən gözəl iş, gözəl ayarlanmış və daha yaxşı axtarış, qeydlər mərkəzi, yəqin ki, excel xidmətləri və ən mühüm, reaching out to other business units. Lakin, bu, mənim üçün olmaq deyil, and that’s sad.

Bu son təcrübəyə əsaslanaraq, 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, əlbəttə.

That’s the consultant’s life and all of these little complaints are even worse in a SharePoint engagement. Mən əvvəl yazılı etdiyiniz kimi, 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 şirkət daha səmərəli ola kömək edə bilər ki, bir çox yollarla edə bilərsiniz, vaxtınıza qənaət, daha yaxşı şeylər… but you don’t always get to do them.

Mən tez-tez kollec həyata mənim ilk iş geri baxmaq, 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, lakin, 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! 🙂

Mənim həzin əhval baxmayaraq, Mən daha olarıq bir yerdə təsəvvür edə bilməz (ruhlar gözəl təchizatı ilə isti çimərlik istisna olmaqla,).

Mən növbəti müəssisə SharePoint layihə həyata başlamaq üçün gözləyin bilməz.

(Heç bir yerinde, Mən bu blog giriş ən yazdı NJ Transit avtobus. I don’t think I made any friends, but one CAN blog on the bus 🙂 )

</son>

Technorati Tags:

Bazar Funny: “Onlar ki, pis deyilik”

Bir cavab buraxın

Geri yaxın 1999, Mən Santa Barbara həftə bir çox həyata sərf edilmişdir, CA, bir müşteri üçün iş, 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. Somewhere xətti boyunca, Mən bir söz coined, "special fear", as in "Samantha has special fears." She as a special fear of "bugs", Onun hansı uçur və ya ladybugs deyil, but rather microbes. She’s afraid of this or that virus or unusual bacteria afflicting our son, və ya mənə, but never really herself. (O, həmçinin Vampires xüsusi qorxur, miniatür pis dolls (xüsusilə klounlar) və sualtı qəza; o Santa Claus kıyafetlerinize ildə geyimli insanlar öz xüsusi qorxu out-artıb).

Bir gün, 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.

Bu gecə, 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, Mən pəncərə həyata 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: Qışqıra-qışqıra: "My God! CAN THEY TAKE OVER YOUR MIND???"

S: Sözün mənə güvən: "No, Onlar pis deyilik."

</son>

Technorati Tags:

Tez və asan: SharePoint Designer E-poçt avtomatik olaraq Open InfoPath Form

1 Cavab

UPDATE: Madjur Ahuja bir bu link göstərir haber qrup müzakirəsi: 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, Onlar e-poçt linki basın və InfoPath form birbaşa bilərsiniz.

Bu canavar URL tikinti mənim üçün işləyir:

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

Şəklində adı ilə qalın harflerle qırmızı mətn əvəz, Aşağıdakı ekran göstərildiyi kimi:

image

Sabit kodlu yolu bir çox URL var Qeyd edək ki,, 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, E-poçt mənbəyinə və sizə daxil lazım olan hər şeyi görəcəksiniz.

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.

</son>

Technorati Tags:

Commercial Products haqqında düşünür

2 Cavablar

I put up a SharePoint Designer extensions project up at CodePlex earlier this year and even though it’s really quite limited in scope, Mən bunu tərəfindən nazil edilmişdir ki, qiymətləndirmək 40 üçün 60 (hətta 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 🙂

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). Əvvəl, I had an entire company behind me and in front of me, selling and supporting the products we brought to market. Bugün, 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, və ya comment tərk edin email me directly. I’d like to hear opinions like:

  • Is it all worthwhile?
  • Practical suggestions for marketing, collecting money, distributing.
  • Pricing.
  • Dəstək.
  • 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.

</son>

Technorati Tags:

Bazar Səhər Funny: “İsa ölmək lazımdır”

1 Cavab

Biz ilk alıb (yalnız və yalnız) "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 Bir neçə gün keçdi before life returned to normal. Just before Floyd struck, biz istifadə Volvo təklif 850 GL və sonra Floyd vurdu, ev sürdü.

It was our first car with a CD player. Like most new car owners, biz bir az CD crazy getdi, 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. Bizim halda, idi İsa Məsih Superstar.

Biri (çox) ki, rok opera parlaq ədəd yaradılması dini növləri tərəfindən ifa olunur, başda 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, ölmək lazımdır, ölmək lazımdır, this Jesus must die". You hear that refrain a lot in that piece.

O zaman, 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, poçt vasitəsilə axtarır və bütün adi walk-in-the-qapı məhsulları və mən birdən-birə o, yalnız deyən oldu ki, həyata, həqiqətən oxuyan deyil: "Jesus must die, ölmək lazımdır, 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 — ki, körpə dostu ilə yəqin ki, sonuncu play tarixi.

We pulled that CD out of the Volvo after that 🙂

</son>

Google AdSense proqramı Into My Live məkanı Blog qarşıladınız

7 Cavablar

UPDATE: Kimi 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.

Bu SharePoint post deyil, lakin ümumilikdə bloqçular üçün maraqlı ola bilər.

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. Lakin, Mənim canlı fəzalarında blog Mən bu yaxınlarda proqram qəbul edilib, belə siyasəti ya dəyişib və ya Google bir səbəbdən onun rədd.

Əlbəttə, Mən canlı kosmosa Google AdSense inteqrasiya hər hansı aşkar şəkildə görmürəm, but it’s a start 🙂

</son>

Technorati Tags: ,

Master həyata keçirilməsi / Xüsusi Lists istifadə Ətraflı münasibətlər

5 Cavablar

Forum users frequently as questions like this:

> Salam,
>
> Ilə xüsusi siyahısını yaratmaq üçün hər hansı imkanlar var, əgər mənə deyin
> master və ətraflı növü (faktura kimi) without using InfoPath.
>

SharePoint ki, kimi biznes tələblərinə cür dəstək verən qutusu xüsusiyyətləri bəzi təmin edir.

Ümumən, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Use additional lists to maintain customer numbers, product numbers, və s..

Use a content query web part (in MOSS only) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) is also available for the reporting side of it.

Lakin, 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:

  • Size of related lookup lists 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 maddələr, that’s going to be a problem. The lookup control does not page through those items. Əvəzində, 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. Məsələn, 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. I’ve written about this here. You can’t implement cascading drop-downs, conditionally enable/disable fields, və s..
  • 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. Məsələn, SharePoint allows you to create two custom lists, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Sonra, you can delete the customer from the list. Qutusu həyata, there is no way to prevent this. To solve this kind of problem, you would normally use event handlers.

It may seem bleak, 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 enables us to fill those gaps using tools such as:

  • Event handlers. Use them to enforce referential integrity.
  • Custom columns: Create custom column types and use them in lieu of the default lookup column. Add paging, buffering and AJAX features to make them responsive.
  • BDC. 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.

    BDC is a MOSS feature (not available in WSS) and is challenging to configure.

  • ASP.NET web form: Create a full-featured AJAX-enabled form that uses the SharePoint object model and/or web services to leverage SharePoint lists while providing a very responsive user interface.

The last option may feel like you’re starting from scratch, but consider the fact that the SharePoint platform starts you off with the following key features:

  • Security model with maintenance.
  • Menu system with maintenance.
  • "Master table" (i.e. xüsusi siyahıları) with security, built-in maintenance and auditing.
  • Axtar.
  • Back end integration tools (BDC).

If you start with a new blank project in visual studio, you have a lot of infrastructure and plumbing to build before you get close to what SharePoint offers.

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, Şərh tərk edin.

</son>

Sadə Tip: Məqalələr Query Web Part, Sütun dəyəri və XSL Axtarış

3 Cavablar

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

That column is of type "lookup".

Mən redaktə var <CommonViewFields> və ItemStyle.xsl sütun göstərmək.

A sadə <XSL:= seçin dəyər və…> geri sıra mövqe data ehtiva daxili dəyər qaytarır, kimi:

1;#Mayami

Insan dostu dəyər əldə etmək üçün, substring-sonra XSL istifadə, kimi:

<XSL:value-of select="substring-after(@ Real_x005F_x0020_Estate_x005F_x0020_Location,'#')"></XSL:dəyər və>

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

<Tamamlama />

Technorati Tags: , ,

SharePoint Beagle dekabr Up Sayı & Yaşamaq

Bir cavab buraxın

Bir çoxunuz artıq bilirik, but the December edition of SharePoint Beagle is live.

Her yazı məncə dəyər oxu.

I want to give a little extra bump to my colleague’s article (Natalya Voskrensenskya). She provides a screen-shot extravaganza while describing how she used custom lists, iş, 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 her blog while you’re at it.

Don’t forget to check out my article as well 🙂 I wrote about using MOSS to help an HR department manage open positions.

</son>