Component Features
Clause Module
| Overview | The Clause module is used to create, organize, approve, version, and reuse clause content. |
| Key Features | Clause creation, Draft management, Approval submission, Version control, Copy, Soft delete, Search, Filter |
| Key Fields | Clause Name (Unique name), Description, Category (e.g. HR, Offer Letter), Business Entity, Tags, Status, Version, Last Modified By, Last Modified On |
| Workflow | Create or edit a clause, save as draft or submit for approval, approver reviews in Workspace, then approves, rejects, or sends for rework. |
| Business Rules | Draft edits are creator-specific; delete is soft delete for eligible statuses, and versioning applies to selected status transitions. |
Clause Library Tabs
| Tab | Description |
|---|---|
| All Clauses | Shows all clauses |
| Active Clauses | Shows only active clauses |
| Pending Clauses | Shows only pending clauses |
Actions by Status
| Status | Actions |
|---|---|
| Active | View, Edit, Copy |
| In Progress | View only until approval is completed |
| Draft | View and Edit by creator, with Save, Submit, or Discard options |
| Rework | Creator can review suggestions, update, and resubmit |
| Rejected | Viewable by users for reference |
Approval and Controls
| Rule | Description |
|---|---|
| Approval enabled | Submitted clauses move to Pending/In Progress |
| Approver actions | Approvers can approve, reject, or send for rework |
| Versioning | Updates to selected statuses create new versions |
| Delete | Soft delete allowed only for Draft, Discarded, and Rejected |
Search and Filter
| Function | Supported By |
|---|---|
| Search | Clause name, description |
| Filter | Status, category, type, date range |
Template Module
| Overview | The Template module is used to build reusable document templates using approved clauses and signatures. |
| Key Features | Template creation, Drag-and-drop editing, Preview, Layout configuration, Copy, Delete, Approval routing, Versioning |
| Key Properties | Layout (Single/multi-column), Spacing, Header/Footer, Watermark, Preview, Section Copy/Delete |
| Workflow | Create a template, add approved content, configure layout and formatting, preview output, then save or submit for approval. |
| Business Rules | Template approval is based on business entity settings, and available actions depend on the current template status. |
Template Library Tabs
| Tab | Description |
|---|---|
| All Templates | All templates |
| Active Templates | Active templates |
| Pending Templates | Pending templates |
Available Actions
| Status | Actions |
|---|---|
| Active | Edit, Copy |
| Draft | Edit, Delete |
| Rework | Edit |
| Rejected | Delete, Copy |
Editing Experience
| Feature | Description |
|---|---|
| Drag-and-drop | Add approved clauses and signatures |
| Format settings | Header, footer, watermark, configuration |
| Layout | Single/multi-column options |
| Spacing | Alignment and distribution options |
| Section | Copy or delete sections |
| Preview | Preview before saving or submitting |
Approval Flow
| Step | Description |
|---|---|
| Pending | If approval required, templates move to Pending and appear in Workspace |
| Approver actions | Approvers can approve, reject, or send for rework |
Document Module
| Overview | The Document module is used to generate, upload, store, manage, and retrieve business documents. |
| Key Features | Single generation, Mass generation, Upload, Download, Pinning, Search, Sorting, Filtering |
| Key Fields | Name (Document name), Description, Created On, Category, Business Entity, Location, Actions (View, Download, Delete) |
| Workflow | Select a template or upload source content, generate one or many documents, store them in the library, and access them based on permissions. |
| Business Rules | Document actions depend on user access, and bulk creation follows the Excel upload format defined by the template fields. |
Document Generation Options
| Option | Description |
|---|---|
| Single Generation | Create one document by selecting a template, storage location, and description, then filling the required fields |
| Mass Generation | Download an Excel file, enter values for multiple records, upload the completed file, and create many documents at once |
Document Library Sections
| Section | Description |
|---|---|
| My Documents | User's own documents |
| Pinned Documents | Frequently accessed/pinned documents |
| All Documents | All documents in the library |
Additional Support
| Feature | Description |
|---|---|
| Search | Search for documents |
| Sorting | Sort documents |
| Filtering | Filter documents for faster access |
Workspace Module
| Overview | The Workspace module is used to manage review and approval activities across the application. |
| Key Features | Approval queue, Task visibility, Review actions, Due date tracking, Status monitoring, Audit support |
| Key Fields | Task Name, Transaction ID, Supplier, Vendor, System, Process, Due Date, Status, Actions (Approve, Reject, Rework) |
| Workflow | Reviewers open pending tasks, evaluate content, and take actions such as approve, reject, or send for rework. |
| Business Rules | Workflow routing is controlled by decision configurations, and all approval actions should be traceable for audit purposes. |
Admin Module
| Overview | The Admin module is used to configure platform-level rules and reusable setup data. |
| Key Features | Decision tree setup, Field catalog management, Naming convention control, Governance configuration |
| Key Areas | Decision, Field Catalog, Naming Convention |
| Workflow | Administrators configure workflow routing, maintain shared field definitions, and standardize naming practices for consistent system behavior. |
| Business Rules | Administrative configurations should apply consistently across libraries, approvals, and generated outputs. |
Configuration Areas
| Area | Description |
|---|---|
| Decision | Define approval workflows and decision trees based on business entity, approval levels, approvers, and stage progression |
| Field Catalog | Manage reusable global fields referenced across clauses, templates, and document generation |
| Naming Convention | Configure naming patterns for Clauses and Templates for standardization |
Signature Module
| Signature Module | |
|---|---|
| Overview | The Signature module is used to manage signatures that can be applied in templates and generated documents. |
| Key Features | Signature creation, Activation control, Entity-based assignment, Usage in document output |
| Key Fields | Signature Name, Business Entity, Status, Usage Context (templates, documents) |
| Workflow | Create a signature, validate activation eligibility, associate it with the required business entity, and use it during template or document creation. |
| Business Rules | Max 8 active signatures; only one active signature per business entity at a time; inactive signatures cannot transition directly to Active without satisfying activation controls and validation rules. |