Arkivji tal-Kategorija: Soluzzjonijiet SharePoint Disinn

Traċċar Attivitajiet ta 'prattika – Parti 1

3 tweġibiet

Madwar sena ilu, I ssieħbu Consulting slalom hawn fi New York bħala nsejħu Ċomb Żona Prattika.  (Bħala minuri aside għall-punt ta 'dan blog post, li l-bidla fil-kontijiet impjiegi għal drop-off tiegħi total fil blogging.  Kien bidla kbira fl-irwoli u bidla kbira fil-jum għal jum "għalf" imma stajt tip ta 'akklimatizzati myself lilha u ħerqana għall-kitba mill-ġdid Tbissem ).

F'dan ir-rwol PAL, Jien responsabbli biex isalva l-kumpanija u l-inħawi immedjati ta ' 21 West triq 21 minn diżastru fuq bażi regolari.  Huwa ħafna pressjoni (more than you might think – just think of all the children!). 

In service to that imperative, I need to help out with pre-sales, create and update go-to-market offerings, hire good folks, train up folks to make them better (but really, to make my job easier) and occasionally do something billable at a client.  I get a lot of “input” – questions from clients, sales opportunities, my own addled thoughts and so forth.  Some of it’s really good (like a hot sales oppty) while a lot of it is less good.  The key is to initially track, prioritize and manage each of these ideas (great and small) to a successful conclusion. 

This kind of task management isn’t new, dritt?  And we have lots of task tools to help us with this.  Outlook has tasks.  You can slap a spreadsheet together nice and quick.  My very first task management tool was a legal notepad back in my days at GAF as a developer in the IT department.  (Ask me about those good old days the next time you see me if you’re interested, or maybe not...).

Being a SharePoint guy (nominally, inqas), I’ve always thought to use SharePoint.  But for some reason, a generic Task list never quite did it for me.  A bunch of months ago, I decided to heal myself and just create a SharePoint based solution.  It was so embarrassingly easy to create that I thought to write about it here.

Allura, my goals here were very simple:

  • Super easy and fast data entry
  • Prioritize activities
  • Categorize activities
  • “next step” driven – these activities will often span weeks (maybe even months).  Huma kważi qatt "end" wara aġġornament speċifiku wieħed.

Dawn bits jipprestaw ruħhom ħafna nicely għal tip kontenut, hekk dan huwa dak I maħluqa:

image

Inti tista 'attwalment tara li kelli bias bejgħ ma' dan fl-ewwel, peress I jkollhom li "Klijent" qasam.  A lott ta 'Attivitajiet ta' prattika tiegħi huma bbażati madwar il-klijenti (jew attwali jew prospettiv).  Iżda ħafna minnhom huma wkoll internament iffokat.  I SLAP "Slalom" fil hemm meta I jinħolqu minnhom, iżda dejjem iħoss a tad stramb.  I għandhom ikunu semmew xi ħaġa aktar ġeneriku.  Forsi "Organizzazzjoni Target" jew xi ħaġa.

