Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info
titleJira Link

https://jira.kuali.org/browse/OLE-30

Info
titleJira Link

https://jira.kuali.org/browse/OLE-31

Info
titleJira Link

https://jira.kuali.org/browse/OLE-32

Info
titleRice2.x Framework

License Request is going to be developed using the new Rice2.x codebase which offers rich UI via the KRAD framework. The various features pertaining to License Request will be tested and demonstrated independently of OLE_Rice1.x. Workflow for License Request will be developed using KRMS framework. License workflow will be integrated with Requisition workflow which exist in OLE_Rice1.x.

...

  • Requisition can link to only one or no License Request.
  • A License request can link to one or many Agreement documents.
  • A License request can link to only one Agreement if License Request Type is New.
  • A License request can link to one or more Agreement if License Request Type is Renewal or Addendum.
  • Agreements can be linked to 1:Many Agreement Documents.
  • Version all Agreement Documents.
  • Upon uploading Agreement Documents through the License Request- the License Request, Requisition, Agreement, and Agreement Documents should be linked with each other.
  • Agreements can be linked to 1:Many License Requests.
  • Agreement meta data and content can only be "viewed" “viewed” from the License Request. It can be edited only through ONIX-PL license Editor.       

...

 a) OLE_Licenses : OLE_Licenses are the assignees for Requisitions requiring licenses or license negotiations. This role is the "owner" “owner” of the license agreement, and has full edit, attachment, routing, and status change permissions. Can create, edit, and delete Agreements. Can upload, edit, and delete Agreement Documents. Can edit a License Request to record events or send a license request. Can select only from allowable "intiate licensing workflow" options: License Needed, License Requested, Licence Received, In Process, In Negotiation

 b) OLE_LicenseManager : OLE_Licenses are the assignees for Requisitions requiring licenses or license negotiations. This role is the "owner" “owner” of the license agreement, and has full edit, attachment, routing, and status change permissions. Can create, edit, and delete Agreements. Can upload, edit, and delete Agreement Documents. Can edit a License Request to record events or send a license request. Can initiate any selection from "initiate licensing
workflow"

...

 h) OLE_LicenseReviewer: View only License Request and Agreement; download & upload agreement docs.

People Flow Logic : Below table lists the People Work flow based on the Rule. The rule need to pass two determinants (License Request Type and Agreement Method). Based on the Rule evaluation People Flow (workflow) Allowed,Not Allowed, Required determined.

Based on the user selection in drop down provided for Initiate License Workflow (selected by user in OLE_LicenseManager Role) and upon submission of document, the rule is evaluated and document routed to the users in People flow based on the selection.

If unallowable workflow status is selected, determined by the rule evaluation, the exception message ("Owner “Owner must select allowable workflow for this license request type and Agreement Method." ) is shown.

Rule

Allowed

*Not Allowed*

Required

Approval Requirements

License Request Type = New and Agreement Method= Negotiated License

 

Manual (Self), Signatory Only, Review Only, Approval Only Renewal, Addendum

Full Approval

Need to be approved by ALL USERS in role.

License Request Type = New and Agreement Method= SERU

Full Approval,Signatory Only
Review Only, Approval Only

Manual (Self), Renewal,Addendum

 

Need to be approved by ALL USERS in role.

License Request Type = New and Agreement Method = *Copyright Law*

Full Approval,Review Only, Approval Only

Manual (Self), Renewal,Addendum

 

ANY in Role.

License Request Type = New and Agreement Method = *Click Thru*

Review Only, Approval Only

Manual (Self), Renewal,Addendum

 

ANY in Role.

License Request Type = New and Agreement Method = *Shrink Wrap*

Review Only, Approval Only 

Manual (Self), Renewal,Addendum, Full Approval

 

ANY in Role.

License Request Type = Renewal and Agreement Method= Negotiated License

 

Manual (Self),Signatory Only, Review Only, Approval Only Full Approval, Addendum

Renewal

Need to be approved by ALL USERS in role.

License Request Type = Renewal and Agreement Method= SERU

Manual (Self),Signatory Only, Review Only, Approval Only Full Approval, Renewal

Addendum

 

ANY in Role.

License Request Type = Renewal and Agreement Method = *Copyright Law*

Manual (Self), Signatory Only, Review Only, Approval Only Full Approval, Renewal

Addendum

 

ANY in Role.

License Request Type = Addendum and Agreement Method= Negotiated License

Manual (Self),Signatory Only, Review Only, Approval Only Full Approval, Addendum

Renewal

 

ANY in Role.

License Request Type = Addendum and Agreement Method = SERU

Manual (Self), Signatory Only, Review Only, Approval Only Full Approval, Addendum

Renewal

 

ANY in Role.

 

Roles assigned to People Flow :

...