Eu reorganizou miña vida un pouco e atopei un tempo para enviar un artigo para www.endusersharepoint.com. My latest article is up here: Use listas personalizadas para Auditoría fluxo de traballo máis eficaz (http://www.endusersharepoint.com/?p=1658).

Este é o gráfico da apertura ':

SharePoint Designer workflow doesn’t give us a lot of visibility into what’s happening with our workflow solutions. E, a visibilidade que comezan é dificultada por unha interface relativamente pobre e 60 day time window. Este 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, crear unha solución de fluxo de traballo que aproveita o "Log Para History List" acción ...

O problema é que, logo de 60 día, calquera mensaxes que crea desta forma son excluídos da lista histórico fluxo de traballo! After a bit of teeth gnashing and “what were they thinking?"Os argumentos, a liña de fondo é esta: it happens and it needs to happen. A cuestión é:, como podemos contorná-la?

The official answer is to rely upon SharePoint’s built-in auditing feature. From an end user’s point of view, con todo, that’s very weak in WSS and not much better in MOSS. Afortunadamente, 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.

Consulte.

</final>

Rexístrate para o meu blog.

Siga-me no Twitter http://www.twitter.com/pagalvin