An interface for the job
A case queue, a form, the documents, the history and the next action. Design the screens around the process and test them with the people who will use them.
WyldLynx / Content Manager applications
Applications built on Content Manager
An interface for your process. A records design behind it.
WyldLynx builds applications around OpenText Content Manager. Bring the process that runs in spreadsheets, email or shared folders, and we can assess its interface, records, workflow and integration needs.
Build the application around your process
The complaints register in a spreadsheet. Contracts tracked by email. An information request that moves between an inbox, a shared folder and a whiteboard. These are useful starting points for an application conversation.
WyldLynx builds purpose-built interfaces around OpenText Content Manager. The design connects the work people do with the documents, metadata, permissions and records responsibilities behind it. Start with what the process needs, then decide which parts belong in Content Manager and which need another component.
What the application can bring together
Records capture and control
Agree which submissions, documents, emails and decisions become records, how they are classified and secured, and what happens when capture fails. Automation follows that design.
Workflow and deadlines
Bring approvals, due dates, assignments and escalations into the interface using the supported workflow and action-tracking options for the selected release.
Documents and signatures
Assess template-based document generation and electronic signatures, including DocuSign for Content Manager. Confirm components, entitlements and filing behaviour.
Connections to other systems
Assess supported service interfaces and the software development kit for the data the process needs. Define ownership, permissions, validation and error handling at each connection.
Reporting and access
Design reports from the process metadata. Web, mobile, Teams or Outlook access depends on the chosen architecture, supported components and user licensing.
Processes worth assessing
Correspondence, information-access requests, complaints and case work all involve documents, decisions and deadlines. Contracts, grants and board papers can raise similar design questions.
These are examples to assess, rather than a claim that WyldLynx has delivered every category. Bring a sample of the process, the records it creates and the controls it needs. We can then discuss a suitable pattern and relevant evidence.
A published case-management example
Information & Data Manager's November 2022 Metro North Health report names WyldLynx as the vendor for workshops, a proof of concept and implementation. It describes two record types, customised action tracking and a web interface for documents generated from templates.
The report records a Digital Transformation Award at the 2022 Micro Focus forum. It is a historical project account, rather than evidence of current rollout scope or a new client endorsement. Read the original 2022 report.
OpenText's published WyldLynx customer story also describes support tracking and training delivery on Content Manager. It discusses timesheet development as a planned rollout at the time of the story.
Use the records platform deliberately
Building on an existing records platform lets the design draw on its records model, access controls, retention and audit functions. Those controls still need configuration, testing and accountable operation for the new process.
Review user entitlements, application components and connected products before assuming the existing licences cover the design. A hybrid application can create additional data stores, and an AI connection still needs its own review of permissions, processing, copies, logs and outputs.
Read about information foundations for AI. Using supported interfaces helps maintainability; compatibility still needs testing against the target product version and dependencies.
Choose an architecture that fits
Content Manager-centred
Records, metadata, permissions and selected workflow in Content Manager, with a custom interface for the process. Assess this for work centred on documents and recorded decisions.
Hybrid application
Content Manager holds the records and documents while another application handles complex structured data, reporting or portal functions. Define where each authoritative item lives.
Connect an existing application
Keep a business application that already does the job and integrate the records it creates with Content Manager. Agree capture rules and reconciliation across the connection.
How an application engagement runs
Understand the process
Work with the process owner, users, records team and technical team. Identify the documents, decisions, exceptions and evidence of success.
Review a design
Set out the screens, records model, workflow, integration and reporting. Agree whether a prototype is useful, along with its scope, price and acceptance criteria.
Build and test
Use an agreed test environment and authorised representative data. Review the application with the people who will run and own it.
Deploy and hand over
Plan cutover, rollback, role-based training, documentation and ownership. Agree intellectual property, source-code access and operational responsibilities in writing.
Support and evolve
Define maintenance, response arrangements, supported versions and upgrade tests. Future changes and custom work need to be included in the agreed support scope.
Plan the application and its ongoing care
An application also needs an environment, operational ownership and people who know how to use it. Plan those alongside the build.
Content Manager hosting in Azure, Content Manager support, training, renewal and licensing review and Microsoft 365 integration are related services to discuss. Confirm inclusions, responsibilities and any additional charges in the proposal.
Common questions
Do users need to learn Content Manager?
Users can work through an interface designed for their process. Records staff and administrators may still use Content Manager clients. Training should cover the tasks and responsibilities of each role.
Do existing licences cover the application?
That depends on the users, access pattern, licensed modules, connected components and contract terms. Confirm the licensing position before committing to the design, including any external or read-only access.
Who owns the code?
Ownership, licensing, source-code handover and reuse of generic components are agreed in writing before work starts.
Will it work after an upgrade?
Test against the target release, supported interfaces and connected systems. Agree who checks compatibility, fixes issues and maintains the application. No unchanged-upgrade guarantee is implied.
Can Content Manager support a case-management application?
Yes. The published 2022 Metro North Health report is one example of a custom interface working with Content Manager record types and action tracking. The right design for another organisation depends on its process and controls.
Can you work with a hosted or on-premises environment?
We assess the selected environment, supported version, access, security and integration requirements before agreeing the deployment approach.
How do we start?
Describe the process, who uses it, the documents and decisions it produces, and what you need to improve. We can discuss a design review and an appropriate proposal.
Tell us about the process you want to improve
Bring the register, inbox, shared folder or manual hand-off. Tell us what happens today and what a useful result would look like.