Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-139395

As an Operations Manager, I want to assign Task Nodes to Asset Creators, Resource Actions, Roles and Users

    Details

    • Type: Story
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: Master
    • Component/s: Workflow
    • Labels:

      Description

      As an Operations Manager, I want to I want to assign Task Nodes to Asset Creators, Resource Actions, Roles and Users so that tasks can be automatically assigned to the appropriate executors.

      Design Deliverables

      Mockup

      Context

      In order to satisfy the growing needs and expectations of our users, the Workflow builder technology needs to evolve. The current technology limits us from evolving and achieving our low-code first vision. It was therefore decided that we will replace the current Kaleo Designer of Workflow built in Alloy with a new and improved Workflow Process Designer built in React and leveraging the React Flow Library.

      This will allow us to not only improve the UI/UX of the feature, but also enable the company to drastically reduce the cost to maintain and develop new features in the Workflow Process Builder. Overall, this migration is key to the future goals of Workflow, the Low Code Initiative and Commerce Use Cases.

      As part of this migration, we will be migrating the Assignments property. Task nodes require interaction by people. Assignments are used to associate the task with the right people. You can assign Task nodes to specific Roles, multiple Roles of a Role type (Organization, Site, Asset Library, Account, or Regular Role types), to the Asset Creator, to Resource Actions, or to specific Users. Additionally, you can write a script to define the assignment. To read more about Assignments, please read the Learn.Liferay entry, Assigning Task Nodes.

      In this Story's scope, users should be able to:

      1. Assign Task nodes to the following groups:
        • Asset Creator
        • Resource Actions
        • Role
        • User
      2. View tasks that are assigned to them or their role in their My Workflow Task.
      3. Complete tasks that are assigned to them.
      4. Leave the Assignment Property sidebar and have their information autosaved. 

      Not in the scope:

      1. Assign Task nodes to the following groups (will be added in LPS-142768):
        • Role Type
        • Scripted Assignment
      2. Enable notifications for these assignments (this property will be added in LPS-139392).

      Acceptance Criteria

      Given that a user is defining a workflow process using the React Designer,
      when a Task node is added,
      then the user should be able to assign the task node to the Asset Creator.

      Given that a user is defining a workflow process using the React Designer,
      when a Task node is added,
      then the user should be able to assign the task node to a Resource Action,
      and define the Resource Action.

      Given that a user is defining a workflow process using the React Designer,
      when a Task node is added,
      then the user should be able to assign the task node to a Role.

      Given that a user is defining a workflow process using the React Designer,
      when a Task node is added,
      then the user should be able to assign the task node to a specific User.

      Given that a user is defining the Assignment property,
      when the user leaves the Assignment property and returns to the main node sidebar,
      then the Assignment information should be autosaved without alerting the user.

      Given that a Task has been assigned to a user, their role, etc,
      when the user opens My Workflow Tasks,
      then they should be able to view and complete that task.

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • Code with peer review completed;
      • Validated by QA, Product Designer and/or PM;
      • No critical bug related to Story scope (ex.: similar of FP4, FP5);
      • Make sure that all system documentation were updated (if necessary)
      • Make sure that it has the extensions points needed to allow GS and customers to customize the feature (If applicable)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              daniel.angotti Daniel Angotti
              Reporter:
              nara.andrade Nara Andrade
              Engineering Assignee:
              Product Team Zulu
              Recent user:
              Lucas Falcao
              Participants of an Issue:
              Product Designer(s) Assigned:
              Arthur Coninck
              Frontend Developer(s) Assigned:
              Carlos Montenegro
              QA Engineer(s) Assigned:
              Ana Buchmann
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master