Actualización: Vexa este fío MSDN, especialmente a entrada do último: http://forums.microsoft.com/MSDN/showpost.aspx?postid=2631057&siteid=1. It describes a condition that may short circuit this whole thing. En resumo, pode ser tan sinxelo como facer polo menos un dos campos obrigatorios.
Eu teño unha biblioteca de documentos que soporta oito tipos de contido.
I have a SharePoint Designer workflow that wants to calculate and assign a "reminder date" simplemente subtraindo 30 día a partir de outra columna, "due date". This should only happen for one of the content types, "Insurance". The business objective is to produce a KPI that shows two categories of insurance documents: "about to expire" and "expired." (Podes ler máis sobre este tipo de KPI e máis substancial Drill-down aquí).
I have configured the workflow to fire when a new item is created and when an item is modified. The idea is that when an insurance document is uploaded, we calculate a "warning date" based on the expiration date. A pair of views work in connection with a KPI List to highlight these conditions when users hit their home page.
Esta estratexia non funciona cando cargar un documento.
I upload the document and I am presented with the meta data entry screen. Neste punto, I’m already in trouble. SharePoint has already, prematuramente da miña perspectiva, fired the workflow. I haven’t had a chance to pick the correct content type nor assign a due date. Á vez, the workflow does not fire when I hit the submit button at this time. There’s some built-in logic that "believes" that first submit is part of the "create" event. Así … meu traballo foi accionado e cando se executa, it was passed default meta data values.
The best work-around I know of is to insert a "pause until" activity in the workflow. I have the workflow pause for 1 minute. While it’s pausing, Seleccionar o tipo de contido correcto, enter the meta data and submit. The pause completes and the workflow proceeds as needed. (Teña en conta que no meu ambiente, timer workflow activities from SPD do not work out of the box. You may have the same trouble. Ver aquí para máis detalles).
I don’t like "magic delay" work-around. What happens if the user uploads a document and the phone rings and the ensuing conversation outlasts the pause? I can make the pause longer, pero eu non me gusta.
Eu escribín sobre iso no foro MSDN aquí: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2430725&SiteID=1