12-15-2016 03:54 PM
Hello everyone, first of all I notice that I am new in Activiti, I come from the world of Oracle BPM 11g and I am trying to make a parallel between both solutions.
Punctually my question is how to get a user task to the Activiti-explorer inbox and the user selects it, this will trigger a html screen (js, jsp, etc).
Reading the user guide does not make it clear how you carry out that task. Indicates that you use the form-key property, but based on comments in the forums, I understand that this does not apply anymore from version 5.7. My version is 5.21
There is no complete example with this functionality.
If someone can tell me where I can get a process that works with this, I would appreciate it.
12-16-2016 01:18 PM
Hello Marcelo,
Form key is still the mechanism to implement external forms in 5.21 and even in 6.0.
Keep in mind, form key is simply another piece of metadata that in this case is bound to the task.
Think of it in the same way as business data key that is bound to a process instance.
There is no built in mechanism to exploit the form key. What you have to do is create an application framework that uses REST (or the Java API if you are using server side rendering) to retrieve the task details, then take the returned form key and act on it. The form key could represent an html page, or a json structure that your frameworks understands or XML. There is no restriction on what the form key string is or represents, it is simply a piece of metadata your application understands and knows how to handle.
As an example, I wrote a simple Alpaca EZForms integration a couple of years agi that you can find here:
It is dated as it was built for 1.14 and some of the REST API's I used were "legacy" API's so may no longer exist, but it should give you an idea of how to handle.
Hope this helps,
Greg
12-16-2016 01:18 PM
Hello Marcelo,
Form key is still the mechanism to implement external forms in 5.21 and even in 6.0.
Keep in mind, form key is simply another piece of metadata that in this case is bound to the task.
Think of it in the same way as business data key that is bound to a process instance.
There is no built in mechanism to exploit the form key. What you have to do is create an application framework that uses REST (or the Java API if you are using server side rendering) to retrieve the task details, then take the returned form key and act on it. The form key could represent an html page, or a json structure that your frameworks understands or XML. There is no restriction on what the form key string is or represents, it is simply a piece of metadata your application understands and knows how to handle.
As an example, I wrote a simple Alpaca EZForms integration a couple of years agi that you can find here:
It is dated as it was built for 1.14 and some of the REST API's I used were "legacy" API's so may no longer exist, but it should give you an idea of how to handle.
Hope this helps,
Greg
01-02-2017 01:40 PM
Thanks Greg, we will go for that solution
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.