Jira Link
Jira Link
Jira Link
Jira Link
Jira Link
Jira Link
Rice2.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.
License Request Create UI
Simple 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:
- This will provide in adding of all types of agreement documents.
- This will have the columns date,user,agreement document type,label,file, notes and version.
Agreement(links):
- If agreement is not linked, then user can see the Create button.
- If a agreement is linked, then the user can see the Edit button and also displays the datas such as last edited date,user,type status, method, and links of that agreement.
- Create/Edit button will link to the ONIX-PL Editor.
View Related Documents:
- This will have a link to the Requisition Document from which it is created.
Notes and Attachments:
- These will not be linked with agreements and stored in docstore. This will be used
Adhoc Recipients:
- Used for undefined routing not in standard workflow – not for approval, but for FYI and Acknowledgement.
Route Log:
- Used for predefined workflow/routing per workflow table and also for 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
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
License Request Workflow
Compare License Flow
License Negotiation Flow
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
b) OLE_LicenseManager
c) OLE_Licensing_Approver
d) OLE_LicenseConfiguration
e) OLE_Signatory
f) OLE_User
g) OLE_LicenseViewer
h) OLE_LicenseReviewer