User Tools
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:workflow_examples [2015/10/24 18:49] 127.0.0.1 external edit |
en:workflow_examples [2016/09/10 02:01] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Workflow Examples ====== | ====== Workflow Examples ====== | ||
| + | |||
| + | ??? I am looking at setting up a workflow to accomplish this: | ||
| + | <WRAP center round box 94%> | ||
| + | 1. if a trouble ticket is marked as //confirm resolution//, wait 3 days and send out an email if there has been no modification.\\ | ||
| + | 2. If it is not modified in 4 more days send an email alerting that it will be closed in 24 hours.\\ | ||
| + | 3. Mark the ticket as closed if it does not get modified in 24 more hours. (and include in description that it was closed due to inactivity) | ||
| + | </WRAP> | ||
| + | |||
| + | !!! This setup requires two workflows and a combination of conditions and configurations. It is an advanced workflow setup. Let's detail each step. | ||
| + | |||
| + | Our **first workflow** will detect the change of the ticket into the //confirm resolution// status and setup the emails to be sent out. The **second workflow** will check daily for inactive tickets and close them. | ||
| + | |||
| + | The **first workflow** looks like this: | ||
| + | |||
| + | {{ :en:corebos:workflow:ticketwfinformandclose01.png?800 |}} | ||
| + | |||
| + | where we can see that it will be launched against the **Trouble Tickets** module **every time the record is saved**. The workflow will look for the ticket entering the "Wait for Response" status and launch the tasks only when that happens. | ||
| + | |||
| + | It has two email tasks associated which look like this: | ||
| + | |||
| + | {{ :en:corebos:workflow:ticketwfinformandclose02.png?800 |}} | ||
| + | |||
| + | The important parts here are the 3 day delay in sending and the additional condition. When an email task is evaluated, in this case when the ticket enters "Wait for Response" status, it is automatically put in a queue for it to be sent. Once in the queue it will ALWAYS be sent. In this case we tell the system to send it 3 days from "now" so we get our 3 day offset BUT when the day comes we may not want to send it anymore because the ticket has had some changes. In this case we have to add additional conditions on the email itself to detect this case and abort the email if it shouldn't be sent. The condition I use is the "more than hours before" on the modified time and also that the status is still "Wait for Response". It is possible that just with the last condition we could have enough. | ||
| + | |||
| + | The 4 day offset email is identical but with the 4 day numbers. | ||
| + | |||
| + | The [[en:scheduled_workflows|scheduled workflow explanation has a nice image explaining]] the "more than" condition. | ||
| + | |||
| + | The **second workflow** is a scheduled workflow that launches once a day looking for inactive tickets and closing them after sending and email. That will be two task, and **update field** task to change the status and an **email task** to send the email. This looks like this: | ||
| + | |||
| + | {{ :en:corebos:workflow:ticketwfinformandclose03.png?800 |}} | ||
| + | |||
| + | {{ :en:corebos:workflow:ticketwfinformandclose04.png?800 |}} | ||
| + | |||
| + | |||
| ??? Me gustaría que cuando quedan 15 días para que llegue la fecha fin de un proyecto automáticamente envíe un recordatorio a su usuario propietario (asignado) recordándole que quedan 15 días. Igualmente cuando queden 10 y cuando queden 5. ¿Cómo podríamos hacer esto en CoreBos desde los flujos de trabajo? | ??? Me gustaría que cuando quedan 15 días para que llegue la fecha fin de un proyecto automáticamente envíe un recordatorio a su usuario propietario (asignado) recordándole que quedan 15 días. Igualmente cuando queden 10 y cuando queden 5. ¿Cómo podríamos hacer esto en CoreBos desde los flujos de trabajo? | ||
