Sigurtà minima meħtieġa għall Formoli 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. (Dan huwa ġdid-kiri forma on-imbark użata minn riżorsi umani li tniedi workflow).

Biex jintlaħqu dan l-għan, I ħolqot ħolqot żewġ livelli permess ġdid ("create and update" and "update only"), broke inheritance for the form library and assigned permissions to a "create, jaġġornaw" user and a separate "update only" utent. The mechanics all worked, but it turned out to be a little more involving than I expected. (Jekk inti tħoss ftit dgħajfa fuq permessi SharePoint, check out dan 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, Jien għamilt dan li ġej:

  1. Oħloq livell permess ġdid.
  2. Ċar bogħod għażliet kollha.
  3. Selected only the following from "List permissions":
    • Edit Punti
    • View Partiti
    • Ara Pages Applikazzjoni

Għażla ta 'dawn l-għażliet jippermetti utent li taġġorna forma, iżda mhux joħolqu dan.

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, iżda jinstabx huwa.

Create-and-Update was even stranger. I followed the same steps, 1 permezz 3 hawn fuq. I had to specifically add a "Site Permission" għażla: "Use client integration features". Għal darb'oħra, id-deskrizzjoni hemm ma jagħmilha jidhru simili hi jmissha tkun meħtieġa għal forma InfoPath, iżda hemm hu.

</aħħar>

Li “Fil-Bejn” Tħossok; Osservazzjonijiet dwar SharePoint Consulting

Sfortunatament, 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, bħas-soltu 🙂 jien issa bejn il-proġetti, żmien speċjali għall-konsulenti persunal bħal myself (għall-kuntrarju indipendenti li normalment ikollu jgħixu fil-biża perpetwu ta fin-nofs żmien 🙂 ). 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. Madankollu, 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. Min-naħa l-oħra, 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, eċċ. 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. Iżda, 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, tal-kors.

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, madankollu, 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, iżda wieħed CAN blog fuq ix-xarabank 🙂 )

</aħħar>

IL-ĦADD Funny: “Huma qed mhux ħażin”

Back qrib 1999, I kien infiq ħafna ġimgħat fl Santa Barbara, CA, jaħdmu għal klijent, 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. X'imkien matul il-linja, I maħluqa frażi, "special fear", as in "Samantha has special fears." She as a special fear of "bugs", li lilha mhumiex dubbien jew ladybugs, but rather microbes. She’s afraid of this or that virus or unusual bacteria afflicting our son, jew me, but never really herself. (Hija wkoll apposta jibża 'Vampires, pupi ħażen minjatura (speċjalment buffi) u inċidenti taħt il-baħar; hi l-kibret biża speċjali tagħha ta 'nies lebsin Santa Claus ħwejjeġ).

Ġurnata waħda, 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.

Dak il-lejl, 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 l-tieqa."

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: Fil b'leħen qawwi: "My God! CAN THEY TAKE OVER YOUR MIND???"

S: Litteralment rassikuranti me: "No, dawn mhux qed dik ħażina."

</aħħar>

Tags:

Quick u Easy: Formola InfoPath Awtomatikament Open Mill SharePoint Designer Email

UPDATE: Madjur Ahuja jirrimarka din ir-rabta minn diskussjoni 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, huma jistgħu ikklikkja fuq il-link tal-email u jmorru direttament għall-forma InfoPath.

Din il-kostruzzjoni URL monster jaħdem għalija:

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

Ibdel it-test aħmar bolded bl-isem tal-formola, kif muri fil-screenshot li ġejjin:

immaġni

Innota li hemm ħafna ta 'passaġġ hard-coded f'dak 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, tara l-sors ta 'l-email u tkun taf tara dak kollu li għandek bżonn biex tinkludi.

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.

</aħħar>

Thinking About Prodotti Kummerċjali

I imqiegħed Proġett estensjonijiet Designer SharePoint up fuq CodePlex aktar kmieni din is-sena u anki jekk huwa verament pjuttost limitata fl-ambitu, Jiena nistma li huwa kien jitniżżel minn 40 li 60 (possibilment anke 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, li jistgħu jsarrfu ammont goodly ta 'birra 🙂

Isfond tiegħi huwa fil-fatt ħafna aktar fl-iżvilupp tal-prodott u naf dak li huwa meħtieġ biex prodott top-talja, bħala kuntrarju għal proġett passatemp CodePlex, to market. In my ħajja tal-passat, I kien responsabbli għall-prodott R&D for all software products. The difference between then and now is that I’m a consultant now working for an (eċċellenti) ditta ta 'konsultazzjoni (Conchango). Preċedentement, I kellha kumpannija sħiħa lura lili u quddiem lili, selling and supporting the products we brought to market. Illum, I d jkun waħdu.

I jkollhom diversi ideat prodott fil-moħħ, 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 għal liċenzja iżviluppatur bla limitu u $500 per production web front end. I think I would also give away the source code.

Jekk għandek ħsibijiet jew esperjenzi li int lesti li jaqsmu, jekk jogħġbok leave kumment jew email lili direttament. I’d like to hear opinions like:

  • Huwa kollha utli?
  • Suġġerimenti prattiċi għall-marketing, ġbir ta 'flus, distribuzzjoni.
  • Ipprezzar.
  • Appoġġ.
  • Kwalunkwe kumment ieħor li tixtieq li jħallu.

It’s "easy" biex joħorġu b'ideat prodott u biex jimplimentawhom, though many dozens of hours of work are required. The other stuff is not as easy for me.

</aħħar>

Ħadd filgħodu Funny: “Ġesù Must Die”

Aħna mixtrija tagħna ewwel (u biss) "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 diversi jiem għadda before life returned to normal. Just before Floyd struck, aħna għamlet offerta għal Volvo użati 850 GL u wara Floyd laqat, saq dar.

It was our first car with a CD player. Like most new car owners, aħna marru CD crazy ftit, 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. Fil-każ tagħna, kien Ġesù Kristu Superstar.

Wieħed mill- (ħafna) biċċiet brillanti f'dak blat opra hija kantata minn-tipi reliġjużi istabbiliment, mmexxija mill 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, għandu die, għandu die, this Jesus must die". You hear that refrain a lot in that piece.

Fil-ħin, 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, tfittex permezz tal-posta u kollha walk-in-the-bieb tas-soltu tiegħi għalf u I f'daqqa jirrealizzaw li hu biss qal, mhux verament kant: "Jesus must die, għandu 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 — probabbilment l-aħħar data play ma 'dak ħabib baby.

Aħna jinġibed li CD mill-Volvo wara li 🙂

</aħħar>

Google Did Aċċetta My Live Spaces Blog Into-Programm AdSense

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

Din mhix post SharePoint, iżda jistgħu jkunu ta 'interess bloggers ġeneralment.

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. Madankollu, I kien reċentement aċċettat fil-programm għall-ispazji ħajjin tiegħi blog, sabiex il-politika tkun jew inbidlet jew Google miċħuda tagħha għal xi raġuni oħra.

Of course, I ma tara l-ebda mod ovvju biex jintegraw Google AdSense fl-ispazju ħajjin tiegħi, imma hija bidu 🙂

</aħħar>

Master Implimentazzjoni / Relazzjonijiet dettall użu ta 'listi Custom

Utenti forum spiss bħala mistoqsijiet bħal din:

> Hello,
>
> Jekk jogħġbok għidli jekk hemmx xi possibbiltajiet biex tinbena lista dwana ma
> kaptan u dettall tip (bħal fatturi) mingħajr l-użu InfoPath.
>

SharePoint jipprovdi wħud mill-karatteristiċi kaxxa li jappoġġjaw tipi ta 'ħtiġiet tan-negozju bħal dik.

B'mod ġenerali, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Jużaw listi addizzjonali li jżommu klijent numri, numri tal-prodott, eċċ.

Uża parti kontenut tal-web query (fil MOSS biss) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) huwa wkoll disponibbli għall-naħa rappurtar ta 'dan.

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

  • Daqs tal lookup relatati listi 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 oġġetti, that’s going to be a problem. The lookup control does not page through those items. Minflok, 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. Per eżempju, 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. Stajt bil-miktub dwar dan hawn. You can’t implement cascading drop-downs, jippermettu kondizzjonalment / jiskonnettja oqsma, eċċ.
  • 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. Per eżempju, SharePoint jippermettilek li toħloq żewġ listi tad-dwana, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Imbagħad, you can delete the customer from the list. Barra mill-kaxxa, there is no way to prevent this. To solve this kind of problem, inti normalment tuża handlers avveniment.

Dan jista 'jidher skoraġġanti, 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 tgħinna biex timla dawn il-lakuni permezz ta 'għodod bħall-:

  • Handlers Avveniment. Use them to enforce referential integrity.
  • Kolonni Custom: Create custom column types and use them in lieu of the default lookup column. Add paging, buffering u l-karatteristiċi Ajax sabiex isiru sensittivi.
  • 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 hija karatteristika MOSS (mhux disponibbli fil WSS) and is challenging to configure.

  • Formola tal-web ASP.NET: Oħloq full-dehru forma AJAX-ppermettiet li juża l-mudell oġġett SharePoint u / jew servizzi tal-web għal-listi SharePoint lieva filwaqt li tipprovdi user interface ferm reattivi.

L-aħħar għażla tista 'tħossok bħal int tibda mill-bidu, iżda tikkunsidra l-fatt li l-pjattaforma SharePoint jibda inti off mal-karatteristiċi ewlenin li ġejjin:

  • Sigurtà mudell ma 'manutenzjoni.
  • Sistema menu mal-manutenzjoni.
  • "Master table" (I.E. listi tad-dwana) mas-sigurtà, mibnija fil-manutenzjoni u l-verifika.
  • Fittex.
  • Back jispiċċaw integrazzjoni għodod (BDC).

Jekk tibda bi proġett blank ġdid fl-istudjo viżwali, ikollok ħafna ta 'infrastruttura u plumbing biex jibnu qabel ikollok qrib għal dak offerti 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, jekk jogħġbok leave kumment.

</aħħar>

Tip Quick: Parti kontenut Web Mistoqsija, Lookup Valur Kolonna u XSL

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

That column is of type "lookup".

I immodifikaw <CommonViewFields> u ItemStyle.xsl biex juru l-kolonna.

A sempliċi <XSL:valur tal tagħżel =…> prospetti lura valur intern li tinkludi data tal-posizzjoni ordinal, bħal:

1;#Miami

Biex tikseb il-valur tal-bniedem-friendly, użu XSL substring-wara, kif muri:

<XSL:value-of select="substring-after(@ Real_x005F_x0020_Estate_x005F_x0020_Location,"#")"></XSL:il-valur tal->

Uża din it-teknika meta inti taħdem ma 'valuri Lookup fil jittrasforma XSL u jeħtieġ li jiksbu l-valur tal-bniedem-friendly.

<aħħari />

Tags: , ,

SharePoint Beagle Diċembru Ħruġ Up & Live

Many of you know this already, but the December edition of SharePoint Beagle is live.

Every article is worth reading in my opinion.

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, workflow, 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 artiklu tiegħi kif ukoll 🙂 I kiteb dwar l-użu MOSS biex jgħinu dipartiment HR tamministra pożizzjonijiet miftuħa.

</aħħar>