Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-14064

People Flow does not add an annotation in Route Log

    Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.5.1
    • Fix Version/s: 2.6
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-9962Add a description field to People Flow stops that would appear in the route log or even the action list
      KULRICE-12555Rebuild People Flow
      KULRICE-6559People Flow Edit: exception thrown when adding / deleting delegates to people flow members
      KULRICE-8048People Flow - Adding roles to a stop allowed without selecting the role
      KULRICE-7972People Flow: No routing option for and/or in the same stop.
      KULRICE-9959Member Lookup missing from People Flow Maintenance screen
      KULRICE-2520route log does not show complete info when routing to kim roles, e.g. i can't even see who it went to
      KULRICE-6810People Flow Inquiry doesn't work
      KULRICE-275Add "service callouts" directly to the document type flow definition
      KULRICE-10166Adding an attachment or note to a people flow maintenance doc doesn't add the attachment
    • Rice Module:
      KEW
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      When routing documents using People Flow, the Annotation field is left blank.
      Please add an annotation giving similar appropriate information (the Role/Group associated with people flow stop?) in the route log annotation field.

      Steps to Recreate:
      1 Create a People Flow with a delegate structure
      2 Create an agenda that will call the PeopleFlow in a re-createable situation.
      3 Create a Document that will fire the agenda created in step 2 (KC Proposal Development Document is one choice)
      4 Open the route log and look at the Annotation for the included PeopleFlow nodes

      Attached is a screenshot of a RouteLog displaying the issue. It contains both Responsibility Node annotations highlighted in Blue and a People Flow annotations highlighted in red.

        Issue Links

          Activity

          Hide
          Daniel Seibert (Inactive) added a comment - - edited

          RE: attached screenshot. The blank people flow annotations are highlighted in red.
          Please provide similar info as shown in the Responsiblity Node annotations highlighted in blue.

          Show
          Daniel Seibert (Inactive) added a comment - - edited RE: attached screenshot. The blank people flow annotations are highlighted in red. Please provide similar info as shown in the Responsiblity Node annotations highlighted in blue.
          Hide
          Eric Westfall added a comment -

          Labeling as a near term item so we can knock this one out. However, we need to determine what language should be in the annotation here first so I'm going to flag this one as being blocked pending that decision.

          Show
          Eric Westfall added a comment - Labeling as a near term item so we can knock this one out. However, we need to determine what language should be in the annotation here first so I'm going to flag this one as being blocked pending that decision.
          Hide
          Eric Westfall added a comment -

          As per the suggestion on KRACOEUS-7415, the annotation should display the namespace of the peopleflow and the peopleflow name (see screenshot on linked jira to see how this is displayed for role namespace and role name).

          Show
          Eric Westfall added a comment - As per the suggestion on KRACOEUS-7415, the annotation should display the namespace of the peopleflow and the peopleflow name (see screenshot on linked jira to see how this is displayed for role namespace and role name).

            People

            • Assignee:
              Unassigned
              Reporter:
              Daniel Seibert (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel