Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Maintenance
    • Application Requirement:
      Rice
    • Sprint:
      2.4.0-m3 KRAD Sprint 4
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      M: Automatically clears out secure fields upon a BO copy operation.
      1) Build a KRAD sample linked from the KRAD sample app / labs / maintenance page, and
      2) identify a KNS example.
      Add links to these in the corresponding row the Maintenance Gap Analysis wiki page (https://wiki.kuali.org/display/KULRICE/Gap+Analysis+-+Maintenance+Document) to these examples.

      The TravelerDetail has a masked secure fields. For the sample we'll need a maintenance document view and lookup to copy the BO.

      In KNS this was implemented in KualiMaintenanceDocumentAction.clearUnauthorizedNewFields

        Attachments

          Issue Links

            Activity

            eghm-kuali-m Erik Meade logged work - 05/Dec/13 7:21 PM
            • Time Spent:
              2 hours
               
              TravlerDetailMaintenance needs to be created, with _s MySQL table. TravelerDetail uses KNS controllers contact Corey about any problems I will cause him if I update it to KRAD controllers.
            eghm-kuali-m Erik Meade logged work - 06/Dec/13 2:10 PM
            • Time Spent:
              2 hours
               
              <No comment>
            eghm-kuali-m Erik Meade logged work - 09/Dec/13 8:20 PM
            • Time Spent:
              6 hours, 15 minutes
               
              Permissions aren't setup, worked a bunch on that, still not doign something right, have hacked permission in and working on next issue of no existing Id for doc type
            eghm-kuali-m Erik Meade logged work - 10/Dec/13 9:00 PM
            • Time Spent:
              5 hours, 20 minutes
               
              SQL to workaround Doc Type exception add properties to xml investigate various maintenance actions
            eghm-kuali-m Erik Meade logged work - 11/Dec/13 8:39 PM
            • Time Spent:
              2 hours
               
              Trying to get back to the place I was yesterday. Am getting the no id for document type TravelerDetailMaintenanceDocument, was getting past this point yesterday.
            eghm-kuali-m Erik Meade logged work - 12/Dec/13 10:53 PM
            • Time Spent:
              2 hours
               
              <No comment>
            eghm-kuali-m Erik Meade logged work - 13/Dec/13 1:54 PM
            • Time Spent:
              1 hour
               
              SQL Exception
            eghm-kuali-m Erik Meade logged work - 16/Dec/13 1:18 PM
            • Time Spent:
              1 hour
               
              <No comment>
            eghm-kuali-m Erik Meade logged work - 17/Dec/13 2:56 PM
            • Time Spent:
              15 minutes
               
              Labs Maintenance links
            eghm-kuali-m Erik Meade logged work - 17/Dec/13 4:36 PM
            • Time Spent:
              30 minutes
               
              Investigate and document some issues
            eghm-kuali-m Erik Meade logged work - 17/Dec/13 5:41 PM
            • Time Spent:
              15 minutes
               
              Track down KNS (KFS) example

              People

              • Assignee:
                eghm-kuali-m Erik Meade
                Reporter:
                cniesen Claus Niesen
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 day Original Estimate - 1 day
                  1d
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 days, 6 hours, 35 minutes
                  2d 6h 35m