nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Activiti integration through an API

hmesha

Hi all,

I'm trying to integrate Activiti within an application through API calls. I have been spending time looking around the source code of Activiti to figure out the right entry point to this exercise. I have a few question that I'd appreciate an answer to. First, here's what I'm trying to do:

1. Configure the process engine programmatically
2. instantiate a ProcessEngine instance
3. Deploy a ProcessDefinition
4. Start a process instance
5. Query in-progress process instances of a particular process definition
6. Query the state of in-progress process instance
7. Associate an object (web form that has nothing to do with Activiti forms) with a task
8. Associate the task with a roles and users in LDAP store (active directory)
9. trigger an action in an exclusive gateway on a task

I managed to do 1 - 4

I'm struggling with 5-9. I'd appreciate pointers and maybe code examples of how to go about accessing the execution entities to perform those actions from the process engine.

Thanks,

Hany Mesha

Find more posts tagged with

Comments

frederikherema1

Hany,

5. This is quite easy, this can be done using the API with the ProcessInstanceQuery:

<br>List<ProcessInstance> instancesRunning = runtimeService.createProcessInstanceQuery().processDefinitionKey("myProcess").list();<br>

6. The ProcessInstance objects, queried in step 5 contain a lot of information about the process instance. To get the variables for the instance, use:
<br>Map<String, Object> vars = runtimeService.getVariables(instance.getId());<br>
7. Depends on what you are trying to do. If each task-instance has it's own object you'd like to store, you can use task-local variables (will be introducded in 5.1 release, comibg out in the beginning of january. If you want to use it as a resource as task-form, I suggest you read http://activiti.org/userguide/index.html#externalFormRendering

8. For setting candidat users/groups for a task, check out http://activiti.org/userguide/index.html#bpmnUserTask, section User assignement. The LDAP integration doesn't come out of the box, but as far as I know some members of the community are working on this. Not shure wat the current status is on that, do a quick search for 'LDAP' on the forum, that will get you started.

9. Not really sure what you are trying to do. It's possible to ruin custom java-coe when a task starts or completes. You can also add serviceTasks which perform you java-code.
check out http://activiti.org/userguide/index.html#bpmnJavaServiceTaskXML and http://activiti.org/userguide/index.html#taskListeners

hmesha

Hi Frederik,

Thanks very much for your reply.

#6, you mentioned that the process instance object variables can be used to obtain information about the current state of the process instance. Can you please elaborate what variables are set and what's their ID's?

For 7, 8, and 9 what I'm trying to do is to have a web application to allow a user to login and edit a form then perform actions that are represented by action buttons on the form. Those action buttons text should be populated from the workflow instance actions based on the current active activity the process is at. For example, let's take the loan request example that's is used in the user guide.

1. When the user logs in the web application and click on the loan request link, a process instance should be created but not start execution
2. The form loads for edit and the button text should be the next sequence flow that the process instance next operation is specified. In this case, it's 'Submit'
3. When the user submits the form, the workflow instance transition to the next state. Which in this case submitted
4. The workflow instance now automatically moves to the next set of candidate according to the process definition which is to advance the workflow intance to the candidates that will approve and reject.
5. When those candidate login to the web application should be able to see the buttons with text populated ('approve 'reject') which will be the possible directions on the process instance gateway.
6. Once a user clicks either on, the workflow instance advances to the execution path choosen by the user according to the process instance definition.

That's what I'm trying to achieve in my application. To do so, I'm writing a set of calls to interact with Activiti process engine that will either query the engine for information about where the process is at (current active activity), list of possible actions (destinations from the current active activity), signal a process instance execution (submit), perform a specified action by the user (approve or reject).

I think what I'm trying to do is achievable but requires more knowledge about how Activiti works!!

I appreciate if you can point me in the right direction to implement this in Activiti.

Thanks,

Hany Mesha