Understand the platform.
Build with confidence.
Task-focused guidance for the SOLA product ecosystem. Use the instructions matched to your environment for detailed deployment and version-specific operations.
Getting started
Begin with the people, information, and outcomes your solution needs to support.
Choose a bounded first use case
Identify one clear business journey, its users, its source information, and its desired outcome. Map it to the relevant SOLA products.
Prepare access and ownership
Identify the administrators and business owners who will maintain knowledge, configure processes, and review access.
Configure and validate
Work with the implementation team on environment setup, roles, source content, and representative test scenarios.
Plan rollout and support
Train the initial users and agree how questions, changes, and support requests will be handled.
Documents & metadata
Organize information so people can find and use the right content.
Create a cabinet and folder structure
Use cabinets as top-level containers and folders for related documents. Decide how the structure reflects departments, projects, or business categories.
Define content types
Create document categories and their metadata fields. Choose fields that help the team search, validate, and manage the information.
Upload and review
Select the destination, upload the document, and complete the required metadata. Use preview and review to check the document and its details.
Work with versions
Add a new version when content changes. Use version history to download an earlier revision or restore the appropriate version.
Access & permissions
Define the people and roles that can work with your information.
Assign the right role
Give users the level of access needed for their responsibilities. Review administrative access separately from everyday content access.
Use inheritance deliberately
Cabinets, folders, and documents can inherit permissions. Use an override where a specific resource needs a different access rule.
Validate common access paths
Check viewing, downloading, editing, sharing, and managing content with representative user roles.
Review connected AI access
When connecting knowledge or actions to an AI experience, confirm the access model and available tools as part of the solution design.
Workflows & pipelines
Connect input, conditions, review, and actions in a clear process.
Model the business path
List the starting event, required inputs, responsible roles, decision points, and completion state before building the workflow.
Connect the steps
Use the visual designer to define routing, assignments, approvals, notifications, and conditional paths.
Include document processing
A configured pipeline can include classification, OCR extraction, metadata mapping, and human review.
Test normal and exception paths
Check approval, return, rejection, missing information, and any escalation behavior before rollout.
AI knowledge & RAG
Prepare relevant sources and check how the answer uses them.
Select approved sources
Choose documents, website content, and FAQs that your organization maintains as business knowledge.
Resolve outdated content
Remove obsolete information and reconcile conflicting requirements before preparing the knowledge base.
Test retrieval and references
Ask representative questions and check that the answer uses relevant material and provides useful references.
Maintain the knowledge
Assign source owners and review the questions users struggle to answer. Refresh source material as the business changes.
AI agents & chatbots
Connect conversation, knowledge, and configured business actions.
Define the experience
Decide who the agent or chatbot serves, what questions it should answer, and which channels are in scope.
Connect the knowledge
Use a prepared knowledge base to supply relevant business context for the conversation.
Scope the actions
List the tools and integrations an agent may use. Define the permissions and confirmation points for sensitive actions.
Validate the complete journey
Test questions, actions, incomplete knowledge, and the transition between guidance and an actual system operation.
Service management
Structure tickets, ownership, assets, and service commitments.
Define service categories
Organize the supported request types and configure the fields needed to investigate each one.
Set ownership and service rules
Map requests to the right teams. Define service commitments, notifications, and escalation around your operating model.
Maintain useful asset records
Keep the asset and configuration information needed by the service team connected to its support work.
Review pending work
Use reports and dashboards to understand workload, tickets awaiting action, and service performance.
Deployment & integrations
Plan around the version, infrastructure, and systems in your implementation.
Confirm the deployment package
Obtain the package and the instructions matched to your licensed product version and target environment from the SOLA team.
Plan environment dependencies
Review hosting, identity, networking, storage, backup, and the services required by the selected products.
Define integration contracts
Document the available APIs, authentication approach, business actions, and data mapping with the owners of each connected system.
Validate before release
Confirm user access, representative journeys, operational monitoring, backups, and support ownership in the agreed environment.