How to Add an Action to the Three Dots Menu in a User Task

Flowable Designer
1

I am working on a case with a process, and I have a requirement to add a functionality that seems challenging. Here’s the scenario:

  1. Goal:
  • I want to add an action to the three dots menu (which, when empty, says “No available actions”) of a user task in the process.
  • This action should:
    • Close the current process.
    • Transition to a stage on the case level to set specific case-level flags.
    • Close the case entirely.
  1. What I’ve Tried:
  • On the case level, I’ve successfully implemented manual activations and user event listeners for similar actions. However, I can’t replicate this behavior at the process level for the user task.
  • Currently, I have an outcome button for the user task, but I want to move this functionality to the three dots menu instead of displaying it as a normal outcome button.
  1. Challenges:
  • I am unable to figure out how to add custom actions to the three dots menu of the user task without showing them elsewhere.
  • I also need to ensure that this action effectively communicates with the case to trigger the appropriate transitions and actions.
  1. Possible Alternatives:
  • Alternative 1: Add an action at the case level and expose it to the user task in the process.
  • Alternative 2: Create an action at the user task level that can:
    • Close the process.
    • Transition to a case-level stage to set the necessary variables.
    • Close the case.

I’m looking for guidance on the following:

  • Is it possible to add actions to the three dots menu in a user task?
  • If yes, how can I implement such an action to achieve the desired functionality?
  • Are there better approaches to achieve this functionality that I might have overlooked?
2

I solved it! But i must say there is no documentation around this…

Solution Approach:

  1. User Event Listener on Case Level:
  • I created a user event listener on my case and in UI configuration, I set:
    • Channels = menu
    • Expose as Action to Object with:
      • Scope ID = The task ID where I wanted to see the action in the three dots menu.
      • Scope Type = task
  1. Task Event Listener on User Task (inside the process):
  • On task creation, I used a Task Event Listener to fetch the task ID.
  • This task ID is then written back to the case level, allowing the case-level user event listener to identify the task and expose the action in its menu.