Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-489

Consider more explicit I/O mapping between rules and processes

    XMLWordPrintable

Details

    • Task
    • Resolution: Obsolete
    • Major
    • None
    • None
    • None
    • 3
    • 2019 Week 44-46 (from Okt 28)

    Description

      follows up on KOGITO-430.

      Current mapping may be considered too "magic". Consider a way to make data injection and extraction more "explicit"

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. KOGITO-590 Rules should "see" process variables

          • 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
          relates to

          Task - Represents a small unit of work that is not end-user facing. KOGITO-430 Complete Rule Unit input/output mapping

          • 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

          Activity

            People

              evacchi Edoardo Vacchi (Inactive)
              evacchi Edoardo Vacchi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: