Kima cha chini cha Usalama Required Kwa Fomu 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. (Hii ni mpya-kuajiri juu-bweni fomu kutumiwa na Rasilimali kwamba yazindua workflow).

Kufikia lengo, Mimi umba kuundwa mbili ngazi ruhusa mpya ("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" mtumiaji. The mechanics all worked, but it turned out to be a little more involving than I expected. (Kama wewe kujisikia shaky kidogo juu ya SharePoint ruhusa, angalia hii baada ya blog). 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, Nilifanya zifuatazo:

  1. Kujenga mpya ruhusa ngazi.
  2. Wazi mbali chaguzi zote.
  3. Selected only the following from "List permissions":
    • Hariri Items
    • View Items
    • View za Maombi

Kuchagua njia hizo inaruhusu mtumiaji update fomu, lakini si kujenga.

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, lakini zinageuka ni.

Create-and-Update was even stranger. I followed the same steps, 1 kupitia 3 juu ya. I had to specifically add a "Site Permission" chaguo: "Use client integration features". Tena, maelezo kuna haina kufanya hivyo kuonekana kama inavyopaswa zinazohitajika kwa ajili ya fomu InfoPath, lakini kuna ni.

</mwisho>

Tags technorati: ,

Kwamba “Katika-Kati” Hisia; Uchunguzi juu ya SharePoint Consulting

Cha kusikitisha, 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, kama kawaida 🙂 Sasa mimi ni kati ya miradi, muda maalum kwa ajili ya wafanyakazi washauri kama mwenyewe (kinyume na wagombea binafsi ambaye ni lazima kwa kawaida wanaishi katika hofu ya daima ya in-kati ya wakati 🙂 ). We staff consultants fill this time in various ways: Kufanya kazi na watu mauzo ya kuandika mapendekezo; kujaza kwa mtu au inaunga mkono juu ya mtu juu ya kazi hii au isiyo ya kawaida; studying; Mabalozi :). It’s hard to plan more than a few days in advance. At times like this, wakati mimi kuwa na kidogo ya muda juu ya mikono yangu, 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. Hata hivyo, wewe kula chakula cha mchana na mteja, kuchukua nje kwa chakula cha jioni na / au kwa ajili ya vinywaji, kununua cookies kwa ajili ya timu ya, kwenda kwenye anaendesha kahawa, kutoa / kupokea kadi likizo — 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. Kwa upande mwingine, you’re a baby. On day zero, washauri hawajui majina, the places or the client’s lingo. Most times, washauri kamwe kujifunza yote.

Wakati mambo kwenda vizuri, 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, kamwe kutambua wao ni kufanya hivyo.

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, utawala, Jamii, msingi maudhui aina, nk. na katika mambo mengi, kiasi na ya muda mrefu, 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, kutekeleza uhusiano BDC kwa PeopleSoft, ilianzisha workflow haki tata na SharePoint Designer, touched on basic KPI’s and more. A proper phase two would extend all of that with extensive, karibu kuenea BDC, kweli nice workflow, faini tuned na bora tafuta, kumbukumbu za kituo cha, kuutumia huduma na pengine muhimu zaidi, reaching out to other business units. Lakini, siyo kuwa kwa ajili yangu, and that’s sad.

Kulingana na uzoefu huu wa hivi karibuni, 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, bila shaka.

That’s the consultant’s life and all of these little complaints are even worse in a SharePoint engagement. Kama nimepata iliyoandikwa kabla ya, 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, unaweza kuona njia nyingi kwamba SharePoint inaweza kusaidia kampuni ya kuwa na ufanisi zaidi, kuokoa muda, kufanya mambo vizuri… but you don’t always get to do them.

Mimi mara nyingi kuangalia nyuma kwa kazi yangu ya kwanza nje ya chuo, 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, hata hivyo, 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! 🙂

Licha ya mood yangu soda, Siwezi kufikiria mahali nisingependa kuwa (isipokuwa katika pwani ya joto na usambazaji mzuri wa roho).

Siwezi kusubiri kupata ilianza kutekelezwa ijayo biashara SharePoint mradi.

(Apropos ya kitu chochote, Mimi aliandika zaidi ya kuingia hii blog juu ya NJ Transit basi. I don’t think I made any friends, lakini moja UNAWEZA blogu kwenye basi 🙂 )

