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

Namespace Attributes - checkbox objects (entitled "Required" and "Active") should not be marked as required fields for this eDoc

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 0.9.3 - Build 3, 0.9.3
    • Component/s: Development
    • Labels:
      None
    • Environment:
      all
    • Similar issues:
      KULRICE-815Mark required rule fields from attributes with an asterix
      KULRICE-4156Required fields on group document not properly marked
      KULRICE-1886On Namespace document choices for Required and Active on a Default Attribute record don't hold
      KULRICE-1487Add REQUIRED and ACTIVE as fields to the Namspace Dflt Attributes table
      KULRICE-8090The Namespace Code and the Name should include "*" as they are required fields.
      KULRICE-7199Required fields not marked required on Send Event and Send Simple Notification
      KULRICE-2091Ensure that group type specific attributes only show up if they are active and that they are marked required if that's how they are defined for the group type
      KULRICE-8096Data Mapping Field Definition, Business Object Component Lookup - Namespace Duplications - KFS-PURAP/KFS-PDP
      KULRICE-4326prd:eDoc Lite:org.kuali.rice.kew.exception.WorkflowRuntimeException: org.kuali.rice.kew.exception.WorkflowRuntimeException: Error validating attribute edu.iu.uis.eden.routetemplate.attribute.AccountBasedOrgReviewAttribute Account Number is Required Acc...
      KULRICE-6867On Term Spec maint doc, namespace, name, and data type should all be required.
    • Rice Module:
      KIM
    • Application Requirement:
      Rice

      Description

      In the Namespace eDoc, on the Namespace Attributes tab, there are checkboxes to indicate whether the attribute you are creating is required, and if it is active. Checkbox entries should not be marked as required fields for the eDoc - it has no meaning in this context.

      Please remove the asterisk from these options. This is consistent with KFS display of the Active Indicator checkbox in the maintenance eDocs.

        Activity

        Hide
        Barb Sutton added a comment -

        changed from bug to improvement

        Show
        Barb Sutton added a comment - changed from bug to improvement
        Hide
        Aaron Godert (Inactive) added a comment -

        Nirmal, all that needs to happen with this one is remove the "required" property on the two attributes in the NamespaceDefaultAttribute.xml DD file.

        Then test to see if the * are gone on the Namespace maint doc.

        Show
        Aaron Godert (Inactive) added a comment - Nirmal, all that needs to happen with this one is remove the "required" property on the two attributes in the NamespaceDefaultAttribute.xml DD file. Then test to see if the * are gone on the Namespace maint doc.
        Hide
        Nirmal JosephSahaya (Inactive) added a comment -

        Hi Aaron,

        There is no 'required' property for these two attributes in the NamespaceDefaultAttribute.xml DD file. I just added 'required' property and set as false, though the * were there. so I then changed the required property as false in the NamespaceMaintenanceDocument.xml for these attributes, now the * are gone.

        is that OK? shall I commit the changes?

        Show
        Nirmal JosephSahaya (Inactive) added a comment - Hi Aaron, There is no 'required' property for these two attributes in the NamespaceDefaultAttribute.xml DD file. I just added 'required' property and set as false, though the * were there. so I then changed the required property as false in the NamespaceMaintenanceDocument.xml for these attributes, now the * are gone. is that OK? shall I commit the changes?
        Hide
        Aaron Godert (Inactive) added a comment -

        Yep, that should work, though I think we want to remove the required property from the NamespaceDefaultAttribute.xml and just have the ones set to false in the NamespaceMaintenanceDocument.xml file.

        Then I would say go ahead and commit after testing.

        Show
        Aaron Godert (Inactive) added a comment - Yep, that should work, though I think we want to remove the required property from the NamespaceDefaultAttribute.xml and just have the ones set to false in the NamespaceMaintenanceDocument.xml file. Then I would say go ahead and commit after testing.
        Hide
        Nirmal JosephSahaya (Inactive) added a comment -

        tested and the changes are committed

        Show
        Nirmal JosephSahaya (Inactive) added a comment - tested and the changes are committed

          People

          • Assignee:
            Nirmal JosephSahaya (Inactive)
            Reporter:
            Barb Sutton
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved:

              Structure Helper Panel