vania-janet/multiturn-rag-retrieval-data huggingface dataset:
List of Span array of objects with the form {"text":String, "location": {"begin": Integer, "end": Integer}} [{ "text":"Jane", "location": {"begin": 5, "end": 9} }, { "text":"...", "location": {"begin": 15, "end": 40} }] 
 Special case: empty List array with 0 elements [ ] 







 Advanced rules model limits 

The number of advanced rules models that you can define per service instance depends on your Discovery plan type.



Advanced rules model plan limits

 Plan Advanced rules models per service instance 

 Cloud Pak for Data Unlimited 
 Premium 3 
 Enterprise 3 
 Plus (includes Trial) 1
Why am I getting a charge limit error when I try to make a payment? 

You can't make a full payment on your invoice because of a charge limit.

  What’s happening 

You try to make a payment on an invoice that is over $1,000.00 USD, but you get the following error message:

> Manual payment request cannot be processed. Payment amount is higher than the limit allowed.

  Why it’s happening 

By default, credit card payments in US Dollars cannot exceed $1,000.00 USD, which might cause you to make multiple payments to pay your invoice.

  How to fix it 

You can contact [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter) to request an increase in this maximum credit card payment limit. All requests are considered based on the payment and invoice history of the account.
{"group": "group_0","location": 0, 12]},
{"group": "group_1","location": 0, 3]},
{"group": "group_2","location": 0, 3]},
{"group": "group_3"},
{"group": "group_4","location": 4, 7]},
{"group": "group_5","location": 8, 12]}
]

location is a property of an entity that uses a zero-based character offset to indicate where the detected entity value begins and ends in the input text.

If you expect two phone numbers to be supplied in the input, then you can check for two phone numbers. If present, use the following syntax to capture the area code of the second number, for example.



 Variable Value 

 second_areacode 



If the input is I want to change my phone number from 958-234-3456 to 555-456-5678, then $second_areacode equals 555.





 Viewing API call details 

As you test your dialog with the Try it out pane, you might want to know what the underlying API calls look like that are being returned from the service. You can use the developer tools provided by your web browser to inspect them.

From Chrome, for example, open the Developer tools. Click the Network tool. The Name section lists multiple API calls. Click the message call associated with your test utterance, and then click the Response column to see the API response body. It lists the intents and entities that were recognized in the user input with their confidence scores, and the values of context variables at the time of the call. To view the response body in structured format, click the Preview column.

![Shows how to view the API call details by using Chrome web browser developer tools.]
This property applies only when the metadata service is enabled by setting metadata_service.enabled to true. The default is false.



 Set the metadata hop limit when you provision an instance 

To set the response when you provision an instance, call the [POST /instances method](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance) method, and specify the metadata_service.response_hop_limit property value between 1 (default) and 64.

This property applies only when the metadata service is enabled by setting metadata_service.enabled to true. The default is false.





 Set the metadata hop limit on an existing instance 

