Я рэарганізаваў сваё жыццё крыху і знайшоў час, каб прадставіць артыкула www.endusersharepoint.com. My latest article is up here: Выкарыстанне карыстацкіх спісаў для больш эфектыўнага кантролю рабочага працэсу (http://www.endusersharepoint.com/?p=1658).

Гэта графік адкрыцця ":

SharePoint Designer workflow doesn’t give us a lot of visibility into what’s happening with our workflow solutions. І, бачнасць, што мы сапраўды атрымліваем перашкаджае адносна бедных і інтэрфейс 60 day time window. Гэта 60 day window can be a major disappointment to new SharePoint Designer users because it’s not advertised by the tool itself. It’s not at all uncommon for someone to fire up SharePoint Designer, стварыць працоўны працэс, рашэнне, якое выкарыстоўвае "Уваход для гісторыі спіс" дзеянняў ...

Праблема ў тым, што пасля 60 дзён, любыя паведамленні, якія вы ствараеце такім чынам, будуць выдаленыя з спісу часопіса працоўнага працэсу! After a bit of teeth gnashing and “what were they thinking?"Аргументаў, Сутнасць заключаецца ў наступным: it happens and it needs to happen. Пытанне ў тым,, Як мы можам абыйсці гэта?

The official answer is to rely upon SharePoint’s built-in auditing feature. From an end user’s point of view, аднак, that’s very weak in WSS and not much better in MOSS. На шчасце, we can still leverage the familiar SharePoint Designer tool to create a durable workflow history and audit trail which is an order of magnitude more useful to boot. Here’s how.

I describe how to create a more friendly and useful audit solution for declarative workflow created in SPD.

I was inspired to write this article from a recent project for a client that had developed nine technical SPD workflows in support of one logical business process. Assuming for now that nine is a reasonable number, it was certainly a challenge to debug it or view the overall status of the process in one simple view. Each of these separate technical workflows has its own independent workflow history list and that’s just not manageable. I was able to combine all of them into a single audit list using the technique I describe on the site.

Праверце гэта.

</канец>

Падпісацца на мой блог.

Выконвайце за мной на Twitter у http://www.twitter.com/pagalvin