vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Valid values for html are on, off.
* js: Automatically minify all JS for your website. Valid values for js are on, off.



* Valid values for mobile_redirect are status, mobile_subdomain, strip_uri. For example, -v status=on,mobile_subdomain=m,strip_uri=true



* status: Whether or not the mobile redirection is enabled. Valid values for status are on, off.
* mobile_subdomain: Which subdomain prefix you wish to redirect visitors on mobile devices to (subdomain must already exist).
* strip_uri: Whether to drop the current page path and redirect to the mobile subdomain URL root. Valid values for strip_uri are true, false.



* Valid values for opportunistic_encryption are on, off.
* Valid values for origin_error_page_pass_thru are on, off.
* Valid values for brotli are on, off.
* Valid values for prefetch_preload are on, off.
* Valid values for pseudo_ipv4 are off, add_header, overwrite_header.



* off: Disable Pseudo IPv4.
* add_header: Add additional Cf-Pseudo-IPv4 header only.
* overwrite_header: Overwrite the existing Cf-Connecting-IP and X-Forwarded-For headers with a pseudo IPv4 address.



* Valid values for response_buffering are on, off.
* Valid values for script_load_optimization are on, off.
* Valid values for security_header are enabled, max_age, include_subdomains, preload, nosniff. For example: -v enabled=true,max_age=100,include_subdomains=true,preload=true,nosniff=true



* enabled: Whether or not security_header is enabled.Valid values for enabled are true, false.
* max_age: Specify the duration(in seconds) security_header are cached in browsers.
{"ClientIP":"2620:1f7:8c5::1f:949e:c04d","ClientRequestHost":"test.logpull.load.com","ClientRequestMethod":"GET","ClientRequestURI":"/assets/bootstrap.css","EdgeEndTimestamp":1545067627952000000,"EdgeResponseBytes":17311,"EdgeResponseStatus":200,"EdgeStartTimestamp":1545067627948000000,"RayID":"48ab1942af85c7a7"}
{"ClientIP":"2620:1f7:8c5::1f:949e:c04d","ClientRequestHost":"test.logpull.load.com","ClientRequestMethod":"GET","ClientRequestURI":"/assets/jquery.js","EdgeEndTimestamp":1545067628045000000,"EdgeResponseBytes":33555,"EdgeResponseStatus":200,"EdgeStartTimestamp":1545067628042000000,"RayID":"48ab19434882c7a7"}
{"ClientIP":"2620:1f7:8c5::1f:949e:c04d","ClientRequestHost":"test.logpull.load.com","ClientRequestMethod":"GET","ClientRequestURI":"/assets/watson.gif","EdgeEndTimestamp":1545067628052000000,"EdgeResponseBytes":893230,"EdgeResponseStatus":200,"EdgeStartTimestamp":1545067628046000000,"RayID":"48ab194348a3c7a7"}
Getting started with IBM Cloud Internet Services 

