topic Re: JTA inside a java delegate in Alfresco Archive

JTA inside a java delegate

chimu — Thu, 16 May 2013 15:30:49 GMT

We have a Activiti workflow with UI developed using JSF , JPA and CDI. We have a submit screen which is associated with start-form-key and one User task which correspondsto the approver screen. I have some questions :-Q1) We have a requirement such that if Approver rejects the data then we need to s

Re: JTA inside a java delegate

chimu — Mon, 20 May 2013 05:51:01 GMT

I have one more question to include in addition to above one
Q5) If I commit my business data in in user task of final approver, then atleast I can show error message on his screen(on exception) and that task will still remain alive in his Inbox, but on other hand if I commit inside a service task then users will never come to know that final approved data never got committed to database, and their Task explorer will also not show any pending task. So what is best practice, to commit data in service task or in the last approver user task.

Re: JTA inside a java delegate

frederikherema1 — Wed, 22 May 2013 05:04:08 GMT

Q1: Best to move the screen to a user-task an loop-back. This allows you to have the process persisted with the right state and variables and there is no need to have duplicate logic (both for rendering start-form and rendering task-form with the same form).

Q2: You can just store the assignee the user selected as a process-variable. In the next task where the assignee should be set, use 'activiti:assignee="${assigneeSelectedWhenStarted}"' or use the BPMN2.0 counterpart (see user guide).

Q3: Again, use a process-variable so it's persistent and independent of environment (CDI). Use a gateway with conditions on the flow (e.g.. {$approved == "Yes"}, so it goes to a userTask with activiti:assignee="${initiator}" (having activiti:initiator="initiator" on you start-event).

Q4: Best to do this from the process itself, so all logic related to the process (getaways, tasks, DB-writes) is bundled and contained in one place to have a good overview.

Q5: If you're using JTA and the final task.complete() generates an exception, bot activiti entities and your custom entities will be rolled back. You can just show the error-message and the task WILL NOT be completed and will still be available. It's like the complete never happened…