Workflow Tutorial - NeoSOFT-Technologies/workflow-plugins GitHub Wiki
Expense Claim Workflow
Description
Employees need to submit expense forms for their managers to approve, but if they all send them by e-mail, managers will find it difficult to keep track. Hence in this workflow, we have used the email format application that would be submitted by the employees. The process consists of an approval decision task, followed by an administrative task to pay the expense claim.
The manager may choose to only reject some items on the claim, in which case the process includes an additional task to list the rejected items, so that the person who pays the expense claim can recalculate the total.
Workflow Diagram
You can get all the details of this workflow here.
Activity Explanation
Explanation for highlighted activities are as follows:
1. HTTP Endpoint
HTTP Endpoint activity handles an incoming HTTP request. It allows to specify a relative path on your workflow server's domain.
You need to specify Path for the incoming HTTP request as follows:
2. Fork
The Fork activity simply forks workflow execution into multiple branches.
While adding this activity, you have to specify a list of one or more branch names. These branch names will be scheduled as activity outcomes.
3. Signal Received
Signal Received activity** suspends** workflow execution until the specified signal is received.
You need to specify the name of the signal to wait for.
4. HTTP Redirect
HTTP Redirect activity writes an HTTP redirect response.
You need to specify the redirect URL.
5. Send Email
The Send Email Activity enables you to send email from a Workflow.
Email activity has the following settings:
- From
- To
- Subject
- Body
- Attachments
