WyldLynx / Content Manager capabilities
Content Manager capabilities
Explore the options. Check what your environment needs.
Find integration and development options grouped by the work you need to do, with the version, module, licensing and implementation prerequisites to check before choosing a solution.
Find the option that fits the task
This is a capability map, not a licence-inclusion list. Availability depends on the product release, edition, modules, third-party products, permissions and configuration. Select and perpetual editions have different bundled modules. Ask for an itemised confirmation for your environment. OpenText licensing documents provide the product terms; your agreement establishes your entitlements.
Product options, separately licensed components and WyldLynx-scoped work appear together so you can plan the whole requirement. The prerequisites column identifies what needs checking.
Work where your people already work
| Capability | Purpose | Availability and prerequisites |
|---|---|---|
| Microsoft Outlook (Zero Footprint add-in) | Capture email and attachments, search records and apply agreed filing rules through a supported Outlook integration. | Confirm add-in version, Microsoft licensing and configuration. |
| Microsoft Office (Zero Footprint add-in) | Save, check in and version Office documents through supported integration. Available functions can differ between applications and versions. | Confirm supported Office clients, add-in and licensing. |
| Office Online and co-authoring | Browser editing and collaboration workflows can connect documents with records controls. Check version handling and check-in behaviour in the proposed design. | Confirm Microsoft services, product versions and integration requirements. |
| OneDrive collaboration | Use supported check-out, collaboration and check-in workflows with OneDrive. Agree how edited versions return to the record. | Confirm version, Microsoft configuration and permissions. |
| Microsoft Teams integration app | Capture supported Teams content and work with records from Teams. Conversation types, channel coverage, metadata and multi-dataset behaviour need to be checked for the selected release. | Confirm app, supported content types, permissions and entitlements. |
| Content Manager Governance and Compliance for SharePoint | Apply supported records-management policies to selected SharePoint sites or libraries through a configured integration. Test lifecycle, hold and preservation behaviour. | Confirm Manage in Place and other required module entitlements. |
| Google Drive | Assess supported Google Drive collaboration or repository workflows for the proposed version and deployment. | Confirm current connector scope, permissions and entitlements. |
| EmailLink and Exchange Online | Configure supported server-side email capture and Exchange Online connection options. | Confirm component, authentication, Microsoft requirements and licence. |
| Custom Teams, SharePoint and Power Platform integrations | Scope filing rules, metadata mapping or workflow automation beyond the supported standard integration. | WyldLynx scoped development; feasibility and delivered examples to confirm. |
Capture and ingest
| Capability | Purpose | Availability and prerequisites |
|---|---|---|
| Data Port | Import or export supported record and metadata formats, with mappings and validation agreed for the task. | Confirm supported formats, version and entitlement. |
| SmartMove | Bulk import files and folders with metadata into Content Manager as part of an agreed migration approach. | WyldLynx product; confirm licence, version and project scope. |
| Kofax Capture template | Connect a supported scanning and capture workflow to records and metadata registration. | Confirm capture-product licence, template, compatibility and scope. |
| Mobile app capture | Capture supported documents or photos and carry out available mobile record tasks. Barcode and update functions vary by release. | Confirm mobile version, device, permissions and licensing. |
| Automatic container creation | Configure supported rules to create containers from dates or other agreed structures. | Confirm version, configuration and entitlement. |
| Geographic and photo metadata | Use supported location fields or image metadata where the file and configuration provide it. | Confirm supported metadata, mapping and entitlement. |
| Migrations from other systems | Scope legacy upgrades, dataset consolidation or migration from file shares, SharePoint and other systems. Agree mapping, reconciliation and exception reporting. | WyldLynx scoped project; source access and acceptance criteria required. |
Classify, automate and dispose
| Capability | Purpose | Availability and prerequisites |
|---|---|---|
| Business classification scheme and record types | Model record types, classification, retention and security rules around the organisation’s recordkeeping requirements. | Confirm configuration, authorities and product entitlement. |
| Auto-classification | Apply supported classification rules or content-analysis functions after testing them against representative records. Review accuracy and exceptions. | Auto-classification and analysis components may need separate licences; confirm edition. |
| Workflow and action tracking | Route supported approvals and tasks with responsibility, due dates and an audit trail. Client and mobile functions vary. | Confirm workflow scope, client support and entitlements. |
| Event-based archiving and recycle bin | Configure supported archiving events and recovery options. Confirm retention periods and recovery limits before relying on them. | Recovery is not a guarantee that permanently destroyed records can be restored. |
| Advanced disposal | Manage authorised retention and disposal review, approvals and processing. Holds, exceptions and accountable decisions remain necessary. | Advanced disposal is a separately licensed module in documented configurations; confirm edition. |
| SmartDispose | Support agreed disposal processing and reporting at scale, alongside the organisation’s authorised decisions. | WyldLynx product; confirm licence, supported version and workflow. |
| SmartLocations | Review and consolidate location records such as people and organisations within an agreed clean-up scope. | WyldLynx product; confirm licence and supported version. |
| Auto-redaction and annotation | Use supported viewing, annotation or redaction functions and configured processing where available. Validate the released output. | Confirm viewer, rendering, scripts and any separate component licence. |
| Custom filing rules and automation | Develop agreed registration rules, metadata processing and exception reporting through supported interfaces. | WyldLynx scoped development; permissions and compatibility testing required. |
Find and understand
| Capability | Purpose | Availability and prerequisites |
|---|---|---|
| Metadata and full content search | Search supported metadata and indexed document content. Results depend on indexing, formats, access and the selected client. | Confirm search configuration, index coverage and entitlement. |
| IDOL and document content indexing | Use supported OpenText indexing components to search document content. | Confirm supported search architecture and component licensing. |
| Elasticsearch integration | Assess supported Elasticsearch search infrastructure for the selected Content Manager version and workload. | Confirm supported versions, deployment and licensing. |
| Semantic search | Use supported semantic indexing and search to find related records by meaning. Evaluate results, access controls and indexing boundaries. | Release-specific capability; confirm availability, dependencies and entitlement. |
| OpenText Knowledge Discovery | Assess supported analysis such as classification, extraction, summaries or transcription for the chosen components and content. | Separate product/components; confirm exact capability and licensing. |
| OpenText Intelligence connector | Connect supported Content Manager data with analytics and reporting workflows. | Confirm connector compatibility and separate analytics licensing. |
| Dashboards and reporting | Use available dashboards and reports, or scope a report around an information or operational question. | Confirm client features; custom reports require agreed scope. |
Build and integrate
| Capability | Purpose | Availability and prerequisites |
|---|---|---|
| Web service interface | Use the supported web service interface to perform authorised record operations from connected applications. Operations vary by version and permissions. | Confirm interface version, deployment, authentication and entitlements. |
| .NET and Component Object Model development kit | Build against the supported object model for the relevant Windows or .NET environment. Available operations remain subject to permissions and version support. | Confirm supported development kit, client/runtime and licensing. |
| Web client customisation | Configure supported branding, navigation or page options and assess additional extensions where the client permits them. | Confirm current client extension points; bespoke work is separately scoped. |
| Enterprise Studio | Administer supported dataset, server, document-store and processing settings. | Confirm supported administrative functions and permissions. |
| Administration command line tool | Script supported administrative tasks through the documented command-line interface. | Confirm release-specific commands, permissions and runtime. |
| WebDrawer | Provide supported browser-based access to selected record information through a configured publishing interface. | Confirm publishing security, audience and licensing; do not assume licence-free access. |
| External document-management interface | Connect another system with supported document-management functions through the documented interface. | Confirm interface support, application compatibility and licensing. |
| SAP ArchiveLink connector | Assess supported SAP archiving integration for the relevant SAP and Content Manager releases. | Separately licensed connector and SAP requirements to confirm. |
| Line-of-business integrations | Scope automated filing, metadata mapping or record access for business systems such as property, finance, human resources or case management. | WyldLynx scoped development; feasibility depends on both systems. |
Govern content outside Content Manager
| Capability | Purpose | Availability and prerequisites |
|---|---|---|
| Manage in place | Apply supported governance to selected external repositories. Supported source types and operations differ; assess each repository separately. | Manage in Place/storage optimisation is separately licensed in documented configurations; confirm edition. |
| Holds on external repositories | Assess supported hold and preservation operations for a connected external repository and test their enforcement. | Confirm repository support, module licences and legal/records requirements. |
| Data Security Platform integration | Discover and review supported information sources, then design how selected records and metadata reach Content Manager. Masking or other actions depend on licensed components and configuration. | OpenText Voltage Data Security Platform is separate; integration work is scoped. |
| ControlPoint integration | Assess an existing ControlPoint deployment and its supported information-analysis or transfer workflow. | Separate product; confirm lifecycle, compatibility and licensing. |
| Physical records and warehouses | Manage supported physical-record, barcode, movement and warehouse workflows. External provider integration needs its own compatibility checks. | Physical-storage integration and provider components may be separately licensed. |
| Compliance exports and auditing | Assess the export formats, audit functions and security controls needed for the applicable records standard and selected release. | Confirm exact certification, export version, security configuration and entitlements. |
Sign, share and publish
| Capability | Purpose | Availability and prerequisites |
|---|---|---|
| DocuSign for Content Manager | Send supported records for electronic signing and return the signed material and related evidence through the configured workflow. | WyldLynx product; confirm supported versions and DocuSign licensing. |
| SmartLink | Share supported record links with an agreed audience and access policy. | WyldLynx product; confirm recipient access, expiry and licensing. |
| SmartZIP and SmartPDF | Package selected records or convert supported content to PDF within the agreed workflow. | WyldLynx products; confirm formats, metadata handling and licences. |
| Visitor access | Support a user registered in one Content Manager dataset visiting another dataset, where configured and permitted. | Cross-dataset access; confirm identity, permissions and licensing. Not a licence-free guest audience. |
| Viewing and rendering | View, annotate or render supported document formats through the selected components. Test redaction and conversion output. | Rendering and viewer components may require separate licences; confirm edition. |
Run it anywhere
| Capability | Purpose | Availability and prerequisites |
|---|---|---|
| Clients | Choose supported desktop, browser or mobile clients for the roles and tasks required. Features and device-management options differ. | Confirm platform support, client version and user licensing. |
| Deployment | Assess supported on-premises, cloud-hosted or managed deployment options against security, residency and operational requirements. | Confirm supported architecture, infrastructure and commercial terms. |
| WyldLynx cloud managed services | Scope hosting and operational support for a Content Manager environment, including agreed patching, upgrades and responsibilities. | WyldLynx service; confirm architecture and written service scope. |
| Identity | Configure supported directory, authentication and mail-service options for the selected deployment. | Confirm supported identity protocols, versions and security configuration. |
| Licensing | Compare the available perpetual, subscription or managed-service arrangement with the organisation’s needs. | Select and perpetual editions have different module inclusions; obtain an itemised offer. |
| Tiered storage and document stores | Place supported document stores on an architecture suited to the information’s access and retention requirements. | Confirm storage types, configuration and module entitlements. |
| Multitenancy | Assess supported tenant separation and administration for a shared-service design. | Confirm version, supported isolation model, configuration and licensing. |
Turn the map into an agreed scope
Choose the business outcome first, then check the required components and implementation. Agree security, licensing, acceptance tests, migration reconciliation and ongoing responsibilities before work starts.
Using supported interfaces can reduce compatibility risk, but upgrades and dependency changes still need testing. Support and maintenance apply only within the agreed scope. Review support options and custom development.
Common questions
Does Content Manager have a programming interface?
The product provides supported web service and development interfaces. Available operations depend on version, permissions and deployment; confirm the relevant documentation and entitlements before designing an integration.
Can it connect with our business system?
An interface, event or export from the other system can provide a starting point. Feasibility still depends on supported operations, authentication, data mapping, volumes and licensing on both sides.
Which integrations need an extra licence?
It varies by release, edition and agreement. Product documentation is not a statement of your entitlements. Confirm modules, separately licensed products and third-party requirements in an itemised offer.
Will an integration keep working after an upgrade?
Supported interfaces and compatibility testing reduce risk, but do not guarantee unchanged behaviour. Agree a test plan, maintenance responsibility and any remediation scope before the upgrade.
Can AI agents use records from Content Manager?
A supported integration can be designed around authorised access. Assess identity, permitted actions, provider processing, caches, logs and outputs; do not assume no information leaves the repository. Read the hub’s AI considerations.
Tell us what you need Content Manager to do
Name the system, the process or the problem. We can assess the supported options, additional components and development effort, then agree a suitable next step.