Skip to end of metadata
Go to start of metadata

Purpose

Indicate the necessity for this enhancement. What does it accomplish?
Applications may have roles that, when inactivated, indicate that the user is no longer an applicable user of the application. In these cases, the application should be notified when these actions (removal or inactivation) are made, through this notification, they can then take actions to remove the principal from any other roles they may have for that application either manually or programmatically using available APIs with KIM.

Detailed Description

Make a hook available on the RoleTypeService that gets invoked when members are removed or inactivated on the Role.

Usage Scenarios

Include at least one usage scenario, from the user's task perspective, that might be helpful in understanding the issue:

When someone is removed from the KFS-SYS role they may still be an active principal and have valid roles in other applications, but are no longer valid users of the financial system. However, removing them from KFS-SYS does not automatically remove them from linked KFS roles.

Mocks and Diagrams

Include any mocks (for UI enhancements) or diagrams that might be helpful in understanding the issue:

Performance

If applicable, list expectations for performance (optimal and worst cases would be fine, give time in seconds):

References

Include links to other confluence pages or external resources that might be helpful for this issue:

Requirements Listing

List all requirements (individual verifiable statements) that indicate whether the work for this item has been complete. If there are requirements that are not essential to the functionality but would be nice to have if time allows, enter those under 'Non-Essential':

Primary:
  1. Make a hook available on the RoleTypeService that gets invoked when members are removed or inactivated on the Role.
    1. Include the changes to a Role in a single notification:
      1. X was removed
      2. Y was added

Dependencies

List any functional or technical work that must be completed before work on this item can begin:

  1. item

Issues

List any issues that need to be resolved before work on this item can begin:

Functional:
Technical:

QA or Regression Testing Plan

List steps needed to test the basic functionality of this update, enhancement, bug fix

  1. test/steps
  2. test/steps

Checkoff

Functional Analysis Complete? Yes (completed by SME)

Needs Review by KAI? No(completed by SME)

Technical Analysis Complete? No(completed by DM)

Needs Review by KTI? No(completed by DM)

Estimate: 80 hours(completed by DM)

Technical Design: Link Here (completed by DM)

Jira: https://jira.kuali.org/browse/KULRICE-1157 (completed by SME)

Final Documentation: Link Here (completed by DM)

Added to QA: No (completed by SME)

  • No labels