IBM Cloud® Internet Services (CIS), powered with Cloudflare, offers three main capabilities to enhance your workflow: [security](https://cloud.ibm.com/docs/cis?topic=cis-manage-your-ibm-cis-for-optimal-security), [reliability](https://cloud.ibm.com/docs/cis?topic=cis-manage-your-ibm-cloud-internet-services-deployment-for-optimal-reliability), and [performance](https://cloud.ibm.com/docs/cis?topic=cis-manage-your-cis-deployment-for-best-performance). You can navigate to features for each of these capabilities after you open the CIS UI.

For each capability, CIS helps you tune its features to suit your specific needs. These features are detailed in the [About IBM Cloud Internet Services](https://cloud.ibm.com/docs/cis?topic=cis-about-ibm-cloud-internet-services-cis) section.



 Before you begin 

Before you begin using CIS:



* You'll need an [IBMid](https://www.ibm.com/account/reg/us-en/signup?formid=urx-19776).
* Then, you can order your services through the [IBM Cloud Internet Services console](https://cloud.ibm.com/catalog/services/internet-services).



It is recommended that you use the Chrome browser for CIS.





 Process overview 

You can start using CIS for your internet traffic with just a few steps.



1. Open the CIS application from your IBM Cloud dashboard.
2. Add the domain that you want to manage.
3. Set up your DNS records (optional).
4. Configure your DNS information with the name servers provided.
5. Continue getting started with CIS by following a tutorial, or by setting up other features.





 Step 1: Open the IBM CIS application 

Open the [IBM Cloud catalog](https://cloud.ibm.com/catalog). Then, select the Networking category in the navigation pane.
ImportOfferingOptions offeringOptions = new ImportOfferingOptions.Builder().catalogIdentifier(id).zipurl(offeringURL).build();
Response<Offering> response = service.importOffering(offeringOptions).execute();
System.out.println(response.getResult());

id = "{id}"
offeringURL = "{offeringURL}"
response = self.service.import_offering(catalog_identifier=id, zipurl=offeringURL)
print(response)

id := "{id}"
offeringURL := "{offeringURL}"
offeringOptions := service.NewImportOfferingOptions(id, offeringURL)
_, response, _ := service.ImportOffering(offeringOptions)
fmt.Println(response)

id = "{id}";
offeringURL = "{offeringURL}";
response = await service.importOffering({ 'catalogIdentifier': id, 'zipurl': offeringURL });
console.log(response);





 Validating your software by using the API 

You can programmatically validate your product to by calling the Catalog Management API as shown in the following sample request. This process can take several minutes. For detailed information about the API, see [Catalog Management API](https://cloud.ibm.com/apidocs/resource-catalog/private-catalog?code=javavalidate-install).



* Java
* Python
* Go
* Node



String authRefreshToken = "{authRefreshToken}";
String versionLocator = "{versionLocator}";
ValidationInstallOptions installOptions = new ValidationInstallOptions.Builder().xAuthRefreshToken(authRefreshToken).versionLocId(versionLocator).build();
Only one page-specific token can be present per error page, so if you want to customize every error, you must create one custom error page for each error containing the respective token.



Table 1. Page types and their tokens

 Page Type Token 

 All pages ::CLIENT_IP:: 
 All pages ::RAY_ID:: 
 Basic Security (CAPTCHA Challenge) ::CAPTCHA_BOX:: 
 WAF (CAPTCHA Challenge) ::CAPTCHA_BOX:: 
 Country Challenge (CAPTCHA Challenge) ::CAPTCHA_BOX:: 
 Defense Mode (Interstitial Page) ::IM_UNDER_ATTACK_BOX:: 
 5XX Errors ::CLOUDFLARE_ERROR_500S_BOX:: 
 1XXX Errors ::CLOUDFLARE_ERROR_1000S_BOX:: 
 Serve Stale Content ::ALWAYS_ONLINE_NO_COPY_BOX:: 







 Styling error codes 

Each tag has a unique class that you can use to style individual error codes. It is possible to use CSS to stylize the tags in the div/span/section since they all have class IDs.

Each page (challenge, 5xx errors) has a different ID, so use the preview option to get the proper ID.





 Publishing error pages 

After you're done customizing your error pages, it's time to publish them to our edge. This is done through the [Custom Page CLI](https://cloud.ibm.com/docs/cis?topic=cis-cli-plugin-cis-clicustom-page).

When you publish, the custom error page is requested once by us, then cached on the cloud's edge.





 Updating error pages 

You can update an error page by re-publishing it.

If CIS cannot load your site, or you have blocked the US in the CIS firewall, publishing and previewing the error page does not work.





 Troubleshooting error pages 



* If you encounter errors while attempting to preview or publish your custom error page, run it through a HTML validator and ensure that it is error free.
* Make sure that the minimum page size is greater than 0. You must add content to your page.
See the following example that uses HTTP to search within a range:

POST /my-movies/_find HTTP/1.1
Host: $SERVICE_URL
Content-Type: application/json
{
"selector": {
"Person_name":"Robert De Niro",
"Movie_year": {
"$in": [1974, 2009]
}
}
}

See the following example that uses the command line to search within a range:



* Curl
* Java
* Node
* Python
* Go



curl -X POST -H "Content-Type: application/json" 	"$SERVICE_URL/my-movies/_find" 	-d '{"selector": {"Person_name":"Robert De Niro", "Movie_year": { "$in": [1974, 2009]}}}'

import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.ExplainResult;
import com.ibm.cloud.cloudant.v1.model.PostExplainOptions;

import java.util.Arrays;
import java.util.Collections;
import java.util.HashMap;
import java.util.Map;

Cloudant service = Cloudant.newInstance();

Map<String, Object> selector = new HashMap<>();
selector.put("Person_name", "Robert De Niro");
selector.put("Movie_year",
Collections.singletonMap("$in", Arrays.asList(1978, 2009)));

PostExplainOptions explainOptions =
new PostExplainOptions.Builder()
.db("my-movies")
.selector(selector)
.build();

ExplainResult response =
service.postExplain(explainOptions).execute()
.getResult();

System.out.println(response);
The user starts by visiting the URL [https://cloud.ibm.com](https://cloud.ibm.com) with a browser. The IBM Cloud console sends back a login page to the browser.
2. On the login page, the user enters their username.
3. After clicking to continue, the IBM Cloud console redirects the user's browser to IBM Cloud's IAM component. As part of the redirect, the already entered username is transmitted.
4. With the help of the username, IAM is able to determine the identity provider (IdP) that should be used to run the login sequence. Therefore, IAM is sending back a redirect request to the user's browser.
5. The browser is completing the redirect and displays the enterprise customer's login page. For this interaction, a SAML request is sent to the enterprise customer's user authentication and authorization system.
6. After validating the user's credentials, the enterprise customer's system sends a redirect instruction to the user's browser. Part of this redirect is the SAML response containing assertions that describe the user and the additional attributes of that user.
7. The browser completes the redirect and sends the SAML response with assertions to IBMid.
8. IBMid validates the SAML response and maps the user to an IBMid.
9. IBMid sends a redirect to the user's browser with an authorization code to continue the authentication flow according to the OpenID Connect standard.
10. The browser contacts IAM and provides the authorization code, so that IAM can retrieve the required tokens from IBMid using the OpenID Connect standard.
11. After IBMid provides the required tokens, IAM is now finishing its authentication flow with the console by sending an OAuth2 compliant redirect with an authorization code to the browser.
12. The browser provides the authorization code to the console, which in turn is used to retrieve the required tokens from IAM.
13. When the console receives the tokens, the login sequence ends.
You can't provision a public instance or a dedicated instance that is auto-assigned to a host when you use an image under your own Windows license. Additionally, when you create or update a Windows image template under your own license, the Windows image can't be a cloud-init image.





 Before you begin 

First, go to the device menu and make sure that you have the correct account permissions to complete the tasks.



* Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/image-templates?topic=virtual-servers-navigating-devices).
* Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermissioninfrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





 Importing an image that designates your own license 

You can import a VHD image and specify that you are providing your own license or subscription for the operating system.

To access the Import Image page of Image Templates and mark a VHD image to use your own license or subscription, complete the following steps:



1. From the Devices menu, select Manage > Images.
2. Click the Import Image tab.
3. Complete the required information for importing your VHD image, and select the Your License checkbox that is shown near the Operating System dropdown box. For more information about importing images, see [Preparing and importing images](https://cloud.ibm.com/docs/image-templates?topic=image-templates-preparing-and-importing-imagespreparing-and-importing-images).







 Updating an image template to specify a user provided OS license
Why can't I use Support Center when I log in to the IBM Cloud by applying a trusted profile? 

You need to log in to the account without selecting a trusted profile.

  What’s happening 

You're unable to view, manage, and create Support Center cases when you log in to IBM Cloud by selecting a trusted profile.

  Why it’s happening 

The Support Center is not currently enabled for users that log in to IBM Cloud by selecting a trusted profile.

  How to fix it 

If you need to use the Support Center, log out and log back in without selecting a trusted profile. To do so, complete the following steps.



1.  Go to the Avatar icon ![Avatar icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/i-avatar-icon.svg) > Log out.
2.  To confirm, click Log out.
3.  Go to https://cloud.ibm.com/login to log in again.
4.  Enter your credentials and click Continue.
5.  On the trusted profiles landing page, click Continue without selecting a trusted profile.
From the assistant overview page, click the ![Overflow menu](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/kebab.png) icon, and then choose Settings.
2. Click Webhooks > Log webhook.
3. Do one of the following things:



* To change the webhook that you want to call, click Delete webhook to delete the currently specified URL and secret. You can then add a new URL and other details.
* To stop calling a webhook to log every message and response, click the Log webhook switch to disable the webhook altogether.









 Webhook security 

To authenticate the webhook request, verify the JSON Web Token (JWT) that is sent with the request. The webhook microservice automatically generates a JWT and sends it in the Authorization header with each webhook call. It is your responsibility to add code to the external service that verifies the JWT.

For example, if you specify purple unicorn in the Secret field, you might add code similar to this:

const jwt = require('jsonwebtoken');
...
const token = request.headers.authentication; // grab the "Authentication" header
try {
const decoded = jwt.verify(token, 'purple unicorn');
} catch(err) {
// error thrown if token is invalid
}





 Webhook request body 

The request body the webhook sends to the external service is a JSON object with the following structure:

{
"event": {
"name": "{event_type}"
},
"payload": {
...
}
}

where {event_type} is either message_logged (for messages and responses) or cdr_logged (for CDR events).
Viewer As a viewer, you can view service instances, but you can't modify them. 







 Cognitive View 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use 3p-cognitiveview-xaas-cognitiveview for the service name.

Platform roles

Actions



Table 3. Platform roles - Cognitive View
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 SimpleCloud 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use 3p-summusrender-xaas-simplecl0ud for the service name.

Platform roles

Actions



Table 4. Platform roles - SimpleCloud
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 
 Viewer As a viewer, you can view service instances, but you can't modify them.
Why can’t I see my Watson Studio projects that are used with a Watson service? 

You are unable to browse to a Watson Studio project that you want to use with another Watson service.

  What’s happening 

You want to add a service to a Watson Studio project or find an existing project that uses other Watson services, but you are unable to locate where to do so. You do not see the projects that you created.

  Why it’s happening 

Multiple entry points to Watson services exist. The name of the product might change from Watson Studio to Cloud Pak for Data after you add other services. For some offering plans, projects are specific to the IBM Cloud service region in which they were saved.

  How to fix it 

Log in to [https://dataplatform.cloud.ibm.com](https://dataplatform.cloud.ibm.com/). From that home page, you can view your Watson services, go to existing projects, create a project, and accomplish other tasks.



*  If you prefer to start from the [IBM Cloud console](https://cloud.ibm.com), click Watson Studio from your Resources list, and then click Get Started to go to the home page.
*  If your offering plan supports services in more than one region, [switch your region](https://dataplatform.cloud.ibm.com/docs/content/wsj/console/wdp_admin_console.htmlregion) to see the projects, catalogs, and data in different regions.
*  For more information about other factors that can affect your use of Watson Studio with other services, such as permissions and requirements, see the [FAQs](https://dataplatform.cloud.ibm.com/docs/content/wsj/getting-started/faq.html).
For example, access:dev, proj:version-1.
9. If you selected the Enterprise plan, then specify the Service endpoints. The following options are available:



* Public network - The public network service endpoints are accessible from anywhere on the internet.
* Both Public & Private network - use of both public and private service endpoint network access.



10. Accept the licensing agreements and terms by clicking the checkbox.
11. Click Create. A new service instance is created and the App Configuration console displayed.

Zoom

![App Configuration console](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-console.png)

Figure 2. App Configuration console
* Words containing special characters, such as hyphens (-), asterisks (*), ampersands (&), or at signs (@), including those used in email addresses or URLs.
* Words that belong, meaning words that have implied significance because they occur in your action steps or dialog entity values, entity synonyms, or intent user examples.





 How is spelling autocorrection related to fuzzy matching? 

In dialog, fuzzy matching helps your assistant recognize dictionary-based entity mentions in user input. It uses a dictionary lookup approach to match a word from the user input to an existing entity value or synonym in the skill's training data. For example, if the user enters boook, and your training data contains a @reading_material entity with a book value, then fuzzy matching recognizes that the two terms (boook and book) mean the same thing.

In dialog, when you enable both autocorrection and fuzzy matching, the fuzzy matching function runs before autocorrection is triggered. If it finds a term that it can match to an existing dictionary entity value or synonym, it adds the term to the list of words that belong to the skill, and does not correct it.

For example, if a user enters a sentence like I wnt to buy a boook, fuzzy matching recognizes that the term boook means the same thing as your entity value book, and adds it to the protected words list. Your assistant corrects the input to be, I want to buy a boook. Notice that it corrects wnt but does not correct the spelling of boook. If you see this type of result when you are testing your dialog, you might think your assistant is misbehaving. However, your assistant is not. Thanks to fuzzy matching, it correctly identifies boook as a @reading_material entity mention. And thanks to autocorrection revising the term to want, your assistant is able to map the input to your buy_something intent. Each feature does its part to help your assistant understand the meaning of the user input.
: Use the Trigger word detected action to add words or phrases to two separate groups. The first group connects customers with an agent, when it’s important for a customer to speak with a live agent rather than activate any further actions. The second group shows customers a customizable warning message, used to discourage customers from interacting with your assistant in unacceptable ways, such as using profanity. This action is included with all new assistants created as of this date. This is a beta feature that is available for evaluation and testing purposes. For more information, see [Detecting trigger words](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-trigger-phrases).

Changes to unrecognized requests algorithm
: In Analyze, the Recognition page lets you view groups of similar unrecognized requests. You can use the requests as example phrases in new or existing actions to address questions and issues that aren't being answered by your assistant. With this release, the criteria for grouping the requests is relaxed for customers with lesser amounts of data. Also, the group names have been improved with better grammar and to be more representative of the requests. For more information, see [Use unrecognized requests to get action recommendations](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-analytics-recognition).





 1 February 2023 

Actions templates updated with new design and new choices
: The actions template catalog has a new design that lets you select multiple templates at the same time. It also has new and updated templates, including starter kits you can use with external services such as Google and HubSpot. For more information, see [Building actions from a template](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-actions-templates).





 26 January 2023 

Display formats for variables
: In Global settings for actions, Display formats lets you specify the display formats for variables that use date, time, numbers, currency, or percentages. You can also choose a default locale to use if one isn't provided by the client application.