🔍 Code Extractor

Browse Components

• function create_relationship

  Creates a directed relationship between two Neo4j graph database nodes identified by their UIDs, with optional properties attached to the relationship.

  File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 360-412

  neo4j graph-database relationship edge-creation cypher

• function create_node_and_ensure_relationships

  Creates a new node in a Neo4j graph database and establishes multiple relationships to existing nodes within a single atomic transaction.

  File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 258-358

  neo4j graph-database node-creation relationship-management transaction

• function get_next_document_number

  Atomically retrieves and increments the next sequential document number for a specific document type and department combination from a Neo4j graph database.

  File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 190-256

  document-management counter sequential-numbering neo4j graph-database

• function create_node_with_relationship

  Creates a new node in a Neo4j graph database and optionally establishes a relationship with an existing node in a single atomic operation.

  File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 98-188

  neo4j graph-database node-creation relationship cypher

• function _sanitize_properties

  Sanitizes a dictionary of properties to ensure compatibility with Neo4j by converting complex objects to primitive types, extracting UIDs from DocUser objects, and preserving datetime objects.

  File: /tf/active/vicechatdev/CDocs/db/db_operations.py | Lines: 21-39

  neo4j data-sanitization type-conversion graph-database property-mapping

• function get_next_status

  Determines the next logical status in a document lifecycle workflow based on the current status, using either configured transitions or a predefined fallback flow.

  File: /tf/active/vicechatdev/CDocs/models/document_status.py | Lines: 61-95

  workflow status-management document-lifecycle state-machine business-logic

• function is_published_status

  Validates whether a document status string represents a published or non-editable state by checking against a predefined list of non-editable statuses.

  File: /tf/active/vicechatdev/CDocs/models/document_status.py | Lines: 44-59

  validation document-management status-check workflow permissions

• function is_editable_status

  Validates whether a given document status string allows editing by checking it against a predefined list of editable statuses.

  File: /tf/active/vicechatdev/CDocs/models/document_status.py | Lines: 27-42

  validation status-check document-management permissions configuration

• class DocUser

  Extended User model for document management system. This class wraps and extends the existing User model in the system, adding document-specific roles, departments, and permissions.

  File: /tf/active/vicechatdev/CDocs/models/user_extensions.py | Lines: 24-939

  class docuser

• class ReviewCycle

  Model representing a review cycle for a document version.

  File: /tf/active/vicechatdev/CDocs/models/review.py | Lines: 220-1221

  class reviewcycle

• class ApproverAssignment_v1

  Model class representing an approver assignment within an approval cycle, managing the relationship between an approver and their approval task including status, decisions, and timeline tracking.

  File: /tf/active/vicechatdev/CDocs/models/approval.py | Lines: 1225-1506

  approval workflow assignment approver database-model

• class ApprovalCycle_v1

  Model representing a approval cycle for a document version.

  File: /tf/active/vicechatdev/CDocs/models/approval.py | Lines: 220-1221

  class approvalcycle

• class ApprovalComment_v1

  A model class representing a comment made during a document approval cycle, with support for resolution tracking and database persistence.

  File: /tf/active/vicechatdev/CDocs/models/approval.py | Lines: 22-216

  approval comment document-management workflow resolution-tracking

• class ApprovalCycle

  Model representing an approval cycle for a document version.

  File: /tf/active/vicechatdev/CDocs/models/approval_bis.py | Lines: 220-804

  class approvalcycle

• class ApprovalComment

  Model class representing a comment made during a document approval cycle, with support for resolution tracking and database persistence.

  File: /tf/active/vicechatdev/CDocs/models/approval_bis.py | Lines: 22-216

  approval comment document-workflow database-model graph-database

• function get_all_model_classes

  Retrieves a copy of the internal model registry containing all registered model classes mapped by their names.

  File: /tf/active/vicechatdev/CDocs/models/__init__.py | Lines: 98-105

  registry model-discovery introspection metadata BaseModel

• function get_model_class

  Retrieves a model class from a registry by its string name, returning the class type or None if not found.

  File: /tf/active/vicechatdev/CDocs/models/__init__.py | Lines: 86-96

  registry lookup factory-pattern model-management dynamic-loading

• function register_model

  Registers a model class in a global registry dictionary, enabling dynamic model lookup and management. Can be used as a decorator or called directly.

  File: /tf/active/vicechatdev/CDocs/models/__init__.py | Lines: 72-84

  registry decorator model-registration class-registration plugin-pattern

• class BaseModel

  Base class providing common data model functionality for all models in the system, including property management, serialization, and deserialization.

  File: /tf/active/vicechatdev/CDocs/models/__init__.py | Lines: 17-67

  base-class data-model orm serialization deserialization

• class DocumentVersion_v1

  Model representing a specific version of a controlled document.

  File: /tf/active/vicechatdev/CDocs/models/document.py | Lines: 43-696

  class documentversion