Questions People Actually Ask

Yes — Viora's drag-and-drop builder lets business teams design approval workflows, forms, and role-based access themselves, with IT retaining full governance and audit control. No custom code required.

Yes — Viora runs entirely behind your firewall or in your own private cloud, with role-based access control, full audit trails, and versioning built in, meeting the data-control requirements common in banking, manufacturing, and other regulated sectors.

Yes — Viora includes a visual entity builder for defining records, fields, and relationships directly, without writing SQL or involving a database administrator.

Yes — DocuOne routes any low-confidence field to a human reviewer automatically, instead of silently guessing, so uncertain extractions never enter your ERP unchecked.

DocuOne extracts invoices, contracts, and purchase orders using rules and templates by default — no AI required to get started. Structured Language Models (SLMs) switch on automatically for documents too inconsistent for a fixed template. Either way, validated data posts directly into your ERP, on-premise, with your documents never leaving your infrastructure.

Extraction accuracy improves continuously as the system processes more of your documents. The longer DocuOne runs on your specific document types, the sharper its extraction becomes — it doesn't stay static.

No. DocuOne processes every document inside your own infrastructure, on your own servers. No document, and no byte of it, leaves your environment during extraction — which is central to meeting compliance and data-control requirements.

Yes — Document Management brings uploads, email attachments, and scanned records into one searchable hub, with AI classification and automatic record-linking.

One search box covers metadata, file names, tags, vendors, and document numbers across every source — with list, card, and kanban views, plus folder and tag filters, so you're not hunting through separate folders.

Yes — scanned paper and low-quality images are read with OCR, turning them into searchable text rather than just a picture, so they show up in search alongside every other document.

Ghost-file detection flags orphaned or unreviewed documents, so something that slips through classification doesn't just quietly disappear — it gets surfaced for a human to look at.

Share links can be set to expire, watermarked, and protected with a password or OTP, with full control over whether the recipient can download, print, or copy — and a complete record of who opened or acted on the document.

Yes — every classification, link, and share event is logged and timestamped, giving a complete trail from when a document arrives to whatever happens to it afterward, along with dashboards on intake volume and document mix.

Yes — the Document Package Workspace builds a checklist of required documents automatically, flags anything missing, routes the package through approval, and locks the finished set into a versioned release that gets shared as one secure bundle.

Yes — a certified copy is generated separately from the source file, which stays completely untouched.

Retention periods are configurable per document category, from 1 to 7 years, so nothing is discarded early or held longer than necessary.

Yes — AssureSuite automates API, UI, and end-to-end test coverage across releases, reducing manual regression effort.

Yes — AssureSuite plugs directly into CI/CD pipelines like Jenkins, running automated tests on every build and blocking deployment if tests fail.

Test suites run in parallel across multiple environments and browsers instead of one after another, so a full regression pass doesn't have to happen overnight — teams get results without waiting for sequential runs to finish.

Results are reported back where developers already look — inside GitHub Actions, Jenkins, or whichever CI/CD pipeline is already in use, alongside the automatic test runs triggered on every code push.

Yes — ZeroBot is a zero-license-fee RPA runtime; you can deploy unlimited attended and unattended bots without per-bot costs.

Attended bots run on a user's desktop alongside their work, triggered on demand; unattended bots run independently on a server on a schedule. ZeroBot supports both from the same platform.

Every step a bot takes is logged, and IT gets full visibility through command-line tools, transparent logs, and Orchestrator-Lite's scheduling — so what's running and when is never a mystery.

Yes — API Engine connects SAP, Salesforce, REST APIs, and webhooks with visual field mapping, requiring no code to configure.

Yes — API Engine is built specifically for this: it maps fields between SAP (or other ERPs) and external systems visually, then keeps data in sync automatically.

API Engine supports bidirectional, automatic sync once a connection is configured — changes on either side propagate without manual re-entry.

Every connection tracks synced and failed records separately, so failures are visible immediately rather than silently missed — the dashboard shows exactly how many records went through and how many didn't on each sync.

Data can be reformatted, rounded, combined, or translated as it moves between systems — set the transform once and the engine applies it automatically on every run, not just copied as-is.

Yes — every inbound request through a webhook endpoint is verified before it touches your data, so external systems can trigger actions securely without exposing your data to unverified pushes.

Yes — PDF Engine generates branded, professional PDFs automatically from any business record — invoices, purchase orders, contracts, payslips — with zero manual formatting.

Yes — your logo, colours, address, and tax details appear on every document, and different divisions can carry their own branding without needing a developer to make the change.

Yes — you choose which sections appear on each document, such as headers, line items, totals, and signatures, and map your data to each one, with no design skills required.

Yes — generation can trigger automatically once a record reaches the approved stage, producing hundreds of documents in the background at once with no manual clicks.

No — documents are only generated once a record reaches the approved stage; premature issuance is prevented by design, not just by policy.

Yes — every document generated is logged: who triggered it, when, which template was used, and the file produced, and that history can't be altered or removed.

Yes — Notification Engine routes one triggering event to the right person across Email, Microsoft Teams, and in-app notifications, based on your workflow rules.

Yes — action buttons embedded directly in the notification email let recipients approve, reject, or act on a record with one click, without opening the application.

Recipients are defined by role, workflow stage, or assigned field, and the engine resolves the right people at the moment of sending — there's no fixed list to maintain as people or roles change.

Reminders can be set to fire before a deadline, after a record is created, or when nothing has happened for a set number of days — the engine runs the follow-ups automatically, so nothing falls through the cracks.

Yes — every notification sent is logged by channel as delivered, failed, or pending, along with the full recipient list and any error detail, so nothing goes out without a record of it.

No — one configuration covers Email, Microsoft Teams, and in-app notifications at the same time, so a single event setup reaches every channel instead of configuring each one separately.