... | ... | @@ -35,4 +35,4 @@ Below the class diagram of the base classes for the action. |
|
|
|
|
|
* Regarding the UI stuff we should probably include a layer which translates the configuration options to a Quickform, Angular or whatever UI system might be used in the extending system.
|
|
|
* Tim suggested that a good way to start on this is to put the interface in this extension and that start working on an implementation of it in the form-processor-designer extension. This way I might get some gutfeeling on how things work.
|
|
|
* An action has a set of contexts where it could operate in. |
|
|
\ No newline at end of file |
|
|
* An action has a set of contexts where it could operate in. For exmaple it requires on contact as input, or it requires multiple contacts, or it could be used as an action after searching etc... |
|
|
\ No newline at end of file |