To set the response hop limit on an existing instance, call the [PATCH /instances/{id}](https://cloud.ibm.com/apidocs/vpc/latestupdate-instance) method, and specify the metadata_service.response_hop_limit property value between 1 (default) and 64.









 Activity Tracker events for instance metadata 

Activity Tracker events are triggered when you get an [instance access identity token](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-configure-service&interface=uiimd-json-token) and then [use the service](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-get-metadata). For more information about these events, see [Instance Metadata service events](https://cloud.ibm.com/docs/vpc?topic=vpc-at-eventsevents-metadata).





 Next steps 

After you create an instance identity access token and enable the metadata service, you can retrieve metadata for the instance, SSH keys, and placement groups. For more information, see [Use the instance metadata service](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-get-metadata).
1. In the Genesys Cloud console, go to DID Numbers -> DID Ranges and create a new range. Specify the following information:



* In the DID Start and DID End fields, specify a phone number. (Once again, you do not need to use a real phone number; you can just make up an identifier for your Genesys environment, such as 1-888-888-1234.)



![Genesys create range](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/phone-genesys-create-range.png)



* In the Service Provider field, type a descriptive name (for example, Watson).



2. If you have not already set up a queue to enable callers to wait for available agents, follow these steps to create a simple one now:



1. Click Admin.
2. Under Contact Center, click Queues.
3. Create a new queue and give it a descriptive name.
4. Add yourself as a member.
5. Click Save.



3. Create a simple call flow. (Your business might already have something more complex for routing.)



1. Click Admin.
2. Click Architect.
3. In the Flows: Inbound Call section, click + to create a new flow. Give it a descriptive name (for example, Escalate to Agent).



![Genesys create flow](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/phone-genesys-flow.png)



1. In the toolbox, click Task and drag it into Reusable Tasks.



!
To add billing information, you must establish an account with a credit card processing service so your customers can pay with a credit card. Monthly billing Plans are billed on the same date of each month.
13. Optional: If you want to tailor which operations from an API are included in the Plan, hover the cursor over the API that contains the operation. Click the Show operations icon, and then select or clear the check boxes for the operations you want to include or exclude.
14. Optional: To add a rate limit to your Plan, clear the Unlimited check box and then specify the rate limit that you want to apply. If the Enforce hard limit check box is selected the Plan will stop applications from calling the API after reaching the rate limit, otherwise a warning will be presented.

Note: Applying a rate limit at the Plan level, creates a default rate limit that applies to each operation within the Plan. If you need to set specific rate limits for specific operations, you must set these within the operations themselves and this setting overrides the setting at the Plan level.
15. Optional: Specify whether your Plan requires subscription approval. If you want subscriptions by developers to require approval through the API Manager user interface, select Require subscription approval; otherwise, ensure that the check box is cleared.
16. Optional: Add a rate limit to an operation.



1. Hover the cursor over the API that contains the operation, click the Show operations icon.
2. Hover the cursor over the operation that you want to apply a rate limit to. Click the Edit rate limit icon.
3. Ensure the Unlimited check box is cleared, and then specify the rate limit that you want to apply. If the Enforce hard limit check box is selected the Plan will stop applications from calling the API after reaching the rate limit, otherwise a warning will be presented.







* Click the Save icon to save your changes.



You have created a Product, and specified a set of APIs and Plans into one offering that you can now make available to your developers. Next, stage your poduct to a catalog as explained in the next section, Staging a Product.





 Staging a Product 

Stage a Product to create a specific version of that Product in a Catalog, before publishing.
This property applies only when the metadata service is enabled by setting metadata_service.enabled to true. The default is false.



 Set the metadata hop limit when you provision an instance 

To set the response when you provision an instance, call the [POST /instances method](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance) method, and specify the metadata_service.response_hop_limit property value between 1 (default) and 64.

This property applies only when the metadata service is enabled by setting metadata_service.enabled to true. The default is false.





 Set the metadata hop limit on an existing instance 

To set the response hop limit on an existing instance, call the [PATCH /instances/{id}](https://cloud.ibm.com/apidocs/vpc/latestupdate-instance) method, and specify the metadata_service.response_hop_limit property value between 1 (default) and 64.









 Activity Tracker events for instance metadata 

Activity Tracker events are triggered when you get an [instance access identity token](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-configure-service&interface=apiimd-json-token) and then [use the service](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-get-metadata). For more information about these events, see [Instance Metadata service events](https://cloud.ibm.com/docs/vpc?topic=vpc-at-eventsevents-metadata).





 Next steps 

After you create an instance identity access token and enable the metadata service, you can retrieve metadata for the instance, SSH keys, and placement groups. For more information, see [Use the instance metadata service](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-get-metadata).
The label helps to differentiate zones with name collisions.
* How many private zones are supported?

DNS Services supports 10 private zones per service instance.
* How many permitted networks are supported?

DNS Services supports 10 permitted networks per DNS zone.
* How many DNS records are supported?

DNS Services supports 3500 DNS records per DNS zone.
* How do I delete my DNS Services instance?

To delete a DNS Services instance,



* Navigate to the Resource List in the [IBM Cloud console](https://%7BDomainName%7D/).
* Click the "overflow" menu ![overflow menu icon](https://cloud.ibm.com/icons/actions-icon-vertical.svg) in the final column and select "Delete".



* Why can't I delete a DNS Services instance?

If a DNS zone has been added to the DNS Services instance, the instance cannot be deleted.
* Why can't I delete a DNS zone?

If a network has been added to a zone, the zone cannot be deleted until the permitted network is deleted from the zone.
* What happens if I delete my VPC?

If the VPC is deleted, the corresponding permitted network will also be deleted from the DNS zones of your instance.
* Why can I still resolve my resource records after I deleted its associated zone or permitted network?

To maintain a level of performance while resolving DNS queries, DNS Services resolvers cache data related to permitted networks for a period of time. Changes made to a permitted network might not have propagated until the previously cached data expires. See [Known limitations](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-known-limitations) for more details.
* What do the different zone states mean?

The zone states definitions are as follows.



* Pending: When a DNS zone is added to the instance it will be in Pending. In this state Resource Records can be added, deleted or updated.
For example, you might build a step that executes only if all conditions in group 1 are true or any condition in group 2 is true. (Groups function like parentheses in the boolean conditions of many programming languages.)

After you add a group, you can define one or more conditions in the new group. Between groups, choose and or or to indicate whether the conditions in both conditional groups or only one of them must be met for the step to be included in the conversational flow.





 Operators 

An operator specifies the kind of test you are performing on a value in a condition. The specific operators available in a condition depend on the customer response type of the value, as shown in the following table.



Operators

 Response type Operators 

 <br><br> * Options<br><br><br> <br><br> * is<br> * is not<br> * is any of<br> * is none of<br><br><br> 
 <br><br> * Regex<br><br><br> <br><br> * is<br> * is not<br><br><br> 
 <br><br> * Number<br> * Currency<br> * Percent<br><br><br> <br><br> * is defined<br> * is not defined<br> * is equal to (==)<br> * is not equal to (≠)<br> * is less than (<)<br> * is less than or equal to (<=)<br> * is greater than (>)<br> * is greater than or equal to (>=)<br><br><br> 
 <br><br> * Date<br><br><br> <br><br> * is defined<br> * is not defined<br> * is on (also allows specific day of the week)<br> * is not on<br> * is before<br> * is after<br> * is on or before<br> * is on or after<br><br><br>
This property applies only when the metadata service is enabled by setting metadata_service.enabled to true. The default is false.



 Set the metadata hop limit when you provision an instance 

To set the response when you provision an instance, call the [POST /instances method](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance) method, and specify the metadata_service.response_hop_limit property value between 1 (default) and 64.

This property applies only when the metadata service is enabled by setting metadata_service.enabled to true. The default is false.





 Set the metadata hop limit on an existing instance 

To set the response hop limit on an existing instance, call the [PATCH /instances/{id}](https://cloud.ibm.com/apidocs/vpc/latestupdate-instance) method, and specify the metadata_service.response_hop_limit property value between 1 (default) and 64.









 Activity Tracker events for instance metadata 

Activity Tracker events are triggered when you get an [instance access identity token](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-configure-serviceimd-json-token) and then [use the service](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-get-metadata). For more information about these events, see [Instance Metadata service events](https://cloud.ibm.com/docs/vpc?topic=vpc-at-eventsevents-metadata).





 Next steps 

After you create an instance identity access token and enable the metadata service, you can retrieve metadata for the instance, SSH keys, and placement groups. For more information, see [Use the instance metadata service](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-get-metadata).
This property applies only when the metadata service is enabled by setting metadata_service.enabled to true. The default is false.



 Set the metadata hop limit when you provision an instance 

To set the response when you provision an instance, call the [POST /instances method](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance) method, and specify the metadata_service.response_hop_limit property value between 1 (default) and 64.

This property applies only when the metadata service is enabled by setting metadata_service.enabled to true. The default is false.





 Set the metadata hop limit on an existing instance 

To set the response hop limit on an existing instance, call the [PATCH /instances/{id}](https://cloud.ibm.com/apidocs/vpc/latestupdate-instance) method, and specify the metadata_service.response_hop_limit property value between 1 (default) and 64.









 Activity Tracker events for instance metadata 

Activity Tracker events are triggered when you get an [instance access identity token](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-configure-service&interface=cliimd-json-token) and then [use the service](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-get-metadata). For more information about these events, see [Instance Metadata service events](https://cloud.ibm.com/docs/vpc?topic=vpc-at-eventsevents-metadata).





 Next steps 

After you create an instance identity access token and enable the metadata service, you can retrieve metadata for the instance, SSH keys, and placement groups. For more information, see [Use the instance metadata service](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-get-metadata).
See [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits). When you create or update an application with Code Engine from the console, set the maximum number of instances value in the Autoscaling section of the Runtime tab. With the CLI, specify the --max-scale option on the app create and app update commands. The default value for this option is 10.



When you connect your applications to event producers, remember to account for the frequency and volume of the events from those producers when you set your scale boundaries. For example, if you expect to receive many events at the same time and the processing of each event can take several minutes, then you might need a higher maximum scale value than if each event can be quickly processed. If you set the value too low, you might experience delays in receiving events, or even dropped events due to timeouts while you wait for processing resources to be free.





 Autoscaling settings for concurrency and timing 

Use the following configuration settings to control application scaling.



* Concurrency - This value indicates how many requests each instance of your app can process at one time. For example, a currency value of 100 means that your code can handle 100 concurrent requests at the same time. This value is a "hard limit", meaning that Code Engine does not allow more than the number of requests (as specified with the concurrency setting) to reach any one instance of your application. Therefore, if your code is single threaded and can process only one request at a time, then consider setting concurrency to 1. When the specified number of requests are sent to all running instances of your application, Code Engine then increases the number of instances in preparation for more requests. When you create or update an application with Code Engine from the console, set the max concurrency value in the Autoscaling section of the Runtime tab. With the CLI, specify the --concurrency option on the app create and app update commands.
* Target concurrency - This value acts as a "soft limit" or number of requests per instance that you want in a loaded system. For example, if you specify concurrency as 100, and you specify target concurrency as 70, then Code Engine tries to limit the number of requests per instance to 70.
Response properties are output values that are set by the phone integration and provide information about the call. Request properties are input values that you can modify in your actions to send logging data or to change configuration options for the call.



 Response properties (set by the phone integration) 

Properties contained in the private object are treated as private variables, which are not included in logs.



Response properties of the voice_telephony object

 Name Type Description 

 sip_call_id String The SIP call ID associated with the phone call. 
 assistant_phone_number String The phone number associated with with the Watson Assistant end of the call. 
 sip_custom_invite_headers Object A user-defined array of key/value pairs containing SIP headers from the SIP INVITE request. 
 private.user_phone_number String The phone number from which the customer's call originated. 
 private.sip_request_uri String The inbound SIP request URI that initiated the phone call. 
 private.sip_from_uri String The URI from the From header of the SIP request. 
 private.sip_to_uri String The URI from the To header of the SIP request. 
 final_utterance_timeout_occurred Boolean Set to true when the final utterance timeout has been reached. This timeout can be configured by sending the final_utterance_timeout_count property. 
 post_response_timeout_occurred Boolean Set to true when the final utterance timeout has been reached. This timeout can be configured by sending the post_response_timeout_count property. 







 Example response JSON 

"voice_telephony": {
"private":{
"user_phone_number":"+18595553456",
"sip_request_uri":"sips:+18885557777@public.voip.us-east.assistant.watson.cloud.ibm.com",
"sip_from_uri":"sips:+18565558576@twilio.com",
For more information about creating facets, see [Adding facets](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-facetsfacetexist).



 Regular expression limits 

The number of regular expressions that you can define per service instance depends on your Discovery plan type.



Regular expression plan details

 Plan Regular expressions per service instance 

 Cloud Pak for Data Unlimited 
 Premium 100 
 Enterprise 100 
 Plus (includes Trial) 20
`@sys-number == 0` Please specify a number that is larger than 0. Clear slot and prompt again 
 `(event.previous_value != null) && (event.previous_value != event.current_value)` Ok, updating the number of guests from ` ` to ` `. Move on 
 `true` Ok. The reservation is for $guests guests. Move on 









 Step 5: Add a confirmation slot 

You might want to design your dialog to call an external reservation system and actually book a reservation for the user in the system. Before your application takes this action, you probably want to confirm with the user that the dialog has understood the details of the reservation correctly. You can do so by adding a confirmation slot to the node.



1. The confirmation slot will expect a Yes or No answer from the user. You must teach the dialog to be able to recognize a Yes or No intent in the user input first.
2. Click the Intents tab to return to the Intents page. Add the following intents and example utterances.





* yes

Yes
Sure
I'd like that
Please do
Yes please.
Ok
That sounds good.

![Shows the yes intent](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/slots-yes-intent.png)
* no

No
No thanks.
Please don't.
Please do not!
That's not what I want at all
Absolutely not.
No way

![Shows the no intent](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/slots-no-intent.png)





1. Return to the Dialog tab, and then click to edit the node with slots.
$ curl -X GET "https://<region>.kms.cloud.ibm.com/api/v2/keys/registrations?offset=<offset>&limit=<limit>" -H "accept: application/vnd.ibm.collection+json" -H "authorization: Bearer <IAM_token>" -H "bluemix-instance: <instance_ID>"

Replace the limit and offset variables in your request according to the following table.



Table 8. Describes the limit and offset variables.

 Variable Description 

 offset The number of registrations to skip. <br> <br>For example, if you have 50 registrations in your instance, and you want to list registrations 26 - 50, use ../registrations?offset=25. <br> <br>You can also pair offset with limit to page through your available resources. 
 limit The number of registrations to retrieve. <br> <br>For example, if you have 100 registrations in your instance, and you want to list only 10 registrations, use ../registrations?limit=10. The maximum value for limit is 5000. <br> <br>You can also pair offset with limit to page through your available resources. 









 CRN query examples 

Use URL encoded CRN queries to filter registrations by Key Protect instance, resource type, or resource name. To learn more about CRN segments and format, see [Cloud Resource Names](https://cloud.ibm.com/docs/account?topic=account-crn).

Cloud Services that use Key Protect to associate keys with resources on your behalf can only view or query for CRNs that match the first 8 segments of their service CRN.



* To search for the existence of a registration up to a specific CRN segment, use a colon followed by an asterisk ().

crn:v1:bluemix:public:databases-for-redis:us-south:a/
274074dce64e9c423ffc238516c755e1:29caf0e7-120f-4da8-9551-3abf57ebcfc7::