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

Expand ExternalActnListNotificaionService once KualiCo Action list API is Ready

    Details

    • Type: New Feature New Feature
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.6
    • Fix Version/s: 2.6
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-14199REST-ful API for Action List
      KULRICE-14217SPIKE: Provisioning to external "action list" in real time
      KULRICE-3714Update PermissionService API with a method to check multiple permissions at once
      KULRICE-14220Implement authorization checks on api endpoints for groups, action list, and document search
      KULRICE-89integrate the document authorizer with the KEW valid actions API once it becomes available
      KULRICE-14223Implement authorization on Action List REST api
      KULRICE-5509Expand / Collapse UI problems
      KULRICE-7642RoleResponsibilityAction APIs are insufficient
      KULRICE-889New workflow API
      KULRICE-630Additonal KEN specific action list columns to be added
    • Rice Team:
      Middleware
    • Rice Module:
      KEW
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      KULRICE-14217 was completed. Part of that JIRA created the ExternalActnListNotificaionService which is a polling service that will be used to notify a KauliCo action list when changes are made to the KREW_ACTN_ITM_T.

      Once the KualiCo action list API is complete, the ExternalActnListNotificaionService needs to be finished.

      Main place where code will need to be added: ExternalActnListNotificationServiceImpl.notifyExternalActionList

        Issue Links

          Activity

          Hide
          Shannon Hess added a comment -

          From KULRICE-14217

          One remaining thought for person who implements the code in ExternalActnListNotificationServiceImpl.notifyExternalActionList —
          If updating the KREW_ACTN_ITM_T happens a lot, there is a chance the primary key to the new KREW_ACTN_ITM_CHANGED_T is not adequate. Sequence may need to be added? However, I'm not sure updating the KREW_ACTN_ITM_T is something that frequently (or ever) occurs.

          Show
          Shannon Hess added a comment - From KULRICE-14217 — One remaining thought for person who implements the code in ExternalActnListNotificationServiceImpl.notifyExternalActionList — If updating the KREW_ACTN_ITM_T happens a lot, there is a chance the primary key to the new KREW_ACTN_ITM_CHANGED_T is not adequate. Sequence may need to be added? However, I'm not sure updating the KREW_ACTN_ITM_T is something that frequently (or ever) occurs.

            People

            • Assignee:
              Unassigned
              Reporter:
              Shannon Hess
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel