Stealth run of process with 'empty' user task

[udoderk]

Hi activiti friends and developers,
I use business process, created  with activiti designer. That process has an user task without defined form . I login as "kermit" on Activiti Explorer 5.10. ( I use the demo database). I deploy that process into activiti explorer 5.10 and start it.

After start appears the message about process start. I see no tasks (correct, such no defined), but if i delete such process, appears the dialog-warrning about, that process instance still running. I have expected that such a process must be stopped.

Something is buggy (imo), either compute of the running processes or endless run of such processes.

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:activiti="http://activiti.org/bpmn" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:omgdc="http://www.omg.org/spec/DD/20100524/DC" xmlns:omgdi="http://www.omg.org/spec/DD/20100524/DI" typeLanguage="http://www.w3.org/2001/XMLSchema" expressionLanguage="http://www.w3.org/1999/XPath" targetNamespace="http://www.activiti.org/test">
  <process id="processWithEmptyUserTask" name="processWithEmptyUserTask">
    <startEvent id="startevent1" name="Start"></startEvent>
    <userTask id="usertask1" name="Empty User Task"></userTask>
    <sequenceFlow id="flow1" name="" sourceRef="startevent1" targetRef="usertask1"></sequenceFlow>
    <endEvent id="endevent1" name="End"></endEvent>
    <sequenceFlow id="flow2" name="" sourceRef="usertask1" targetRef="endevent1"></sequenceFlow>
  </process>
  <bpmndi:BPMNDiagram id="BPMNDiagram_processWithEmptyUserTask">
    <bpmndi:BPMNPlane bpmnElement="processWithEmptyUserTask" id="BPMNPlane_processWithEmptyUserTask">
      <bpmndi:BPMNShape bpmnElement="startevent1" id="BPMNShape_startevent1">
        <omgdc:Bounds height="35" width="35" x="180" y="150"></omgdc:Bounds>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape bpmnElement="usertask1" id="BPMNShape_usertask1">
        <omgdc:Bounds height="55" width="105" x="260" y="140"></omgdc:Bounds>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNShape bpmnElement="endevent1" id="BPMNShape_endevent1">
        <omgdc:Bounds height="35" width="35" x="420" y="150"></omgdc:Bounds>
      </bpmndi:BPMNShape>
      <bpmndi:BPMNEdge bpmnElement="flow1" id="BPMNEdge_flow1">
        <omgdi:waypoint x="215" y="167"></omgdi:waypoint>
        <omgdi:waypoint x="260" y="167"></omgdi:waypoint>
      </bpmndi:BPMNEdge>
      <bpmndi:BPMNEdge bpmnElement="flow2" id="BPMNEdge_flow2">
        <omgdi:waypoint x="365" y="167"></omgdi:waypoint>
        <omgdi:waypoint x="420" y="167"></omgdi:waypoint>
      </bpmndi:BPMNEdge>
    </bpmndi:BPMNPlane>
  </bpmndi:BPMNDiagram>
</definitions>

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

[gokceng1]

I haven't tried but i think it is not buggy. You designed a process with a user task and this task doesn't have an assignee and a form. If this is the case someone could still claim(via rest) and complete it. So trying to delete a process which is running generates a warn and it should be.

[udoderk]

I haven't tried but i think it is not buggy. You designed a process with a user task and this task doesn't have an assignee and a form….

Oops, thanks, I forgot to assign it. ops:  ops:
Currently simply missing view "Running Processes without assignment". I experience the state "running" only when i want to delete the process definition  :cry:

If this is the case someone could still claim(via rest)

Claiming the task with REST API of Activiti does not work (imho).

[ronald_van_kuij]

Claiming the task via the java api does work… So try to use that then

[udoderk]

Claiming the task via the java api does work… So try to use that then

You are absolutely right that programmatically works, but an activiti-user is irritated (imho) when such process has been deployed, but it's run state appears nowhere on the Activiti-GUI.
I have jira wish created http://jira.codehaus.org/browse/ACT-1501

[frederikherema1]

Please keep in mind that explorer is a DEMO application to give an example on how activiti API and concepts could be used… The UI task-part is strongly focussed on assignment and candidate-user/groups, so it makes sense that (from a normal user perspective) you don't see those tasks. It's the responsibility of the developer/process designer to make sure tasks don't become unassigned/cadidate-less OR make sure an admin-console is built to track them down.

[udoderk]

Please keep in mind that explorer is a DEMO application to give an example on how activiti API and concepts could be used… The UI task-part is strongly focussed on assignment and candidate-user/groups, so it makes sense that (from a normal user perspective) you don't see those tasks. It's the responsibility of the developer/process designer to make sure tasks don't become unassigned/cadidate-less OR make sure an admin-console is built to track them down.

If one developer/process designer has forgot to assign the candidate-user/groups, how can these errors be found most quickly? Please keep in mind that developer/process designer not knows yet that this error has been made.
The warnings would be one way to signalize about it.
The view (e.g. only for admin users) in activiti explorer with such processes would be second way.
Own analysis for errors would be way.
The questions to activiti (core) developer would be other way.

P.S i know that activiti explorer as DEMO will welcome :mrgreen: But (imho) those days are long gone. The activiti explorer is a part of activiti stack.

[ronald_van_kuij]

The activiti explorer is a part of activiti stack.

development time, yes. And maybe to some extend for an admin during production, but if you develop a real application beyond vacation requests, it fails. That is not critisism, since as a demo app it serves its purpose very well. Maybe to wel, so people start using it for production.

[udoderk]

The activiti explorer is a part of activiti stack.

development time, yes. And maybe to some extend for an admin during production, but if you develop a real application beyond vacation requests, it fails. That is not critisism, since as a demo app it serves its purpose very well. Maybe to wel, so people start using it for production.

When the official documentations (API/Userguide/Toutorials/presentations) have to refer to the fact that activiti explorer is only the DEMO application, it would be better for proof of concept phase.

[trademak]

Hi,

Like Frederik and Ronald pointed out, the Activiti Explorer is not meant as a full admin application.
But you can already see that a user task is open in the new administration view of the Activiti Explorer 5.11.
We didn't add something yet to complete such a user task, but that shouldn't be too much of a problem.
Can you create a JIRA issue?

Best regards,