</mwisho>

Tags technorati:

Jumapili Mapenzi: “Wao uko Si KWAMBA Bad”

Nyuma karibu 1999, Mimi mara matumizi mengi ya wiki nje katika Santa Barbara, CA, kufanya kazi kwa ajili ya mteja, 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. Mahali fulani kwenye mstari, 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).

One day, 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."

</mwisho>

Tags technorati:

Haraka na Easy: Moja kwa moja Open InfoPath kidato Kutoka SharePoint Designer Email

UPDATE: 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, wanaweza bonyeza kiungo kutoka email na kwenda moja kwa ajili ya 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:

picha

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.

</mwisho>

Tags technorati:

Kufikiri Kuhusu Bidhaa Commercial

Mimi kuweka SharePoint Designer upanuzi wa mradi hadi saa CodePlex mapema mwaka huu na hata ingawa ni kweli kabisa mdogo katika upeo, Mimi makisio kwamba imepakuliwa na 40 kwa 60 (pengine hata 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, ambayo inaweza kutafsiri katika kiasi mzuri ya bia 🙂

Background yangu ni kweli zaidi katika maendeleo ya bidhaa na mimi najua ni nini wanatakiwa kuleta bidhaa juu-notch, kinyume na mradi hobby CodePlex, to market. In my kipindi cha maisha, Mimi alikuwa na wajibu wa bidhaa R&D for all software products. The difference between then and now is that I’m a consultant now working for an (bora) kampuni ya ushauri (Conchango). Hapo awali, Mimi nilikuwa na kampuni nzima nyuma yangu na mbele yangu, selling and supporting the products we brought to market. Leo, Ningependa kuwa peke.

Nina mawazo kadhaa bidhaa katika akili, 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 kwa ukomo developer leseni na $500 per production web front end. I think I would also give away the source code.

Kama una mawazo au uzoefu kwamba uko tayari kushiriki, tafadhali kuacha maoni au email yangu moja kwa moja. I’d like to hear opinions like:

  • Je, ni vyema?
  • Vitendo mapendekezo kwa ajili ya masoko, kukusanya fedha, kusambaza.
  • Bei.
  • Kusaidia.
  • Maoni yoyote nyingine Ningependa kuondoka.

It’s "easy" kuja na mawazo ya bidhaa na kutekeleza yao, though many dozens of hours of work are required. The other stuff is not as easy for me.

</mwisho>

Tags technorati:

Sunday Morning Mapenzi: “Yesu Must Die”

Sisi kununuliwa kwanza wetu (na tu) "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 siku kadhaa kupita before life returned to normal. Just before Floyd struck, sisi alifanya kutoa kwa ajili ya Volvo kutumika 850 GL na baada Floyd akampiga, alimfukuza nyumbani.

It was our first car with a CD player. Like most new car owners, tulikwenda kidogo CD mambo, 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. Katika kesi yetu, ilikuwa ni Yesu Kristo Superstar.

Moja ya (wengi) vipande kipaji katika kwamba opera mwamba ni kuimba na aina ya uanzishwaji wa dini, wakiongozwa na Kayafa, 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, lazima kufa, lazima kufa, this Jesus must die". You hear that refrain a lot in that piece.

Wakati, 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, kutafuta njia ya barua na kawaida yangu kila kutembea-katika-mlango-stuff na mimi ghafla kutambua kwamba yeye tu kusema, si kweli kuimba: "Jesus must die, lazima kufa, 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 — pengine mwisho kucheza na tarehe na rafiki kwamba mtoto.

Sisi vunjwa kwamba CD kutoka Volvo baadaye 🙂

</mwisho>

Tags technorati: ,

Google Je Kubali yangu Nafasi Live Blog Ndani ya Adsense

UPDATE: Kama ya 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.

Hii si baada SharePoint, lakini inaweza kuwa ya riba kwa wanablogu ujumla.

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. Hata hivyo, Mimi nilikuwa hivi karibuni kukubaliwa katika mpango kwa ajili ya nafasi yangu ya kuishi blog, hivyo sera ina ama kubadilishwa au Google alikanusha yake kwa ajili ya baadhi ya sababu nyingine.

Bila shaka, Sioni njia yoyote dhahiri kuunganisha Google Adsense katika nafasi yangu ya kuishi, lakini huu ni mwanzo 🙂

</mwisho>

Tags technorati: ,

Utekelezaji wa Mwalimu / Undani Mahusiano Kutumia Orodha Desturi

Forum users frequently as questions like this:

> Hujambo,
>
> Tafadhali niambie kama kuna uwezekano wa kujenga orodha ya desturi na
> bwana na undani aina (kama ankara) without using InfoPath.
>

SharePoint hutoa baadhi ya nje ya makala sanduku kwamba msaada wa aina ya mahitaji ya biashara kama kwamba.

Kwa ujumla, 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, nk.

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.

Hata hivyo, 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 vitu, that’s going to be a problem. The lookup control does not page through those items. Badala yake, 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. Kwa mfano, 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. Nimeandika kuhusu hili hapa. You can’t implement cascading drop-downs, masharti kuwawezesha / afya ya mashamba, nk.
  • 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. Kwa mfano, SharePoint inaruhusu kujenga orodha mbili desturi, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Kisha, you can delete the customer from the list. Nje ya boksi, there is no way to prevent this. To solve this kind of problem, ungependa kawaida kutumia handlers tukio.

Inaweza kuonekana hatarini, 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 unatuwezesha kujaza mapengo wale kutumia zana kama vile:

  • Event handlers. Use them to enforce referential integrity.
  • Desturi nguzo: Create custom column types and use them in lieu of the default lookup column. Add paging, buffering na makala AJAX kuwafanya msikivu.
  • 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 ni hulka MOSS (si inapatikana katika WSS) and is challenging to configure.

  • ASP.NET mtandao fomu: Kuunda full-featured AJAX-enabled fomu kwamba anatumia kitu SharePoint mfano wa kuigwa na / au huduma za mtandao na orodha SharePoint kujiinua wakati kutoa msikivu sana user interface.

hatua ya mwisho inaweza kuhisi kama wewe ni kuanzia mwanzo, lakini kuzingatia ukweli kwamba jukwaa SharePoint kuanza wewe mbali na makala muhimu yafuatayo:

  • Usalama mfano wa kuigwa na matengenezo ya.
  • Mfumo menu na matengenezo ya.
  • "Master table" (i.e. desturi orodha) na usalama, kujengwa katika matengenezo na ukaguzi.
  • Kutafuta.
  • Nyuma mwisho zana ushirikiano (BDC).

Kama wewe kuanza na mradi mpya katika studio ya Visual tupu, una mengi ya miundombinu na mabomba ya kujenga kabla ya kupata karibu na nini SharePoint inatoa.

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, tafadhali acha maoni.

</mwisho>

Haraka Tip: Content Query Mtandao Sehemu ya, Luke Column Thamani na XSL

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

That column is of type "lookup".

Mimi tarehe <CommonViewFields> na ItemStyle.xsl kuonyesha safu.

rahisi <xsl:thamani ya kuchagua =…> anarudi nyuma thamani ya ndani kuwa ni pamoja na data nafasi makutano, kama vile:

1;#Miami

Kupata thamani ya binadamu ya kirafiki, kutumia XSL substring-baada ya, kama inavyoonekana:

<xsl:value-of select="substring-after(@ Real_x005F_x0020_Estate_x005F_x0020_Location,'#')"></xsl:thamani ya>

Kutumia mbinu hii wakati wewe ni kufanya kazi na maadili lookup katika kuugeuza XSL na haja ya kupata thamani ya binadamu ya kirafiki.

<mwisho />

Tags technorati: , ,

SharePoint Beagle Desemba Suala Up & Kuishi

Wengi wa unajua hii tayari, lakini Desemba toleo la SharePoint Beagle ni kuishi.

Kila makala ni thamani ya kusoma kwa maoni yangu.

Mimi nataka kutoa ziada kidogo mapema kwa mwenzake yangu makala (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 yake blog wakati uko katika hilo.

Usisahau kuangalia nje yangu makala pamoja 🙂 niliandika kuhusu kutumia MOSS kusaidia idara HR kusimamia nafasi za wazi.

</mwisho>