Project Summary
OSWorkflow is fairly different from most other workflow systems available, both commercially and in the open source world. What makes OSWorkflow different is that it is extremely flexible. This can be hard to grasp at first, however. For example, OSWorkflow does not mandate a graphical tool for developing workflows, and the recommended approach is to write the xml workflow descriptors 'by hand'. It is up to the application developer to provide this sort of integration, as well as any integration with existing code and databases. These may seem like problems to someone who is looking for a quick "plug-and-play" workflow solution, but we've found that such a solution never provides enough flexibility to properly fulfill all requirements in a full-blown application.
In a Nutshell, OSWorkflow...
- ...
- ...
- ...
-
...
took an estimated 12 years of effort (COCOMO model)
starting with its first commit in December, 2002
ending with its most recent commit about 17 years ago
Quick Reference
Apache License 1.1
Permitted
Commercial Use
Modify
Distribute
Sub-License
Forbidden
Hold Liable
Use Trademarks
Required
Include Copyright
Include License
Include Notice
These details are provided for information only. No information here is legal advice and should not be used as such.
This Project has No vulnerabilities Reported Against it
Did You Know...
-
...
there are over 3,000 projects on the Open Hub with security vulnerabilities reported against them
-
...
learn about Open Hub updates and features on the Open Hub blog
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
search using multiple tags to find exactly what you need
30 Day SummaryMay 25 2016 — Jun 24 2016
|
12 Month SummaryJun 24 2015 — Jun 24 2016
|