Hawnhekk huma noti mixxellanji ftit fuq it-tip kontenut:

  • Attività Impatt ddelega fis kejl ta 'prijorità.  I’m not sure why I went with “Impact” and not “Priority” day zero, but that’s what I did. 
  • Next Steps and Next Steps Date – I have a dashboard that is driven by the next activity date.  This dashboard has sort of become my marching orders for the day/week.  I just go to the dashboard and focus on high priority stuff first and go from there.  (There’s the notion of an “untagged”
  • Primary Owner – the only thing of note is – isn’t it awesome that you can sort and filter on multi-select columns in SP 2010! I actually didn’t fully buy into this notion at first.
  • Activity Status – really just “Open” or “Closed.” 
  • Primary Practice – After I began using this, another PAL in my group wanted to try this out, so I slipped this into the mix to distinguish between my stuff (Portals & Collaboration) and her stuff (Azure).

Here’s my dashboard:

image

(sorry for all the blurred out bits – I didn’t feel like creating a bunch of test data and I don’t want to give anyone a heart attack over sharing vital details [see the bit in the intro re: save the world, eċċ, eċċ, eċċ]).

I have several other views on this list, including a datasheet view that allows me to do mass updates.  I do this most often when a bunch of lower priority items I planned to do a never quite got done and need to be pushed out a week.

Kull jum, I pull up my activities log and just start working off the top of the list.

In part 2, I’ll explain how I made this even more useful with the addition of a nice email-enabled doc library and SPD workflow.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Let Eżempji brillanti Ċomb-Mixja biex Adozzjoni SharePoint Żieda

Ħalli Risposta

Ewwel "pur" BrightStarr dħul blog tiegħi ġiet ippubblikata llum.  Hawn teaser:

Hemm kien hemm ħafna ta 'konversazzjoni fuq l-internets ta tard dwar is-suġġett tal-adozzjoni SharePoint u speċjalment in-nuqqas tagħhom. Ħadd ma trid tmur l-inkwiet ta 'tfassil infrastruttura tas-sigurtà razzett u, jipparteċipaw fil-workshops, tqegħid flimkien ħarsa snazzy u jħossu, xogħol barra arkitettura informazzjoni blat solidu li jistgħu jifilħu għall-inċertezzi ta 'kumpannija re-Orgs u finalment, a tnedija Fanfare mimlija biss biex jiskopru xhur wara tliet go-live li inqas minn 50% ta 'l-impjegati tal-kumpanija qed jużaw SharePoint u ħafna minnhom qed jużaw biex jissostitwixxu l-servers qodma fajl netwerk ("the S:\ drive").

Nru bullet fidda (jew blog post wieħed) se ssolvi din il-problema. Madankollu, hemm ħafna affarijiet li tista 'tagħmel biex tnaqqas ir-riskju ta' portal SharePoint anemiċi. One such technique is the "Shining Example Pattern."

I imħabba biex tkun taf dwar strateġiji oħra adozzjoni SharePoint li inti kura biex jaqsmu.  Jekk inti tagħmel sehem, jekk jogħġbok leave bħala kumment fuq il-blog BrightStarr.

Aqra l-ħaġa sħiħa hawn: http://www.brightstarr.com/US/Pages/blog-view.aspx?BlogID=52

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Oħloq Paġni Printer Friendly u Anke Stampa Them

1 Irrispondi

I kiteb up 'oġġett għall SharePoint Briefing ġimgħa jew hekk ilu u huwa kien stazzjonati.  Hawn hu l-ftit ftuħ:

image

Tista 'taqra l-ħaġa sħiħa hawn: http://sharepointbriefing.com/features/article.php/3904906/Create-a-Printer-Friendly-Page-in-Your-SharePoint-Sites.htm

Nispera li dan jgħin xi ħadd.  Igawdu!

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

"Can Do” versus "Jekk Do” fi Proġetti SharePoint

8 tweġibiet

Naħseb li ħafna minna huma kultant ppreżentati ma, għal nuqqas ta 'frażi aħjar, Rekwiżiti żgħażagħ-tfal.  L-utent aħħari verament, ħażin ħafna trid ħarsa ċerti speċifika u jħossu, jew struttura issortjar speċifiċi ħafna jew li maqtugħa klikk waħda jew għażla menu biex ittaffi navigazzjoni jew [daħħal twemmin passionately ddeċidiet li jiġri li tkun ħażina].  Kif SharePoint pro, nistgħu ġeneralment jiltaqa 'kważi kull tip ta' rekwiżit mal-pjattaforma, iżda għal xi wħud minnhom, nafu fil-qlub tagħna li:

  • Huma ser jieħu ammont sproporzjonat ta 'żmien biex jimplimentaw (u għalhekk jiswew aktar)
  • Huma ser ikunu ferm custom u għalhekk diffiċli li tinżamm u troubleshoot
  • Hemm xi metodu SharePoint faċli li jissodisfa 80% jew aktar tal-ħtieġa (I.E. jissodisfa l-sartja tal-ħtieġa, iżda mhux l-ittra tar-rekwiżit)

Bottom line, nafu li l-"rekwiżit" huwa verament ftit sbieħ li jkollhom jew saħansitra leġittimu f'xi sens, imma xi ħaġa li n-nies għandhom jgħixu mal milli jonfqu ħafna ħin jippruvaw "issolvi."

I think ta 'dawn bħala "żgħażagħ tfal" rekwiżiti għaliex stajt tidher dan il-mudell ħafna drabi qabel.  Kids se arżnu bogħod u NAG inti għal xi ġugarell ġdid għal ġimgħat fi żmien.  Ikollok lilhom l-ġugarell, dawn jilagħbu magħha għal ftit sigħat jew jiem u mbagħad titqiegħed l-isfel, qatt li pick it up qatt darb'oħra.  Jew, inti ma tieħux il-ġugarell, il-waqfiet nagging u l-kid jiċċaqlaq biex isiru President tad-dinja b'xejn.   Stajt rajt dan jiġri fi proġetti SharePoint.  Deċiżjoni dawk li jfasslu jew tikseb dak li jridu u dan isir funzjoni mhux użati jew użati biżżejjed jew ma jiksbu dak li jridu u l-proġett għadu jirnexxilu xorta waħda.

I kien mfakkra li llum fil-post forum u I gustado kif Clayton Cobb ppruvaw jiksbu l-poster forum biex timbotta lura fuq waħda minn dawn it-tipi ta 'rekwiżiti: http://social.msdn.microsoft.com/Forums/en-US/sharepointinfopath/thread/af8a1941-92ad-4f1a-b1bf-875e28ea79b7/

Ninsab verament kurjużi kif in-nies jaraw dan is-suġġett u kif inti jittrattaw dan.  Am I nieqes il-punt?  Għandek strateġiji għall steer dawk li jfasslu d-deċiżjonijiet bogħod minn overinvesting fir-rekwiżiti trivjali?  Jekk jogħġbok leave kumment.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Uża Workflow biex jissimulaw Kontenut Tip Sigurtà

3 tweġibiet

Jum ieħor, ieħor MSDN-forums ispirati post.

Xi ħadd kienet qed titlob jekk dawn jistgħu jiżguraw tip kontenut li meta klikks utent fuq l-"ġodda" buttuna fuq lista custom, biss it-tipi ta 'kontenut li l-persuna tingħata aċċess jidher fil-lista drop-down.  Kif nafu, din ma hija sostnuta mill-kaxxa.

This question comes up now and then and this time, I had a new idea.  Let’s assume that we have scenario like this:

  • We have a helpdesk ticketing system.
  • The helpdesk ticketing system allows users to enter regular helpdesk ticket info, such as problem area, problem status, eċċ.
  • We want to allow “super” users to specify an “urgency” field.
  • Other users don’t have access to that field.  The system will always assign “medium” level priority to their requests.

What we could do is create two separate SharePoint lists and two different content types, one for “super” users and the other for everyone else.

Workflow on each list copies the data to the master list (the actual helpdesk ticket list) and the process proceeds from there.

This approach might work flow a kind of column level security as well. 

I haven’t tried it, but it feels reasonable and gives a fairly simple, if pretty rough, option to implement a kind of content type and even column level security.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Parti kontenut Web Mistoqsija: Svizzera Armata sikkina SharePoint tal

Ħalli Risposta

Artikolu aħħar tiegħi huwa up fuq www.sharepointbriefing.com. Hawn teaser:

image

Aqra l-ħaġa sħiħa hawn: http://sharepointbriefing.com/features/article.php/3874226/Content-Query-Web-Part-SharePoints-Swiss-Army-Knife.htm

Tara fil juża sit web pubbliku reali hawn minn dawn il-passi:

  1. Mur din il-paġna web: http://cdi-its.com/Pages/Customer_Support.aspx (Dan huwa l-paġna ta 'appoġġ klijent għall-CDI).
  2. Ikklikkja fuq "Case Studies" fil-navigazzjoni naħa tax-xellug.

Hija se jaqbżu l-"Customer Support" taqsima tal-istudji każ elenkar.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Pre-kondizzjonijiet eżistenti: SharePoint Templates Twissija għall-salvataġġ (?)

Ħalli Risposta

One of my clients worked with a previous contractor to build out a small but useful HR application for the enterprise. That contractor used SharePoint Designer to implement the workflow portion of the solution. It’s a bit of a mess. Per eżempju, there are nine SPD workflows in support of a single logical workflow process and up to five of them may fire simultaneously at any given time given the right conditions. It’s not easy to debug 🙂

My customer has a number of still-outstanding requirements, one of which is to generally provide more context when the system sends out email alerts – both in the email itself as well as associated task forms. As SPD workflow implementers know, the “collect data from user” SPD action actually creates a task with a custom content type. When we use that action, we don’t get to specify much. We can prompt for some values (e.g. “approve” or “deny”) and we can specify a hard coded value in the title and description. That’s about it.

My customer’s requirement is two fold:

  1. When SharePoint sends an email about a task assignment, include a lot of information about the task in the email body.
  2. More importantly, by far – when the user clicks on the task link in the email, the task form should have all the information the approver needs in order to make his/her approve or deny decision. Right now, the manager needs to click on the item link itself to drill down into the underlying details and no one likes that. You have to click in the email. Then you need to click a sort of obscure link on the task item. Then you can look at the underlying data (an InfoPath form in this case). Then you click back/back, eċċ. Everyone hates it.

I’ve inherited this somewhat messy technical solution and I want to make changes in the least intrusive way possible.

The approach I’m taking right now is to create a custom alert template. You can read about that here. The flow works like this:

  • SPD workflow runs.
  • F'xi punt, it assigns a task to a manager.
  • SharePoint system automatically sends out an alert to that manager. This is not part of the SPD workflow but rather “what SharePoint does.” (The SharePoint timer service, I believe).
  • A custom alert handler is invoked in favor of the standard alert process (following magic rules as described in the above referenced article).
  • When my custom alert handler runs, it generates a beautiful email. More importantly, since it has the task in hand, it also decorates the actual task with all the context information necessary to meet the business requirement.
  • The user gets the email and it’s full of useful context information.
  • User clicks on the task link and the task itself is full of useful context information.
  • Everyone goes home to have watermelon and ice cream.

I did a quick POC and it works well in a lab environment. I get my custom email alert as expected. I also get to update the task description and title itself.

The only tricky bit, s'issa, is to avoid a situation where the alert updates the item, triggering another alert. This doesn’t worry me.

Looks promising so far…

The great thing about this is that I don’t need to muck about with any of the existing SPD workflows. They are blissfully unaware that an alert handler is “IIZ RUNNIN IN DA BAKGROUND, DECORATIN TEH TASK LIST WIF MOAR CONTEXT".

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Dimostrazzjoni SharePoint: SharePoint Leverage Tibni Applikazzjoni Business Vertikali

Ħalli Risposta

[Innota: Irrid ngħid mill-ewwel li jien jkollhom interess finanzjarju fir-riżultat mixtieq ta 'din id-dimostrazzjoni, li nsemmi fl-interess tal-iżvelar sħiħ, eċċ. This is actually the first time I’ve ever blogged about an event where I stand to benefit personally in this way.]

Din id-dimostrazzjoni web iseħħ il-Ħamis, 06/04 fil 12:30 EDT, li jispiċċa mill- 1:30PM EDT.

F'kooperazzjoni mal-partner tiegħi negozju eċċellenti, Sistemi integrati u Group Services (ISSG), I have been working to develop a vertical business application using SharePoint as the platform. F'dan il-każ, we’re building an application that serves the needs of manufacturers that make customized product for their customers. In these cases, a great deal of collaboration needs to take place between the customer and the manufacturer. There’s also a great deal of collaboration required between different groups within the manufacturer, inkluż il-bejgħ, inġinerija, riċerka u żvilupp, gruppi legali u oħrajn.

Il-demo se juru applikazzjoni li jiffaċilita dan it-tip ta 'kollaborazzjoni, flimkien ma 'diskussjoni dwar kif kollha ta' dawk bits kollaborazzjoni jeħtieġu li jintegraw ma 'sistema ERP backend.

Fl-aħħar nett, this isn’t going to be a SharePoint demo. This is a demonstration of a solution for a specific niche problem that happens to use SharePoint as the platform.

Allura, għaliex kieku inti jolqot biex jiffirmaw u tara dan demo? I don’t expect too many readers of my blog to be all that interested in a solution for make-to-order manufacturers 🙂 Your take-away would be the concept itself – using SharePoint purely to deliver a business solution without regard to SharePoint itself.

Jekk int interessat, jekk jogħġbok jiffirmaw hawn(https://www323.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=skmqfwbr5smmlx20).

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Tista PRY Designer SharePoint Mill My Cold, Idejn Mejjet

Ħalli Risposta

My latest article is up at www.EndUserSharePoint.com. I wrote about SharePoint Designer, Utenti finali u l-punti prinċipali ta 'strateġija li l-utenti finali tista' tipprova u jsegwu sabiex juru l-kompetenza u tinbena l-fiduċja madwar din l-għodda.

Il-kummenti huma aktar interessanti mill-oġġett innifsu.

Iċċekkjaha.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

MOSS Profil Utent bħala l-Awtorità għall-preferenza Lingwa User

4 tweġibiet

Fuq il-proġett kurrenti tiegħi, xi wħud mill-utenti ser jivvjaġġaw madwar id-dinja u meta jaslu fid-destinazzjonijiet differenti, use whatever machine is handy at the time. Those guest machines will be running Windows and installed and configured for the local locale. (Stajt biss induna li l-magni mistieden jista 'ma jkollhomx il-lingwa pakketti dritt… probabbilment mhux se, fil-fatt… Jien ipparkjar li wieħed għal issa).

SharePoint needs to provide a mechanism whereby the user can pick their preferred language and then have MOSS honor that language regardless of how the user accesses MOSS. In other words, disregard whatever the browser tells IIS/MOSS and instead look up that preferred language and use it.

Aħna ser tinvestiga żewġ approċċi:

  1. Handler HTTP: A handler HTTP custom installat fuq IIS se tħares up profil MOSS-utent, insemmu l-lingwa preferita u mbagħad jaqilbu l-header HTTP madwar kif meħtieġ qabel ma jgħaddu kontroll biex MOSS.
  2. global.asax: Modify global.asax to do the same thing. We may modify something else, but the idea is that we find some place where we can insert our locale-switching logic.

Il-fattur ieħor komplikat huwa li għandna bżonn sabiex l-utenti 60k, dwar 1,000 tagħhom jista 'jkun aċċess simultanjament MOSS b'tagħbija massima.

Il-handler HTTP jidher pjuttost drastiku, but possibly the best place to put the code since it’s at the IIS level and all-knowing. It’s a good single point of work.

Aħna qed jegħleb lejn approċċ tip global.asax, prinċipalment għaliex aħna nemmnu aħna ser ikollhom aktar għażliet għall-caching data f'dak il-punt.

I ser tkun blogging aktar fuq dan is-suġġett bħala I jitgħallmu aktar.

Jekk għandek tkun taf xejn dwar dan, please post a comment 🙂

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin