Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-8292

Stunner - SLA due date property is missing check formatting

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Critical
    • None
    • 7.18.0.Final
    • Designer
    • NEW
    • NEW
    • 2019 Week 32-34

    Description

      SLA due date property for all nodes is missing check formatting. Currently it is possible to input any value there.

      See how SLA due date works in this post.

      Another possibility to prevent before inputting invalid value could be to use date picker.

      • UPDATE: the property value should be a time duration, so a date picker is not good option.

      Add a hint too - help messages

      Acceptance criteria

      Formatting validation for SLA Due Date property has been implemented for all nodes in Process Designer in both VSCode and Business central.
      Tooltip (hint) message is shown when hovering over the question mark next to the property.

      Attachments

        Issue Links

          is caused by

          Task - Represents a small unit of work that is not end-user facing. JBPM-7915 Stunner - User Task properties part #3

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBPM-8743 Stunner - date/time UI validation

          • Critical - To be worked on immediately following BLOCKER issues.
          • Open
          relates to

          Feature Request - Feature requests from customers and/or users JBPM-8441 Stunner - Start Event Nodes - SLA Due Date property

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Feature Request - Feature requests from customers and/or users JBPM-8480 Stunner - Catching Intermediate Event Nodes - SLA Due Date property

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Feature Request - Feature requests from customers and/or users JBPM-8540 Stunner - All Sub-process Event Nodes - SLA Due Date property

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Feature Request - Feature requests from customers and/or users JBPM-8573 Stunner - All Task Nodes - SLA Due Date property

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Feature Request - Feature requests from customers and/or users JBPM-8615 Stunner - Generic Service Task - SLA Due Date property

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. JBPM-8439 Stunner - SLA Due Date property for all state-based nodes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RHPAM-1033 Allow to model Process Level SLA in new process designer

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              jenrique@redhat.com Jaime Enriquez (Inactive)
              lterifaj@redhat.com Lubomir Terifaj
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: