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.

transition arguments?

bedag-moo

Hi,

In a task-node with two outgoing transitions, I'd like to prompt the user for different data depending on which transition she selects (specifics below).

I'm curious how others approach this; the best approach I see is to define the properties for both transitions in the task model, map them in the web-client-ui, and have users ignore the properties for the transition they don't intend to use. Is there a better way?

Regards
moo

—

Specifics

In the process definition (excerpt)

   <task-node name="edit">
      <task name="bwf:edit" swimlane="editor"/>
      <transition name="Send for review" to="manager_review"/>
   </task-node>
   
   <task-node name="manager_review">
      <task name="bwf:manager_review" swimlane="manager"/>
      <transition name="Reject" to="edit"/>
      <transition name="Send for review" to="fork_review"/>
   </task-node>
   
   <node name="fork_review">
      <action class="org.alfresco.repo.workflow.jbpm.ForEachFork">
         <foreach>#{people.getMembers(bpm_groupAssignee)}</foreach>
         <var>reviewer</var>
      </action>
      <transition name="review" to="review"/>
   </node>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I want to prompt the manager for the reviewers only if he wants to have it reviewed.

Find more posts tagged with

Comments

claudio_martins

Your transition should move to a task-node that defines the custom model (the metadata) you want to request from the user.

bedag-moo

I could do that, but:

1) The manager has to open the task twice in order to send it to review, which is somewhat cumbersome if he has many tasks in his list.
2) The data-entry task will appear in the task history.
3) What if the user changes his mind after he has transitioned to the data-entry node?

In my specific use case, presenting the manager with the reviewer selection list even if he doesn't (yet) want to send the document for review seems a lesser evil. In general, I'll keep that technique in mind 🙂

Any other ideas? I was thinking about modifying the web client to take the user to a data entry wizard upon selecting a transition, but that would probably get quite involved?