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

As a Operation Manager, I want to update the due date a workflow instance while analyzing my process metrics


    • Story
    • Status: Closed
    • Minor
    • Resolution: Completed
    • None
    • Master
    • Workflow


      As an Operation Manager, I want to transition a workflow instance while analyzing my process metrics, so that I can have more options to act and solve problems to optimize my operation while analyzing its metrics.

      Design Deliverable


      Design Acceptance Criteria

      • Users can hover over a row to see action options and select to Update Task Due Date by hovering over the calendar icon.
      • User can select Update Task Due Date in the kebab menu for a particular row.
      • Single step modal window has a default fixed with of 600px, height of 420px
      • The current date/time is pre-populated into the Update Task Due Date form as how it is in My Workflow Tasks.
      • 2 step modal windows are large width at 896px with a height of 800px.
        • Users are required to select at least one task in order to proceed to the next step.
      • Success alert messages 
        • Single step: The due date for this task has been updated.
        • Multiple Step: The due dates for these tasks have been updated.
      • Date & time pickers
        • Date picker should use the updated date picker/calendar component in Lexicon/Clay. Functionality should remain the same in that users can either select with the UI component or enter in a date thru the text input.
        • Time picker can remain the same where users will select in a styled dropdown as seen in Figma and users can input the time thru text as it currently works in My Workflow Tasks.


      • States
        • Loading states for the modal are shown with a loading spinner and corresponding text (as specified in Figma);
        • If there is an unexpected/connection error, the modal displays the specific error state message in banner with a option to retry (as specified on Figma);
        • If there is an unexpected error, the modal displays the specific error state message in banner (as specified in Figma);
        • If there's an error for submitting/completing the action without selecting a transition, show the error banner and the inline error validation for the transition that hasn't been selected (as specified in Figma);

      Context - Update Due Date

      Today, the option to update the due date of a task in Liferay Workflow is only allowed through the "My Workflow Tasks" screen, where users can assign to themselves the available tasks for their roles and update the due date of their tasks.

      The goal of this feature is to also allow users to take this action while analyzing the Workflow Metrics of the process. Users should be able to select and update the due date of instances' tasks in the list of instances of the Workflow Metrics.

      Acceptance Criteria:

      • 1- Given a process built on Liferay Workflow with one or more instances open and registered, when the users is seeing the Instance Listing screen of the Process Workflow Metrics, then the user should be able to choose an instance to update the due date of one or more of its tasks;
        • Completed instances should not be available for due date update.
      • 2- Given an instance with two or more task open, when the user selects to update the due date of the instance in the Workflow Metrics, then the user should be able to select which tasks of the selected instance should be have the due date updated;
        • If there is only one open task in the instance, there is no need to prompt the user for the selection of tasks.
      • 3- Given that the user selected a workflow instance with more than one open task to have its due date updated, when the user selects one or more of those tasks and chooses a new due date to be updated, then the new due date selected and comments (if any applied) should be set for all selected tasks;
        • If the new due date isn't valid for any of the chosen tasks, the due date of that task should not be updated and the user should be notified.
      • 4- Given a Workflow Process configured in Liferay, when the user is updating the due date of a task of the process through the Workflow Metrics, then update due date action through the Workflow Metrics should respect the same limitations, constraints and business rules that exists for updating due date of instances though "My Workflow Tasks";
        • Users that doesn't have permission to update the due date of a task in the "My Workflow Tasks" also should not be able to update the due date of a task in the Workflow Metrics.
      • 6- Given a user updating the due date of a Workflow Tasks in the Workflow Metrics, when the user finishes the process of updating the due date of one or more tasks in the Workflow Metrics, then users should be informed that the update occurred successfully;
        • If problems occurred, the users should also be notified about the problems.

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • Verify if the test labels were added;
      • 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


        Issue Links



              dennys.barros.1 Dennys Barros.1 (Inactive)
              matheus.xavier Matheus Xavier (Inactive)
              SE Support SE Support
              Rodrigo Cunha Rodrigo Cunha (Inactive)
              0 Vote for this issue
              1 Start watching this issue




                  Version Package