Nyaraka za kila mwezi: Januari 2009

Kudhibiti Workflow Tabia na Desturi Lists (Tena)

Mapema mwezi huu, Mimi put together an article originally planned for Mark Miller’s www.endusersharepont.com. Hata hivyo, I instead used like Dustin Hoffman used a cross at the end of the The Graduate to fend off my (kutisha! kirafiki!) editor at TechTarget.

This is another SharePoint Designer workflow article in the same vein as my more recent effort here: http://www.endusersharepoint.com/?p=1226 ("Use Control Lists to Create Flexible Workflow Solutions").

Ni kuanza kama hii:

HAVE YOU EVER wished you could temporarily disable a SharePoint Designer workflow? You may want to do this in order to mass-approve a large number of documents without setting off dozens — or possibly hundreds — of unnecessary workflows.

One way to accomplish this is to access the workflow using Share-Point Designer and disable it. To do that, you’ll need to open up SharePoint Designer, access the workflow, change its properties and re-save it. The problem with that method is that it’s a little messy and likely to ring lots of alarm bells at most companies.

Kwa ujumla, fiddling about with SharePoint Designer workflows is not a good practice in a production environment, nor is it part of a well controlled process.

The article then walks you through a solution to this problem that uses a custom list to turn the WF on or off as needs dictate. Kusoma kitu wote hapa (http://wp.bitpipe.com/resource/org_1127860336_240/SharePoint_vol5_v6 1_16.pdf).

This article was inspired by a question asked on the forums here: http://www.endusersharepoint.com/STP/. Although I spend far more time on the MSDN forums, I strongly recommend that you have a peek at the EUSP forum as well, particularly for end user oriented questions. It’s yet another source of good information and advice.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati:

Kutumia Orodha Udhibiti Kujenga Solutions Workflow Flexible

Wiki iliyopita, Mark Miller posted my latest SharePoint Designer workflow article for end users on his site (http://www.endusersharepoint.com/?p=1226).

Ni kuanza kama hii:

Sisi aina ya kiufundi matumizi mengi ya jargon na Vifupisho katika utaratibu wetu wa kila siku kama vile "OOP" (kitu oriented programu), "CT" (Aina maudhui), "SPD" (SharePoint Designer), "RTFM" (tafadhali kusoma mwongozo), nk. This article concerns itself with a particular bugaboo called “hard coding:” What it is, why it’s bad and how to avoid it in SharePoint designer workflow solutions.

I describe how we can use custom lists to store workflow control and configuration data. Using this approach, we can avoid hard coding values such as approvers’ email addresses, approval dollar limits, nk.

Kuangalia ni nje.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati:

Utawala na SharePoint Tafuta – Ni Kamwe Too Late ya Kuanza

Mimi aliandika makala (http://searchwinit.techtarget.com/tip/0, 289,483, sid1_gci1345231_mem1, 00.html #) kwa SearchWinIT.com on governance as it relates to SharePoint Search. It’s not in my usual "voice" but that’s editing for you 🙂

Hapa ni jinsi ya kuanza:

Ingawa karibu kila nyanja ya SharePoint wanaweza kunufaika na mpango wa nguvu ya utawala, MOSS 2007’s enterprise search functionality benefits most of all.

Kama kila sehemu ya SharePoint, kuna habari njema na habari mbaya kuhusu utawala. Kwa mashirika mengi, habari mbaya ni kwamba ni vigumu sana kuingiza mpango wa utawala ambapo hakuna lolote.

Lakini hapa ni habari njema: Unaweza haraka configure na kuboresha juu ya kutafuta biashara ya saa karibu wakati wowote. Na wakati wewe kutekeleza mpango wa utawala kwa ajili ya kutafuta biashara, unaweza kuona matokeo ya haraka.

Moja ya matatizo na SharePoint na utawala ni kwamba makampuni mara nyingi kupata goti kina katika SharePoint na hakuna mpango wa utawala na kwa wakati huo, there’s no easy path forward to solve it. No so with Search. Read the article to get my thoughts on that subject.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: ,

Ujao FAST Uwasilishaji, Jumatano 01/28, Saa sita mchana EDT

I’ll be doing my first ever online presentation hosted by the mighty EMC marketing machine at 12:00 saa sita mchana EDT Jumatano, 01/28. Mimi sijui nini cha kutarajia kutoka hii, in terms of attendance. Hata hivyo, tangu mimi nina kuongoza ni, Naweza kukuambia nini cha kutarajia kama wewe kufanya muda kwa ajili yake.

I’m going to be describing what we here at EMC mean when we talk about "Enterprise Search." I’m distinguishing between regular old SharePoint Search (which is quite useful by itself) and Enterprise Search, which is a much bigger, nastier, interesting and perplexing problem to solve.

I’m going to make the argument that FAST is a good tool to use while trying to solve the Enterprise Search problem (and I make some analogies to canals while I’m at it). This obviously ties into SharePoint and will be a part of the community’s fabric over the course of 2009 and beyond. That’s the hook for anyone reading my blog here.

If you’re interested in FAST, I think you’ll find enough useful information to justify the time spent listening to me talk about it.

It’s a marketing presentation, but all of the marketing stuff is at the end, so you can always drop off at that point.

The mighty EMC marketing machine has provided me with a signup link, so please use it to register.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: , ,

Self-Huduma Site Uumbaji Je, si Hasa Kuhusu Kujenga Sites

Kama wengi SharePoint mshauri aina, I’ve been exposed to a lot of SharePoint functionality. Some times, I dive pretty deep. Other times I just notice it as I’m flying by to another set of menu options. One of those is "self-service site creation." I haven’t had a need for it until this week.

Wiki hii, I need to solve a business problem which I think is going to become more common as companies loosen up and embrace more direct end user control over SharePoint. Katika kesi hiyo, I’ve designed a site template to support a specific end user community. Folks in this community should be able to create their own sites at will using this template whenever the urge strikes them.

I recalled seeing "self-service site creation" before and I’ve always tucked that away in the back of my head thinking that "self service site creation" ni SharePoint Hands maana, ni wazi kutosha, something like "turn me on if you want end users to be able to create sites when they want to."

Hivyo, Mimi kugeuka juu, kujaribu nje na kwa ajili yangu, it’s not creating sites. It’s creating site makusanyo. Pretty big difference. That’s not what I want, si wakati wote.

It is possible to let end users create new sub sites via a custom permission level. This is exactly where I would have gone in the first place except that the label "self-service site creation" label deceived me. Via twitter, I learn that it’s deceived others as well 🙂

Mimi bado kazi nje ya jinsi ya kutoa kidogo ya mchakato wa zaidi harmoniserad wakati anakaa rena nje ya boksi, but there’s a definite path to follow. Just don’t get distracted by that label.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati:

Akizungumza katika Mkutano wa New York SharePoint Waendelezaji Group

Mimi nitakuwa kuwasilisha katika New York SharePoint mkutano Waendelezaji kundi mjini New York katika Ofisi ya Microsoft juu ya Ave 6 Jumanne, 01/27 katika 6:00 PM (zaidi ya wiki kutoka sasa!).

Ishara ya juu hapa.

It’s going to be a technical presentation where I walk through the process of creating a custom workflow action that can be packaged and installed into a SharePoint environment and used by SharePoint Designer to create declarative workflow solutions.

Think this: http://www.codeplex.com/spdactivities

I’ll do a little evangelizing as I go along, making the case that developers should really think hard about the benefits of this kind of effort. it goes something like this: Give a man a fish and he eats for a day, build him a custom workflow action and he can design and implement his own business process for finding fish (or any other food!) and leave the developers alone to do the heavy duty complex programming that developers are best at doing.

It’s obviously a developer oriented session, but I do encourage curious end users and admins to show up. Even though the specific process of creating a custom action is targeted directly at developers, the meta conversation about one is not.

I hope to see you there.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: