Page Comparison

Technical Specifications for the 4 Maintenance Documents to be created for the License Agreement.

1) Agreement Method Maintenance Document Technical Specification

1. Agreement Method Maintenance (Create/Update/Search)

    a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Agreement Method record.

    b. Participants:

         OleAgreementMethod.xml

         OleAgreementMethodMaintenanceDocument.xml

         OleAgreementMethod.java

         OleAgreementMethod_UT.java

    c. Framework: Rice2.x

2. Security

    OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

    a. Roles:

• OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Agreement Method
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Agreement Method
• User - Can view the Agreement Method

    b. Permissions to do the following on the below entities:

       Agreement Method

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

    <class-descriptor class="org.kuali.ole.agreement.bo.OleAgreementMethod" table="ole_agr_mth_t">
        <field-descriptor name="agreementMethodId" column="AGR_MTH_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_agr_mth_s"/>
        <field-descriptor name="agreementMethodName" column="AGR_MTH_NM" jdbc-type="VARCHAR"/>
        <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
        <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
        <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
    </class-descriptor>

4. Services

5. Data Model:The DM for Agreement Method is going to reside in the Rice2.x Schema

2) Agreement Status Maintenance Document Technical Specification

1. Agreement Status Maintenance (Create/Update/Search)

    a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Agreement Status record.

    b. Participants:

         OleAgreementStatus.xml

         OleAgreementStatusMaintenanceDocument.xml

         OleAgreementStatus.java

         OleAgreementStatus_UT.java

    c. Framework: Rice2.x

2. Security

    OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

    a. Roles:

• OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Agreement Status
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Agreement Status
• User - Can view the Agreement Status

    b. Permissions to do the following on the below entities:

       Agreement Status

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

    <class-descriptor class="org.kuali.ole.agreement.bo.OleAgreementStatus" table="ole_agr_stat_t">
        <field-descriptor name="agreementStatusId" column="AGR_STAT_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_agr_stat_s"/>
        <field-descriptor name="agreementStatusName" column="AGR_STAT_NM" jdbc-type="VARCHAR"/>
        <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
        <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
        <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
    </class-descriptor>

4. Services

5. Data Model:The DM for Agreement Status is going to reside in the Rice2.x Schema

3) Agreement Type Maintenance Document Technical Specification

1. Agreement Type Maintenance (Create/Update/Search)

    a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Agreement Type record.

    b. Participants:

         OleAgreementType.xml

         OleAgreementTypeMaintenanceDocument.xml

         OleAgreementType.java

         OleAgreementType_UT.java

    c. Framework: Rice2.x

2. Security

    OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

    a. Roles:

• OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Agreement Type
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Agreement Type
• User - Can view the Agreement Type

    b. Permissions to do the following on the below entities:

       Agreement Type

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

    <class-descriptor class="org.kuali.ole.agreement.bo.OleAgreementType" table="ole_agr_type_t">
        <field-descriptor name="agreementTypeId" column="AGR_TYPE_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_agr_type_s"/>
        <field-descriptor name="agreementTypeName" column="AGR_TYPE_NM" jdbc-type="VARCHAR"/>
        <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
        <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
        <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
    </class-descriptor>

4. Services

5. Data Model:The DM for Agreement Type is going to reside in the Rice2.x Schema

4) Agreement DocType Maintenance Document Technical Specification

1. Agreement DocType Maintenance (Create/Update/Search)

    a. KRAD Design: A simple KRAD maintenance document will be used to create and update a new or an existing Agreement DocType record.

    b. Participants:

         OleAgreementDocType.xml

         OleAgreementDocTypeMaintenanceDocument.xml

         OleAgreementDocType.java

         OleAgreementDocType_UT.java

    c. Framework: Rice2.x

2. Security

    OLE_CAT namespace will be used for defining some Cataloging roles, and edocs

    a. Roles:

• OLE_Cataloging_Admin - Create ,edit and provide blanket approve for Agreement DocType
• Additional/Permitted Super User - Create ,edit and provide blanket approve for Agreement DocType
• User - Can view the Agreement DocType

    b. Permissions to do the following on the below entities:

       Agreement DocType

        a) Create

        b) Edit

        c) View(Inquiry)

        d) Blanket Approve

3. OJB-Mapping

    <class-descriptor class="org.kuali.ole.agreement.bo.OleAgreementDocType" table="ole_agr_doc_type_t">
        <field-descriptor name="agreementDocTypeId" column="AGR_DOC_TYPE_ID" jdbc-type="VARCHAR" primarykey="true" autoincrement="true" sequence-name="ole_agr_doc_type_s"/>
        <field-descriptor name="agreementDocTypeName" column="AGR_DOC_TYPE_NM" jdbc-type="VARCHAR"/>
        <field-descriptor name="objectId" column="OBJ_ID" jdbc-type="VARCHAR" index="true"/>
        <field-descriptor name="versionNumber" column="VER_NBR" jdbc-type="BIGINT" locking="true"/>
        <field-descriptor name="active" column="ROW_ACT_IND" jdbc-type="VARCHAR" conversion="org.kuali.rice.core.framework.persistence.ojb.conversion.OjbCharBooleanConversion" />
    </class-descriptor>

4. Services

5. Data Model:The DM for Agreement DocType is going to reside in the Rice2.x Schema