[MGNLWORKFLOW-188] Allow registering openwfe custom functions Created: 03/Jun/08 Updated: 10/Jan/14 Resolved: 10/Jan/14 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
openwfe allows to have custom functions, to be used in wf definitions. our wf module should allow registering these through configuration. |
| Comments |
| Comment by John Mettraux [ 03/Jun/08 ] |
|
what about forgetting about those custom functions and focus on integrating the jruby version instead ? (Java 1.5 though) |
| Comment by Jan Haderka [ 03/Jun/08 ] |
|
Java 1.5 will be mandatory for Magnolia 4.0, but not before so we have to wait until then. |
| Comment by Magnolia International [ 03/Jun/08 ] |
|
And
|
| Comment by Philipp Bracher [ 05/Jun/08 ] |
|
note: Currently you can call all magnolia commands out of the workflow. So they can be used instead of custom functions |
| Comment by Magnolia International [ 10/Jan/14 ] |
|
As mentioned by Philipp, Magnolia commands are already useable, which should be a good enough solution. Meanwhile, we moved to jBPM, and I believe similar functionality/possibilities exist there. |