Page Comparison

...

License Request

...

:

...

• A KRAD Document used to create a License Request Document

...

Description Tab:

• OwnerAssignee – default will be Initiator which will have KIM Person lookup
• Initiate licensing Workflow – drop down for manual workflow selection, used by KRMS to initiate Peopleflow
• Current Location – Editable by Initiator if the document not in current Rice workflow
• License Request Type – New/Renewal/Addendum
  • Renewal - New or final Agreement if method is renewal, will have an Active Date, where the new Agreement becomes the Current/Active, and the original is archived, but still linked
  • Addendum - Amended Agreement will become a supplemental to the original Agreement.Both are active. The parent/primary Agreement stays active, but is versioned by any changes in Addendum once final. Docstore needs to version these.

Event Log Tab:

• This tab will capture manual adds, and also system generated logs for each file attachment and workflow/routing completion
• For the manual adding and for Event view, a new UI - Event log view is used.

Agreement Documents Tab:

• The tab used for uploading agreement documents for different agreement types.
• This will have the columns date,user,agreement document type,label,file, notes and version.

Agreement(links):

• If no agreement is available for License request or linked to License request, Create button is displayed.
• If any agreement is available for license request or linked to License request, Edit button is displayed. Following meta data displayed for agreement link : last edited date,user,Agreement type, Agreement status, Agreement method, and links of that agreement.
• User can relink to different Agreement or delink the existing Agreement
• Create/Edit button will link to the existing or blank ONIX-PL Editor.

View Related Documents:

• Link to Requisition Document from where License request is created, is provided.

Notes and Attachments:

• These will not be linked with agreements.

*Adhoc Recipients:*

• Used for manual routing of document, not defined in standard workflow. It adds one more step to the predefined workflow and does not replace it. Adhoc routing can only be FYI or Acknowledgement.

Route Log:

• Shows predefined workflow/routing as per workflow definition. It also shows ad hoc tracking

License Request Search:

• Simple KRAD screen used for searching the existing License Request.
• User will be able to search all the License Request (not just assigned to him). Also can filter using title/status/date last modified/current owner and current location.
  

Agreement Search:

Simple KRAD screen used for searching the existing Agreement.

• This is used as a lookup in the License Request. User can search Agreements by agreement title, contract number
• "return value " will create copy and link the associated agreement to the License Request

 Order Holding Queue:

...

• .
• Participants:
• FrameWork: Rice2.x
• workflow:

License Request Workflow

Image Added

Compare License Flow
Image Added 

License Negotiation Flow
Image Added

License Request Search:

• Simple KRAD screen will be used to search the License Request Documents using the Title, License Request Status, Owned By, Current Location.
• The Result fields will be Doc Id, Bib Title, License Request Status, Date Last Modified, Initiator, Current Location.
• This Search will have the option for saving with a name, which can be used afterwards.
• Participants:
• FrameWork: Rice2.x

Manage CheckList:

• A simple KRAD Maintenance Document will used for upload/create, search, delete past checklist and update for checklist description and active status
• This will have checklist name,checklist author and active indicator as the search criterias.
• Participants:
• FrameWork: Rice2.x

Agreement Search:

• A simple KRAD screen which will search the agreement details from the docstore.
• Search filters will be agreement title, contract number, licensee, licensor/agent and the result fields will be agreement title, licensee, licensor/agent, date modified and the agreement method.
• Participants:
• FrameWork: Rice2.x

Requistion :

• Existing Transactional Document in Rice 1.x
• Contains a checkbox for the License Request initiation.
• Participants:
• FrameWork: Rice1.x
• workflow:

Image Added

Requisition Search:

• Existing Requisition Search screen in Rice 1.x.Extended the Requisition Search to have the new Licensing Workflow value ALNC- Awaiting Licensing Negotiation Completion,DLNF- Disapproved- License Negotiation Failed in the Requisition Status

...

• .
• Participants:
• FrameWork : Rice1.x

Order Holding Queue Search:

...

• Existing Order Holding Queue Search screen in Rice 1.x.Modified Order Holding Queue to have the new Licensing Workflow value ALNC- Awaiting Licensing Negotiation Completion,DLNF- Disapproved- License

...

Manage CheckList

Simple KRAD Maintenance Document used for creating and searching the checklist.

• Search using the filters checklist name,checklist author and active Indicator
• Upload/Create
• Delete past checklists
• Update Checklist Description, Active status.

• Participants:
• FrameWork : Rice1.x

Security:

General Business Rules :

• 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" from the License Request. It can be edited only through ONIX-PL license Editor.        

License Request Workflow

Image Removed

Compare License Flow
Image Removed 

License Negotiation Flow
Image Removed

Requisition Flow

Image Removed

Security:

 Roles :

 a) OLE_Licenses : OLE_Licenses are the assignees for Requisitions requiring licenses or license negotiations. This role is the "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

...

Addendum : Document first goes to Review Step. Upon completion document goes to Signatory step and upon completion goes to Approval step. 

Services:

Agreement lookup search :

• OleAgreementSearchService
  • getAgreementResults
  • getAgreementResults(Map agreementFilters)

License Request create/Search:

• OleLicenseRequestCreateService (invoked by requisition submit)
  • createLicenseRequest
• OleLicenseRequestService
  • generateAgreement
  • ingestAgreement
  • getLicenseRequestResults(Map licenseFilters)