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.
<?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>
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)
Claiming the task via the java api does work… So try to use that then
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.
The activiti explorer is a part of activiti stack.
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.
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,
Hi,No that's fine. But as I said you can view the process instance already in the administration view of the Activiti Explorer.Best regards,