Switching systems often comes with uncertainty, but with Vodori, the transition from Veeva Vault PromoMats or MedComms is smooth and intuitive. We’ve designed Vodori with a user-centric approach that surfaces functionality only when it’s relevant, keeping the experience simple and intuitive. Workflows are tailored to your specific business requirements, reducing the policies you need to memorize and making it easier to navigate the system successfully.
This guide walks through the key differences and terminology equivalents to support your success.
Terminology Comparison: Familiar Terms, Simpler Experience
While terminology may differ, the core functionalities remain consistent, ensuring a smooth transition.
| Veeva Term | Vodori Equivalent | Description |
|---|---|---|
| PromoMats | Vodori (Platform) | Central content and workflow hub |
| Document | Document (Material) | A core content item under review (e.g., brochure, email, video) with version tracking. |
| Binder | (No direct equivalent) | Vodori relies on metadata or directly linked Supporting Materials to associate content |
| Workflow | Job | The structured process for reviewing and approving content. |
| Task | Task | Assigned steps for both review and content preparation |
| Annotation/Comment | Annotation | Used to provide feedback or request changes on content. |
| Reference/Attachment | Reference/Supporting Document | Uploaded files used to support claims or statements in the material. |
| Document Workflow State | Document Status | Reflects the stage of a material (e.g., Draft, In Review, Approved, Expired). |
| Vault Configuration | Vodori Configuration | Vodori manages system setup, removing the burden from internal IT teams. |
| Verdict | Vote | Vodori votes are standardized: Approve, Amend & Progress, Amend & Return, Amend & Resubmit, Reject |
| License Type | Persona | Each user is assigned one persona per app. Personas available for Core Platform include Member, Reader, and Agency. |
| External User | Guest | Users outside your company who may have more limited access or authenticate with a different method. |
| Link Annotation | Reference Link | The connection made between highlighted text in your document and a reference or reference point, helping to support claims or content with precise evidence. |
| Anchor | Reference Point | A specific section within a reference document marked for substantiation purposes. |
System Differences at a Glance
Document Versioning & Due Dates
- Veeva: Users upload new versions into existing records. If configured, the system will update task due dates based on the overall review due date.
- Vodori: A new Job creates a new document version for a revision. The due date field is the overall review due date. Task-level due dates are not calculated by the system at this time.
Document Properties (Metadata)
- Veeva: To see the full metadata associated with the document, reviewers can click on the metadata panel or tab to expand it.
- Vodori: To see the full metadata associated with the document, reviewers can click on the Details button.
Annotations
- Veeva: Annotations are ordered from top of bottom based on their placement on the document.
- Vodori: By default annotations are ordered from top to bottom based on when they were added, but this sort order can be changed to their placement on the document.
Task Assignments and Tracking
- Veeva: Tasks listed in My Tasks; tracked via workflow history or custom dashboards.
- Vodori: Tasks shown on the Jobs Board; clear visual indicators of status and action needed.
Voting
- Veeva: Verdicts can be configured to short-circuit the workflow to cancel all other workflow tasks. Verdict labels are configurable.
- Vodori: All required reviewers must vote to end the current circulation. Vote labels are not configurable.
Document Relationships & Translations
- Veeva: Uses parent-child links, binders, and relationship fields for translations and references.
- Vodori: Uses linked references, reference points, or claims for substantiation, along with related Supporting Materials, to create easily referenced relationships. Parent-child links are created when documents are translated or localized. No binder concept; relationships managed through metadata and Supporting Materials.
Configuration & Metadata Management
- Veeva: Highly configurable; admins can manage document types, fields, lifecycles, and permissions. While this provides flexibility, it also introduces the risk of configuration drift (when changes accumulate inconsistently across environments) and staleness (when custom setups lag behind evolving best practices). These risks can increase complexity and long-term maintenance burden for IT teams.
- Vodori: Configuration is vendor-managed; customers request changes and Vodori implements them. This model provides less flexibility but ensures consistency, reduces the chance of drift or outdated practices, and lowers the maintenance burden. Customers benefit from guided best practices and proactive updates that keep configurations aligned with industry standards.
Multi-Document Workflows
- Veeva: Workflow tasks can be configured to include different types of verdicts—single versus multiple—when there are multiple documents in the same workflow.
- Vodori: Each job can contain one document.
Comments
0 comments
Article is closed for comments.