Go to file

Aaron Louie fd9c685979 Handles processes with multiple top-level elements		2020-02-10 15:20:45 -05:00
config	Travis configuration for connecting to postgres.	2020-02-05 15:17:47 -05:00
crc	Handles processes with multiple top-level elements	2020-02-10 15:20:45 -05:00
docs	Cleanup.	2020-01-09 10:09:59 -05:00
migrations	Updates list of allowed files. Removes unnecessary migrations. Note this will require a full wipe & reset of the database to work.	2020-02-05 17:23:37 -05:00
postgres	Gets docker-compose working.	2020-02-04 21:42:09 -05:00
readme_images	Updates to the README and removing a problematic dependency	2019-11-20 17:00:02 -05:00
schema	Adds basic Flask, Connexion, and SpiffWorkflow structure	2019-11-19 15:57:46 -05:00
tests	Adds workflow_spec_id back in to WorkflowApi	2020-02-07 12:36:08 -05:00
.gitignore	Gets docker-compose working.	2020-02-04 21:42:09 -05:00
.sonarcloud.properties	Adds new token	2020-02-10 10:03:21 -05:00
.travis.yml	Again...	2020-02-05 17:14:29 -05:00
Dockerfile	Trivial change to force travis docker push	2020-02-06 11:18:23 -05:00
LICENSE.md	Adds basic Flask, Connexion, and SpiffWorkflow structure	2019-11-19 15:57:46 -05:00
Pipfile	Converting this over to using Postgres. See the new postgres directory for a docker container to spin this up. Tests and development databases are the same, will try and get this corrected at some point.	2020-02-04 14:25:17 -05:00
Pipfile.lock	Returning better cleaner information about workflow with the workflow endpoint. Removes the get_all_tasks and get_user_tasks endpoints as tasks are returned with the workflow. Workflow endpoint also includes the last task and next_task, which may or may not be user tasks. The task "type" returned is now the class name of the task_spec, rather than just the word "task".	2020-02-07 11:34:44 -05:00
README.md	Updates in travis to do a push to docker hub, so our code can be deployed to various environments.	2020-02-05 15:53:52 -05:00
docker_push.sh	Scripts should be executable.	2020-02-06 09:02:02 -05:00
docker_run.sh	Adds command line option to reset database	2020-02-06 21:08:49 -05:00
example_data.py	Cleaning up the tests and making it easier to test workflows without adding them to the example data structure.	2020-02-04 16:49:28 -05:00
fact_runner.py	Creating a dependency on the SpiffWorkflow fork we created. and placing the command line script into this code base and demonstrating that our workflow processor works at least on that level. Removing all kinds of garbage that had piled up before to keep this thing clean.	2019-12-11 11:45:44 -05:00
run.py	Merge pull request #1 from sartography/fred/dockerize	2019-12-20 14:37:14 -05:00
sonar-project.properties	Adds sonar properties	2020-02-08 14:00:37 -05:00
wait-for-it.sh	Scripts should be executable.	2020-02-06 09:02:02 -05:00

README.md

CrConnectFrontend

CR Connect Workflow Microservice

Development Setup

Tools

These instructions assume you're using these development and tools:

IDE: PyCharm Professional Edition
Operating System: Ubuntu

Environment Setup

Make sure all of the following are properly installed on your system:

python3 & pip3:
- Install python3 & pip3
- Installing Python 3 on Linux
pipenv:
- Install pipenv
- Add ${HOME}/.local/bin to your PATH

Project Initialization

Clone this repository.
In PyCharm:
- Go to File > New Project...
- Click Pure Python (NOT Flask!!)
- Click the folder icon in the Location field.
- Select the directory where you cloned this repository and click Ok.
- Expand the Project Interpreter section.
- Select the New environment using radio button and choose Pipenv in the dropdown.
- Under Base interpreter, select Python 3.6
- In the Pipenv executable field, enter /home/your_username_goes_here/.local/bin/pipenv
- Click Create
PyCharm should automatically install the necessary packages via pipenv. For me, the project interpreter did not set set up for me correctly on first attempt. I had to go to File -> Settings -> Project Interpreter and again set the project to use the correct PipEnv environment. Be sure that your settings like simliar to this, or attempt to add the interpreter again by clicking on the gear icon.
With this properly setup for the project, you can now right click on the run.py and set up a new run configuration and set up a run configuration that looks like the following (be sure to save this run configuration so it doesn't go away.) :

Running the Web API

Just click the "Play" button next to RUN in the top right corner of the screen. The Swagger based view of the API will be avialable at http://0.0.0.0:5000/v1.0/ui/

Testing from the Shell

This app includes a command line interface that will read in BPMN files and let you play with it at the command line. To run it right click on app/command_line/joke.py and click run. Type "?" to get a list of commands. So far the joke system will work a little, when you file it up try these commands in this order:

> engine  (this will run all tasks up to first user task and should print a joke)
> answer clock (this is the correct answer)
> next (this completes the user task)
> engine (this runs the rest of the tasks, and should tell you that  you got the question right)

You can try re-running this and getting the question wrong. You might open up the Joke bpmn diagram so you can see what this looks like to draw out.

Documentation

Additional Documentation is available on ReadTheDocs

Additional Reading

BPMN Is the tool we are using to create diagrams of our business processes. It's is a beautiful concise diagramming tool. We strongly recommend you read this complete tutorial, as this notation is the foundation on which this project as well as many other software systems for businesses are built. Know it well.

Notes on Creating Good BPMN Diagrams in Comunda

Be sure to give each task a thoughtful (but unique!) id. This will make the command line and debugging far far easier. I've tended to pre-fix these, so task_ask_riddle if a task is asking a riddle for instance.