The meeting reviewed the process for requesting a contract in Contracts+ and outlined the necessary user permissions.
Key steps and benefits of using contract requests were discussed, including efficiency improvements for both requesters and contract managers.
Demonstrations highlighted end-user procedures and administrative configurations for streamlining contract initiation and approval workflows.
Considerations for further automation and customization were also introduced.
Action Items
(No due date – Admin team/IT): Review and configure contract request templates and required fields as needed for organizational needs.
(No due date – Admin team/IT): Evaluate whether to request JAGGAER representatives enable workflow robot automation for automatic contract creation post-approval.
Requesting a Contract in Contracts+
Users must have the “Contract Requestor” permission to initiate a contract request.
Contract requests are designed for users who identify a contract need but may not know all required content or lack contract creation permissions.
The typical request process involves naming the request, selecting a pre-configured template, completing required fields (marked by an asterisk), and submitting for approval.
Approved requests become accessible to authorized users (e.g., contract managers) in the 'Requests Ready for Contract Creation' section.
Contract Creation from Request
Contract managers can convert approved requests to contracts; information from the request auto-populates the new contract header.
Managers may edit or append information as needed, ensuring consistency and reducing manual data entry.
Requests and resulting contracts remain linked for traceability and easy navigation.
Automation and Configuration Options
Organizations may opt to further streamline the process by enabling a workflow robot to auto-create contracts upon request approval.
Only JAGGAER representatives or certified partners can activate this automation; customers must submit a formal request.
Demonstration and End-User Experience
Demonstration showed a user (Kate) submitting a contract request using a generic template, completing required and conditional fields.
The form may be configured to show/hide attachments or fields based on selections or administrative preferences.
Upon submission, users can track their request status, view workflow steps, and communicate with stakeholders within the application.
Decisions
Contract requests will be used for users lacking full contract creation knowledge or permissions — This supports efficiency and reduces errors in the contract initiation process.
Open Questions / Follow-Ups
Should the organization request JAGGAER to enable the workflow robot for automated contract creation after approvals?
Are additional templates or conditional fields needed to better fit common contract scenarios?