Skip to main content

Velox maintenance tools

Advanced tools can rewrite configuration or data and require backups, test-context use and change approval.

ToolPurpose/effectRequired checks
Resave modulesLoads and rewrites selected module serialisationFull configuration backup; identified compatibility/repair reason; capture failures; reopen and test every affected type
Unused Modules / Check UsageReads relation/usage candidatesResults depend on current relation metadata; manually verify scripts, external callers and linked relationships before archive/delete
Sync RelationsRebuilds module relationship metadataBack up, run in controlled context, compare usage before/after and investigate lost/unexpected relations
Create All File FoldersCreates configured File Connection foldersRuns with interactive identity; validate effective paths and then service-account access/ACL separately
Update PasswordsApplies credential changes across selected scopeProtect input, record exact scope, back up, coordinate rotation and test all dependent runtime Connections/Transports
Send Outbound Transports NowPrompts queued outbound processingRecord queue selection and reconcile receiver state; monitor one item before releasing a backlog
Create XSDInfers schema from XML samplesUse sanitised representative samples; generated schema is a draft requiring standards/data-owner/security review
Expand/Contract EDI FileTransforms EDI presentation for inspection/useWork on copies, verify separators/release/message version and byte-level output; do not overwrite sole source evidence
Convert PuTTY KeyConverts supported SSH key materialUse a protected working directory, validate output format/passphrase/ACL and securely remove temporary copies under policy

Change procedure

  1. Identify the exact symptom and tool effect; do not run a broad utility experimentally in production.
  2. Back up affected configuration/files and record context, version, counts and owner approval.
  3. Use test/non-production first with a small scope.
  4. Capture results/errors, reopen affected modules and run representative runtime tests.
  5. Reconcile queue/files/external state and retain the change evidence.

The visible Create Transports utility is customer/scenario-specific and is not a general supported creation workflow. The inactive/unconfirmed Database Upgrade UI is not documented as a normal tool; use the approved upgrade runbook.