Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 1.1
-
Component/s: None
-
Labels:None
-
Request Controller:Albers, Stephan
-
External Supervisor:Please select
-
Executing Programmer:Please select
Description
There is a defined API. You can send an Event with a list of parameters (= process variables) to GrailsFlow. What other APIs are needed?
- startProcess
- sendEvent
- showWorklist (with a configurable list of columns?)
- showProcessList (security restrictions on change/schedule/kill process..)
- showProcessDetail
(return via XML (for embedding) or HTML (decorated or body only))
(security restriction)
Exists the problems with customization and using GrailsFlow-core plugin. This plugin does not provide the real API and documentation for it. In the SSM we should customize GrailsFlow-Core but we can not do it in correct manner, because don't know what we can change, but what not.
We should care about API of GrailsFlow-core.
- How i can see this API?
- How I can use it?
- What is API (for example: SecurityHelper is API, exists own impl in the GrailsFlow, but you can override it), but what is inner implementation (for example Domain Models is inner layer, external applications should not have access to it directly)
Missing API leads to the following open issues:
- Incompatible changes with previous version. We should try to avoid situation when jCatalog applications work with old Branches of GrailsFlow (Now SSM based on the branch which was created about 1 year ago).
- Not clear question: Is it possible for jCatalog application to use SNAPSHOT or we should use only released version of GrailsFlow-core.
- A lot of logic implemented into Controllers and GSPs of GrailsFlow. It must be a part of API. And we need approach how to customize UI in our applications.