# laravel_workflower

**Repository Path**: bpmn-php/laravel_workflower

## Basic Information

- **Project Name**: laravel_workflower
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 1
- **Forks**: 0
- **Created**: 2020-12-05
- **Last Updated**: 2022-11-11

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# Workflower with laravel. A Bussines Process Implementation with PHP

## Table of Contents

- [Introduction](#introduccion).
- [Installation](#installation)
- [The workflow diagram](#the-workflow-diagram)
- [Sourcecode](#sourcecode)
- [Screenshots](#screenshots)

## Introduction

This project is an example of https://github.com/phpmentors-jp/workflower  BPMN 2.0 workflow engine and Laravel 5.8 Framework integration.

I used https://github.com/77web/workflower-bundle-playground example as basis.

The bpmn file can be viewed and edited with comunda modeler. The service tasks are not supported by the visual editor but you can edit directly in the source code.

## Installation

Run composer install and and php artisan migrate command.

## The workflow diagram

![documentation/img/pullrequest_process.png](documentation/img/pullrequest_process.png)

## Sourcecode

### Workflow implementations

The class Process does the magic and we focus in this.

This class needs three class to work.

1. A **WorkItemContextInterface** implementation (**PullRequestWorkflow**).  This class has the workflow bpmn file name saved in the storage/app/process path.
2. A **Bpmn2WorkflowRepository** implementation (**WorkflowRepository**). The phpmentors-jp/workflower has an implementation but is useless for laravel projects.
3. A **MergePullRequestOperationRunner** implementation (**MergePullRequestOperationRunner**). This class contains the logic used by the service task merge PR. For laravel projects you most consider replace service task for simple task and use Jobs.

Additionally to this classes I create the class Workflow/Entities/**PullRequest** that implements ProcessContextInterface and WorkflowSerializableInterface interfaces. This class it is a data structure that has the necessary data for the workflow to work.

With this classes create a Process instance. 

```php
$repository = new WorkflowRepository();
$pullRequestWorkflow = new PullRequestWorkflow();
$operationRunner = new MergePullRequestOperationRunner();
$process = new Process($pullRequestWorkflow, $repository, $operationRunner);
```
We set the instance in the Usecase class and pass the Pullrequest instance in the run method.

```php
$usecase = new CreatePullRequestUsecase();
$usecase->setProcess($process); // createProcess() method in the controller class
$entity = $usecase->run($pullrequest); // $entity attribute in the controller class
return $entity;
```
### Laravel

For persistence I create a eloquent model Models/**PullRequest**. This class save the data in the database including the serialized workflow.

The **PullRequestController** is the application's start point. This class makes the calls to the workflower engine through Usecase classes.

## Screenshots

![lista de pullrequest creados](documentation/img/index.png)

![documentation/img/index.png](documentation/img/create.png)

![documentation/img/index.png](documentation/img/review.png)

![](documentation/img/fix.png)