vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Websheets](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=views-websheets)

You can work with websheets in Planning Analytics with Watson. You can create and work with sandboxes in websheets, and you can combine websheets and views on the same sheet.
* [Explore scenarios with sandboxes](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=wibv-explore-scenarios-sandboxes)

Sandboxes let you try out different changes to the data before making those changes public to other users and before committing those changes to the base data. Sandboxes are visible only to you.
* [Snap commands](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=wibv-snap-commands)

Snap commands are simple commands that you can use to perform tasks quickly.
* [Collaborate with chat in Planning Analytics with Watson](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=views-collaborate-chat-in-planning-analytics-workspace-classic)

You can use the chat feature to collaborate with other Planning Analytics with Watson users. Chat conversations are associated with and accessed from an individual book.
* [Access your data and other objects quickly](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=wibv-access-your-data-other-objects-quickly)

You can quickly access your data and other objects in Planning Analytics with Watson. You can add a view, a visualization, or objects to a collection to reuse them in a book. You can access recently used objects in the navigation tree. You can bookmark items in the navigation tree for later retrieval.
* [Export to Excel](https://www.ibm.com/docs/planning-analytics/2.0.0?topic=wibv-export-excel)

You can export a cube view as a Microsoft Excel spreadsheet.
During the beta release, Knowledge Graph functionality and the methods associated with it are only available for service instances that are subscribed to Advanced plans, Premium plans, and all Dedicated environments. The new features are: entity similarity, evidence, and canonicalization and filtering : Update: As of 30 September 2019, the IBM Watson™ Discovery Knowledge Graph Beta APIs are no longer accessible. See the [3 September 2019 release notes](https://cloud.ibm.com/docs/discovery?topic=discovery-release-notesdiscovery-3september2019) for more information.





 7 March 2018 

Fixed known issue with ingestion : The following ingestion known issue is fixed: Between 28 February and 6 March, a small percentage of documents were indexed with only the id and extracted_metadata fields (other document content was not indexed). The underlying problem is fixed; however, you must resubmit any affected documents for ingestion. There is no simple way to identify the affected documents.





 5 March 2018 

Fixed Knowledge Graph known issue : The following IBM Watson™ Discovery Knowledge Graph known issue is fixed with the 2018-03-05 API version update. This fix only applies to newly created collections that use the 2018-03-05 version update.

Fixed names defect in ingestion : All entity type names and relation type names were previously converted to uppercase during ingestion. For example, the entity "GeoPoliticalEntity" was converted to "GEOPOLITICALENTITY," and the relation "partOf" was converted to "PARTOF." This is no longer the case.





 1 March 2018 

Improved query limits for Advanced and Premium plans : [Query expansion](https://cloud.ibm.com/docs/discovery?topic=discovery-query-conceptsquery-expansion) limits are increased for Advanced and Premium plans to 5,000 query expansions and 25,000 total terms. See [Discovery pricing plans](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans) for details.





 28 February 2018 

Deprecated AlchemyLanguage enrichments : AlchemyLanguage enrichments are deprecated, effective 1 March 2018.





 23 February 2018
! ! !

<-- </ol> -->

<-- </ul> --><-- </section "id="section-24jan2020ki-fixed" "> --><-- </section "id="section-24jan2020ki" "> --><-- <section "id="section-29nov2019ki" "> --> 2.1.0, 27 November 2019 <-- <ul> --> * When you apply an enrichment to a collection, the enrichment language must match the collection language, or it will fail. The tooling displays all the collections, regardless of language. * On the Manage Fields tab, you can edit system-generated fields. The following fields should not be edited by changing the field type or turning off indexing: document_id, extracted_metadata, metadata. * When you delete a Collection and select the option Don't delete underlying data, any incomplete document ingestion crawls will continue running in the background, which will impact the new crawl start times, until the existing crawls are completed. IBM Cloud Pak for Data

Discovery can fail to start up correctly due to components getting into a lock state. Manual database intervention may be needed to clear the lock. For more information on identifying and resolving this issue, see Clearing a lock state]] ] ] ] .
* If you upload a document with the Upload Data function, delete that document, and then try to upload either the same document or another document with the same document ID,the upload will fail and the message Error during creating a document will be displayed. * Documents that produce an html field when processed can not be used with relevancy training. html is produced for documents processed with Smart Document Understanding or Content Intelligence. The html field must be removed before relevancy training can complete successfully. * If the Part of Speech enrichment is not turned on: Dynamic facets will not be created, Dictionary suggestions cannot be used, Content Miner "extracted facets" will not generate. * [Update: fixed in version 2.1.1 Discovery for Content Intelligence and Table Understanding enrichments are configured out of the box to be applied on a field named html.
Update : Pricing plans [Update](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans)

Environments : You can create only one environment per service instance to upload your own data. : Discovery is located in a single availability zone (US South). : Dedicated and Premium plans are not available at the current time.





 Environment sizing 

Update : Pricing plans [Update](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans)

Environment sizing : You can choose an environment size only when creating a new environment. The ability to resize an environment is not currently available to users. : Choosing an environment size with more RAM increases performance. : There are currently no prescriptive sizing recommendations available for specific use cases. : Custom sizing for IBM Watson™ Knowledge Studio models is not self-serve. Contact your IBM® representative for more information.





 Ingestion limitations 

Update : Pricing plans [Update](https://cloud.ibm.com/docs/discovery?topic=discovery-discovery-pricing-plans)

Ingestion limitations : The ingestion rate is currently limited to 100 concurrent document ingestion operations. An application that submits documents to the service for ingestion needs to respect HTTP 429 errors and throttle down ingestion requests accordingly. : AlchemyLanguage enrichments are limited to the first 50 kB per field. : Enrichments from IBM Watson™ Knowledge Studio custom models are not limited, but split documents into 10-kB chunks. No relationships are annotated across chunk boundaries.





 Query limitations 

Update : Query concepts [Update](https://cloud.ibm.com/docs/discovery?topic=discovery-query-concepts)

Query limitations : Excessive query load can cause the search-index process to restart automatically. : Applications that issue queries must enforce reasonable limits on the number of concurrent queries.







 Known issues
For more information about using toolchains and tool integrations with the API, see [Creating a toolchain with the API](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-toolchains_getting_started&interface=apicreating_a_toolchain_api), [Deleting a toolchain with the API](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-toolchains-using&interface=apideleting_a_toolchain_api), [Working with tool integrations](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-integrations&interface=api), and the [CD Toolchain API docs](https://cloud.ibm.com/apidocs/toolchain).
* Can I use the console, APIs, or CLI to modify resources that are managed by Terraform?

When you use Terraform to manage resources such as Continuous Delivery service instances, toolchains, and Tekton pipelines, avoid changing the resources by using the console, APIs, or CLI, or by any other method outside of Terraform's control.

If you circumvent Terraform by directly changing resources, you might cause [resource drift](https://developer.hashicorp.com/terraform/tutorials/state/resource-drift), a situation in which the states of your actual resources on IBM Cloud deviate from the definition of the resources in Terraform. The next time that you apply the Terraform configuration, Terraform attempts to update your resources to align them with the Terraform configuration. This action might lead to unintended consequences, such as reverting changes or deleting and then re-creating resources.

For more information about resource drift, see [Manage Resource Drift](https://developer.hashicorp.com/terraform/tutorials/state/resource-drift).
* My Continuous Delivery service states that Lite plan services are deleted after 30 days of inactivity. What does inactivity mean?
: Planning Analytics Workspace within Planning Analytics as a Service has been updated to version 2.0.85.
: For more information on new and changed features in Planning Analytics Workspace 2.0.85, see [What's new in Planning Analytics Workspace](https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=wnipaw-2085-whats-new-march-22-2023). To see which issues were fixed in this Planning Analytics Workspace update, review the [Planning Analytics Workspace 2.0.85 fix list](https://www.ibm.com/support/pages/system/files/inline-files/ibm_fixlist_planning_analytics_workspace_2085_sc.pdf).





 28 February 2023 

Planning Analytics Workspace update
: Planning Analytics Workspace within Planning Analytics as a Service has been updated to version 2.0.84.
: For more information on new and changed features in Planning Analytics Workspace 2.0.84, see [What's new in Planning Analytics Workspace](https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=wnipaw-2084-whats-new-february-16-2023). To see which issues were fixed in this Planning Analytics Workspace update, review the [Planning Analytics Workspace 2.0.84 fix list](https://www.ibm.com/support/pages/system/files/inline-files/ibm_fixlist_planning_analytics_workspace_2084_sc.pdf).

Planning Analytics Spreadsheet Services update
: Planning Analytics Spreadsheet Services/TM1 Web within Planning Analytics as a Service has been updated to version 2.0.83.
: For more information on new and changed features in Planning Analytics Spreadsheet Services/TM1 Web, see [What's new in Planning Analytics Spreadsheet Services](https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=web-2083-feature-updates-february-17-2023).
Select Machine Learning Model > Versions.
2. Click Export current model.

If you have a Lite plan subscription, no export option is available.

The model is saved as a ZIP file, and you are prompted to download the file.
3. Download the file to your local system.
4. From the Discovery service, follow the steps to create a Machine Learning enrichment, which include uploading the ZIP file. For more details, see [Machine Learning models](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-domainmachinelearning) in the Discovery v2 documentation.



If you're using a Discovery v1 service instance, you must provide the model ID when it is requested during the Discovery service enrichment configuration process. For more information, see [Integrating your custom model with the Discovery tooling](https://cloud.ibm.com/docs/discovery?topic=discovery-integrating-with-wksintegrate-customtooling) in the Discovery v1 documentation.







 Deploying a machine learning model to IBM Watson Natural Language Understanding 

When you are satisfied with the performance of the model, you can deploy a version of it to IBM Watson Natural Language Understanding. This feature enables your applications to use the deployed machine learning model to analyze semantic features of text input, including entities and relations.



 Before you begin 

You must have a Natural Language Understanding service to deploy to. And you must know the IBM Cloud space and instance names that are associated with the service. If you do not remember the space or instance names, find them by logging in to IBM Cloud. If you do not have an IBM Cloud account, sign up for one.





 About this task 

When you deploy the machine learning model, you select the version of it that you want to deploy.





 Procedure 

To deploy a machine learning model to the Natural Language Understanding service, complete the following steps:



1. Log in as a Knowledge Studio administrator or project manager, and select your workspace.
2. Select Machine Learning Model > Versions.
3. Choose the version of the model that you want to deploy.
For more information, see the [End of Service announcement](https://cloud.ibm.com/docs/dns?topic=dns-resellone-eos).
* What are the benefits of migrating to Hover?

 What are the benefits of migrating to Hover? 

As a Hover customer, you’ll benefit from a clean and intuitive domain management control panel. You'll also get an expanded selection of premium top-level domains, and great customer support.
* What are the benefits of migrating to OpenSRS?

 What are the benefits of migrating to OpenSRS? 

As a direct OpenSRS reseller, you’ll be able to fully manage your domains with greater ease. You'll get a greater selection of premium top-level domains and be able to offer your customers an expanded selection to automate your domain management experience. Post migration, you’ll benefit from improved availability of your business-critical domain services and additional features, including:



* Brandable end-user communications
* Scalability
* Exceptional reliability
* Flexible integration



* What service agreement do I follow after migration to Hover?

 What service agreement do I follow after migration to Hover? 

After migration, you are automatically transitioned to Tucows’ retail domains brand Hover's [Terms Of Service](https://www.hover.com/tos).
* What service agreement do I follow after migration to a Tucows OpenSRS Reseller account?

 What service agreement do I follow after migration to a Tucows OpenSRS Reseller account? 

After migration, you are automatically transitioned to the OpenSRS/Tucows’ Inc. Master Services Agreement. You can find this from the [OpenSRS website](https://opensrs.com/wp-content/uploads/Master_Services_Agreement.html).

Additional resources can be found in [OpenSRS Documentation](https://opensrs.com/resources/documentation/).
* If I have more questions, who can I contact?

 If I have more questions, who can I contact?
Should I go ahead? Your pizza is on its way! see *Complex response* 



Complex response Because users might include affirmative or negative statements at other times during the dialog (Oh yes, we want the pizza delivered at 5pm) or (no guests tonight, let's make it a small), use the slot_in_focus property to make it clear in the slot condition that you are looking for a Yes or No response to the prompt for this slot only.

(yes || no) && slot_in_focus

The slot_in_focus property always evaluates to a Boolean (true or false) value. Only include it in a condition for which you want a boolean result. Do not use it in slot conditions that checks for an entity type and then save the entity value, for example.

In the Not found prompt, clarify that you are expecting the user to provide a Yes or No answer.

{
"output":{
"text": {
"values": [
"Respond with Yes to indicate that you want the order to
be placed as-is, or No to indicate that you do not."
]
}
}
}

In the Found prompt, add a condition that checks for a No response (#no). When found, ask for the information all over again and reset the context variables that you saved earlier.

{
"conditions": "no",
"output":{
"text": {
"values": [
"Let's try this again. Tell me what size pizza
you want and the time..."
]
}
},
"context":{
"size": null,
"time": null,
"confirmation": null
}
}
Show more





 Replacing a slot context variable value 

If, at any time before the user exits a node with slots, the user provides a new value for a slot, then the new value is saved in the slot context variable, replacing the previously-specified value. Your dialog can acknowledge explicitly that this replacement has occurred by using special properties that are defined for the Found condition:
[Plus or higher plans only](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/plus.png) For environments where private endpoints are in use, keep in mind that the preview sends traffic over the internet. For more information, see [Private network endpoints](https://cloud.ibm.com/docs/assistant?topic=assistant-securitysecurity-private-endpoints).
3. In the "Assistant preview" pane, submit test utterances to see how the assistant responds.

If the Connect to agent response is displayed, it means you do not have a conversational skill added to your assistant. You must add one before you can chat with the assistant.
4. You can click the Restart conversation button to start a conversation over.

This action is useful if you want to test different routes through a single conversational flow. Or if you set or change context variable values in a dialog skill and want to see how specifying different values affects the conversation.

The conversation is restarted after the assistant's inactivity period elapses. The inactivity period can range from 5 minutes to 7 days depending on what you configure for your service plan type. After the intactivity time frame passes, any context variable values that were set during the conversation are set to null or back to their default values. For more information, see [Changing the inactivity timeout setting](https://cloud.ibm.com/docs/assistant?topic=assistant-assistant-settingsassistant-settings-change-timeout).
5. To test the assistant from a separate web page, copy and paste the Share this link URL into a web browser.

A simple IBM-branded web page is displayed that contains a chat window where you can interact with your assistant. You can share the page with others by sending them the Share this link URL. If necessary, you can click the toggle on the Preview page to disable the link.
How can I access infrastructure services in my account? 

You can't view all infrastructure sections of the console because of an account configuration issue.

  What’s happening 

When you attempt to access infrastructure sections of the IBM Cloud console, the following message might be displayed:

> This page can't be loaded because your infrastructure account is not fully configured as an IBM Cloud account.

  Why it’s happening 

There are multiple reasons why the message is displayed:



*  You have a [Lite account](https://cloud.ibm.com/docs/account?topic=account-accountsliteaccount), which does not allow access to infrastructure services.
*  Your account is not linked to an infrastructure account.



  How to fix it 

To resolve this issue, you must upgrade to a Pay-As-You-Go or Subscription account. For more information, see [Upgrading your account](https://cloud.ibm.com/docs/account?topic=account-upgrading-account).
Activity Tracker offers ready to run event search offerings that you can use to expedite your time to greater insights. You can choose to retain your events for 7, 14, or 30 days. In addition, a 30 day HIPAA compliant offering is also available. For more information about these offerings, see [Service plans](https://cloud.ibm.com/docs/atracker?topic=atracker-service_plan).

Use Activity Tracker hosted event search offerings to manage events using a UI or to manage auditing events that are not routed by Activity Tracker Event Routing.



* What are the different options to collect and monitor auditing events in my account?

To collect and monitor activity in your account, you must configure the Activity Tracker Event Routing service in your account by using any of the following methods:



* You can [configure Activity Tracker Event Routing](https://cloud.ibm.com/docs/atracker?topic=atracker-getting-started-routing-2) to manage auditing events in your account while maintaining Financial Services Validated status.

The target resource must be an IBM Cloud® Object Storage bucket that is available in the same account where the auditing events are generated.

You can also use a bucket that is available in a different account from where auditing events are generated.

You must follow and comply with the Financial Services Validated requirements for buckets to maintain Financial Services Validated status.
* You can [configure the Activity Tracker Event Routing hosted event search offering](https://cloud.ibm.com/docs/atracker?topic=atracker-getting-started-search) to manage auditing events through the UI, or if you need PCI, SOC2, Privacy Shield or HIPAA compliance.
* You can configure Activity Tracker Event Routing to define the Activity Tracker Event Routing hosted event search instances where auditing events are routed.

The Activity Tracker Event Routing hosted event search instances can be located in the same account where auditing events are generated or in a different account.



* Where can I find the list of Cloud services that generate Activity Tracker Event Routing events?
* Journeys currently do not meet accessibility requirements.
* Journeys are not supported if you are using the [element configuration option](https://web-chat.global.assistant.watson.cloud.ibm.com/docs.html?to=api-configurationoptionselement) to render the web chat in a custom DOM element.
* When the customer starts a journey, the web chat window temporarily closes, but will reopen when the journey finishes. If you are using the window:close event to trigger the display of a post-chat form, your code should check the value of the new event.reason parameter of the event and verify that it is not set to open_tour.