Unus de emergentes exemplaria invenio in innectis SharePoint solutiones leverages SharePoint Designer workflow, et opus Receptorem.
Hic est a negotio missionis ponerent in context:
- Ego upload a tabellae ut a doc lib.
- Ego calcitrare off multi-step usura workflow creavit SharePoint Designer.
- Ad punctum in quod processus, workflow assignat officium alicui (per colligere notitia de user negotium vel assignare).
- We want to use a KPI to track how long that task is awaiting completion. The KPI shows green for tasks that are completed or due more than 3 days from now. It shows yellow if the task is due tomorrow or today. It shows red if the task is past due.
- Hic 'CALCITRO: Volo diem festum esse qui pellit quod KPI-Conscius.
I can’t calculate a holiday-aware due date in SharePoint Designer workflow very easily. I would have to create a custom action or use a 3rd party tool. Autem, it’s easy enough to calculate such a date in an event receiver. Merge those two together and we get a pattern like this:
- Define a hidden yes/no site column on the document library labeled "DoCalcualteDueDate".
- Ut falsum illud Initialize.
- In tempore opportuno workflow (e.g. just before the "collect data" Actio), quod ad verum valorem assignaret.
- An ItemUpdate() event receiver looks to see if "DoCalculateDueDate" is true. Since the event receiver runs on every update, "DoCalculateDueDate" falsum est normaliter.
- Cum workflow assignat veram DoCalculateDueDate, Receptorem Supputat eventus feriae-date debitum conscia.
- Ubi ad rem facit accipientis Calculo, Nuntium ad hoc ponit falsam DoCalculateDueDate.
In finem, SPD workflow is communicated with an event receiver via the DoCalculateDueDate semaphore and we have holiday-aware due dates that are assigned at the exactly correct moment in the workflow’s life. SharePoint Designer controls when the due date is assigned but the event receiver performs the actual calculation and assignment.
</finem>
