Skip to end of metadata
Go to start of metadata

Purpose

Indicate the necessity for this enhancement. What does it accomplish?
Fix bug(s) where not having a document type label on the document type from causing errors in the KNS. See JIRA for example of error message thrown when document type label is missing.

Detailed Description

Give a detailed description for the enhancement. Clearly describe all concerns, eliminating ambiguities.
Document type label is not required on the document type document, but it's the only thing displayed many places and the KNS blows up if it's not specified. We need to make it required and provide an upgrade script for instances where it's not there currently.

Usage Scenarios

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

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):

  • The suggested solution should not have an impact on performance.

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. Update document_type making label required
  2. Update document type maintenance document making label required
  3. Create upgrade script to set default labels to "undefined" where it's currently null

Dependencies

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

  1. N/A

Issues

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

Functional:
  1. item
Technical:
  1. item
  2. item

QA or Regression Testing Plan

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

  1. Create a new Document Type document
  2. attempt to route the document with all but the Label field populated
  3. check for presence of Label requiredness error message upon route

Checkoff

Functional Analysis Complete? Yes (completed by SME)

Needs Review by KAI?No(completed by SME)

Technical Analysis Complete? Yes(completed by DM)

Needs Review by KTI? No (completed by DM)

Estimate: 8hr(completed by DM)

Technical Design: Link Here (completed by DM)

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

Final Documentation: Link Here (completed by DM)

Added to QA: No (completed by SME)

  • No labels