Rainbird
  • 🏃‍♂️Getting started
    • What is Rainbird?
    • How does Rainbird work?
    • Example use cases
      • 📈Investment suitability assessment
      • 🤖Digital tax consultant
      • 🏥Covid risk assessment
      • 🚗Insurance claims liability
      • 💰Fraud identification
    • Hosting options
    • Quickstart guide
    • Onboarding with Rainbird
  • 🧠Knowledge Modelling
    • What is knowledge modelling?
    • What is a query?
    • Modelling
      • Concepts
        • Concept instances
      • Relationships
        • Question Configuration
        • Rules
          • Match, Infer, Ask process
          • Expressions List
      • Facts
      • Datasources
      • Other features
        • Markdown
        • Import/Export Knowledge Maps
      • Troubleshooting Tips
    • Testing
      • Manual tests
      • Automated tests
      • External User Acceptance Testing (UAT)
    • Versioning
    • Publishing
      • API Management
      • Setting a live version
      • Publishing an agent
    • Stats and Reporting
    • Managing your data
    • The library
      • How to: update a template
  • 🔍Evidence
    • What is evidence?
    • The Evidence Tree
      • The Salience Chart
  • 👩‍💻Developer guides
    • Overview
    • API Guide
      • API request flow
      • Run example queries
      • Environments
      • Error codes
      • Skipping an answer to a question
      • Retrieving a full Evidence Tree for use with a custom UI or application
      • Building an Evidence Tree URL
    • API interactive documentation
    • SDKs
  • Rainbird Labs
    • Overview
    • Consult
    • Generate from documentation
    • Co-author
    • /interact
    • /explain
Powered by GitBook
On this page
  • Publishing a version live
  • Enabling interaction history
  1. Knowledge Modelling
  2. Publishing

Setting a live version

Last updated 3 months ago

Publishing a knowledge map is the process of selecting the version that you want to be accessed by default via the Rainbird API.

This ensures that any external solutions integrated into the knowledge map will use the correct version by default, and supports continuous improvement as additional changes can be made to the knowledge map without impacting live solutions.

Once newer versions have been tested and signed off, the live version can be updated directly from the Studio.

Publishing a version live

To publish a version as live, navigate to the Publish tab, select the version to be published and select Set Live.

Enabling interaction history

Interaction history provides an alternative form of evidence and reporting on queries to the knowledge map. This can be enabled per version by clicking the Record Interactions checkbox.

🧠
Setting a live version