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

KRAD Demo Lookups Account name is now editable and not masked.

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.4
    • Fix Version/s: 2.4
    • Component/s: Development, JPA
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-13589Fill AFT Gap: KRAD Demo - Travel Account Bulk Update (Edit)
      KULRICE-11403Error adding Sub Account to KRAD Demo Travel Account
      KULRICE-11721Fill AFT Per-Screen Item Gap: KRAD Demo: Lookup (Basic)
      KULRICE-14059AFT Failure DemoTravelAccountLookUpAft testTravelAccountLookUp Travel Account Type Code quickfinder now defaults to CAT
      KULRICE-11715Fill AFT Per-Screen Item Gap: KRAD Demo: Travel Account Maintenance (Edit)
      KULRICE-9076Fix Criteria Masking on Lookups with encrypted fields
      KULRICE-13246Editing existing line using lookup on Lookup Collection Edit Line demo does not work correctly
      KULRICE-11163KRAD Demo Account Multi-Value Lookup Lookup collection name is required returning selected
      KULRICE-10216KRAD Demo Account Maintenance (Edit) Incident Report RiceRuntimeException: Exception trying to invoke action ROUTE
      KULRICE-10461Create Web Tests for KRAD Maintenance Document Masked Fields
    • Sprint:
      2.4.0-m2 Sprint 2
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required

      Description

      KRAD Demo, Demo - Lookup views, Lookup (basic) and Lookup Sample with Conditional Criteria Field, Account Name are editable and not masked. In 2.3 they were readonly and masked.

        Activity

        Hide
        Erik Meade added a comment -

        How Account Name appeared in 2.3

        Show
        Erik Meade added a comment - How Account Name appeared in 2.3
        Hide
        Erik Meade added a comment -

        How Lookup with Conditional Account Name was in 2.3

        Show
        Erik Meade added a comment - How Lookup with Conditional Account Name was in 2.3
        Hide
        Eric Westfall added a comment -

        My guess is that this is related to some of the JPA work. Assigning to Jonathan since he's been working on the sample app some and probably knows whether or not this is still a problem with some of the recent work he's put in.

        Show
        Eric Westfall added a comment - My guess is that this is related to some of the JPA work. Assigning to Jonathan since he's been working on the sample app some and probably knows whether or not this is still a problem with some of the recent work he's put in.
        Hide
        Jonathan Keller added a comment -

        It was something I pulled out because it did not make sense in the context of the sample application. I did not attempt to make it identical when I was converting it.

        If we have a list of features we want to demonstrate in the demo application (and that are not demonstrated in the Labs portion of the application), let's make a list and figure out how best to incorporate them rather than throwing features onto fields which don't make sense. This is part of our demo system after all, so the screens should make sense to someone viewing the application. (In this case, having a key field non-editable and no permission granted to be able to edit it in KRAD made the sample application almost unusable.)

        Show
        Jonathan Keller added a comment - It was something I pulled out because it did not make sense in the context of the sample application. I did not attempt to make it identical when I was converting it. If we have a list of features we want to demonstrate in the demo application (and that are not demonstrated in the Labs portion of the application), let's make a list and figure out how best to incorporate them rather than throwing features onto fields which don't make sense. This is part of our demo system after all, so the screens should make sense to someone viewing the application. (In this case, having a key field non-editable and no permission granted to be able to edit it in KRAD made the sample application almost unusable.)

          People

          • Assignee:
            Jonathan Keller
            Reporter:
            Erik Meade
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 4 hours
              4h
              Remaining:
              Remaining Estimate - 4 hours
              4h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Agile

                  Structure Helper Panel