vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can also use the IBM Cloud Activity Tracker service to [audit events for a project](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-at_events). 







 Change management 

Change management includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion.



Table 2. Responsibilites for change management
The first column describes the task that the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities 

 Updates, fixes, and new features IBM provides regular updates and bug fixes, as well as new features following a continuous delivery model in a manner transparent to the customer. N/A 
 Creating and deploying configurations IBM provides the ability for customers to create and deploy configurations by using projects. Use projects to [configure and deploy a deployable architecture](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-config-project). 
 Deleting a project IBM provides the ability for customers to delete a project. Customers can [delete a project](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-delete-project) whenever they need to. 
 Pulling deployable architecture changes into a project IBM provides the ability for customers to update the version of a deployable architecture in a project, should a new version become available.
20 January 2023 

Deprecated Arabic and United Kingdom model names are no longer available
: The following Arabic and United Kingdom model names are no longer accepted by the service:



* ar-AR_BroadbandModel - Use ar-MS_BroadbandModel instead.
* en-UK_NarrowbandModel - Use en-GB_NarrowbandModel instead.
* en-UK_BroadbandModel - Use en-GB_BroadbandModel instead.



The Arabic model name was deprecated on 2 December 2020. The UK English model names were deprecated on 14 July 2017.

Cloud Foundry deprecation and migration to resource groups
: IBM announced the deprecation of IBM Cloud Foundry on 31 May 2022. As of 30 November 2022, new IBM Cloud Foundry applications cannot be created and only existing users are able to deploy applications. IBM Cloud Foundry reaches end of support on 1 June 2023. At that time, any IBM Cloud Foundry application runtime instances running IBM Cloud Foundry applications will be permanently disabled, deprovisioned, and deleted. For more information about the deprecation, see [Deprecation of IBM Cloud Foundry](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecation).

To continue to use your IBM Cloud applications beyond 1 June 2023, you must migrate to resource groups before that date. Resource groups are conceptually similar to Cloud Foundry spaces. They include several extra benefits, such as finer-grained access control by using IBM Cloud Identity and Access Management (IAM), the ability to connect service instances to apps and service across different regions, and an easy way to view usage per group. For more information about migration, see [Migrating Cloud Foundry service instances and apps to a resource group](https://cloud.ibm.com/docs/account?topic=account-migrate).

The max_alternatives parameter is now available for use with next-generation models
: The max_alternatives parameter is now available for use with all next-generation models. The parameter is generally available for all next-generation models.
When you select the Destination Type as any one of the push notification services (FCM, APNs, Chrome, Firefox, and Safari), you can select a Pre-production destination for developing and testing your environments at a low cost.





 Step 3: Add the destination 

Click Add.





 Upgrading a Pre-production destination to Production destination 

You can upgrade a Pre-production destination to Production destination after creating the destination by using the Edit option from the overflow menu.

To understand the billing impact of upgrading a Pre-production destination to Production destination, see [here](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destinations-pushen-destinations-push-charge-preprod-to-prod).

To modify the destination,



* Select the pre-production destination from the list of destinations
* Click the three vertical dots in the selected pre-production destination to access the overflow menu
* Click Edit, which brings the editable view of the selected destination.
* Click the Production destination tile to change the destination.
* Click Add.



You cannot change a Production destination to Pre-production destination.
[Edit icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/edit-tagging.svg) for the field you want to update.
4. Click Save.

You can revert to the published state of your support information by clicking Revert changes.
5. Click Request approval when you're ready with your updates. The approval can take at least five business days.
6. After your request is reviewed and approved by the IBM Cloud team, publish your changes by clicking Publish approved changes.

Any changes that you don't publish are deleted after 60 days.



You can toggle between the updated and the published state of your support information. Toggle the switch on to review your updates, and toggle the switch off for the published state.
* Anticipate and address the case when the user changes the number of guests.

If, at any point while the node with slots is being processed, the user changes a slot value, the corresponding slot context variable value is updated. However, it can be useful to let the user know that the value is being replaced, both to give clear feedback to the user and to give the user a chance to rectify it if the change was not what she intended.



12. From the edit view of the node with slots, click the Edit slot![Edit slot](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/edit-slot.png) icon for the @sys-number slot.
13. From the Options![More icon](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/kebab.png) menu in the Configure slot 3 header, select Enable conditional responses.
14. In the Found section, add a conditional response by clicking the ![Edit response](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/edit-slot.png) icon, and then add the following condition and response:



Slot 3 conditional response details

 Condition Response Action 

 `@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
Dates that are marked with a dagger (†) are tentative and subject to change.



Release timeline for IBM Cloud Kubernetes Service version 1.24

 Version Supported? IBM Cloud Kubernetes Service <br>release date IBM Cloud Kubernetes Service <br>unsupported date 

 1.24 Yes 09 Jun 2022 06 Sept 2023 † 







 Preparing to update 

This information summarizes updates that are likely to have and impact on deployed apps when you update a cluster to version 1.24. For a complete list of changes, review the [community Kubernetes change log](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.24.md) and [IBM version change log](https://cloud.ibm.com/docs/containers?topic=containers-changelog_124) for version 1.24. You can also review the [Kubernetes helpful warnings](https://kubernetes.io/blog/2020/09/03/warnings/).



 Update before master 

[Pod security policies](https://kubernetes.io/docs/concepts/security/pod-security-policy/) are scheduled for removal in Kubernetes version 1.25. See the Kubernetes [Deprecated API migration guide](https://kubernetes.io/docs/reference/using-api/deprecation-guide/psp-v125) for more information. Customers will have the option to replace Pod Security Policies with [Pod security admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/) or a [third party admission webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/). IBM Cloud Kubernetes Service will make a beta version of Pod Security available in version 1.24 to aid in the migration, but this support is not yet available.

The following table shows the actions that you must take before you update the Kubernetes master.
"creationDate": "2020-03-10T20:41:27Z",
"createdBy": "...",
"algorithmType": "Deprecated",
"algorithmMetadata": {
"bitLength": "128",
"mode": "Deprecated"
},
"algorithmBitSize": 128,
"algorithmMode": "Deprecated",
"lastUpdateDate": "2020-03-16T20:41:27Z",
"keyVersion": {
"id": "30372f20-d9f1-40b3-b486-a709e1932c9c",
"creationDate": "2020-03-12T03:37:32Z"
},
"dualAuthDelete": {
"enabled": false
},
"deleted": false
}
]
}

The integer mapping for the Active key state is 1.
"updated_at": "0001-01-01T00:00:00Z",
"system_state": {
"status_code": "draft"
},
"agent_kpi": {
"availability_indicator": "normal",
"lifecycle_indicator": "consistent",
"percent_usage_indicator": "30%"
}
}





 Next steps 



* You can see [update an agent](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-agents-update), and [delete an agent](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-agent-overview&interface=cli)
* You can check out the [agent FAQ](https://cloud.ibm.com/docs/schematics?topic=schematics-faqs-agent) for any common questions related to deleting an agent.
This is due to the way that the migration is being conducted. You are only billed through one. When the migration is complete, the global instance will be removed from your account.





 2 May 2023 

Schedule the frequency of your scans
: You can now schedule the frequency at which your scans are run in the updated architecture. Options include everyday, every 7 days, and every 30 days. You can also now pause your scans. It is recommended that you continue to scan your environments daily. To get started, see [Scanning IBM Cloud resources](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-scan-resources).





 1 May 2023 

Support for context-based restrictions (CBR)
: Manage user and service access to your Security and Compliance Center resources by using context-based restrictions, based on defined criteria. For more information, see [Protecting Security and Compliance Center resources with context-based restrictions](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-cbr).





 25 April 2023 

Filter results by tag
: You can now filter your results by specific tags. For more information about viewing and filtering results, see [Viewing results in the dashboard](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-results).





 24 April 2023 

Now available: Toronto location
: Toronto is now available as a location for processing your data. To learn more about how data is processed in Security and Compliance Center, see [Storing and encrypting](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-mng-data).





 20 April 2023 

Updates to the IBM Cloud for Financial Services profile
: Version 1.2.0 of the IBM Cloud for Financial Services profile are now available. For more information, see the [Change log](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-fs-change-log).





 17 April 2023 

Updates to the IBM Cloud Security Best Practices library and profile
However, you are encouraged to upgrade to the new "Preferred" version of the database as deprecated versions are eventually removed from IBM Cloud and are no longer provisionable, restorable, or supported.

Untagged - Untagged database versions are fully supported and deployable versions. They are usually slightly older than the current preferred version, but they are still supported by the database project maintainers. They continue to be supported on Cloud Databases deployments until their deprecation is announced.





 Deprecation of Major Versions 

IBM Cloud Databases tries to support a major version of a database for 3 years from its release.

If a database version is deprecated or marked end of life by the open source project owners, IBM Cloud Databases takes steps to deprecate that version.

When a major version is deprecated, a six-month transition window is opened for current users of the deprecated version.

At the beginning of the period, we seek to contact users affected by the deprecation. During the six-month transition window, users are able to initiate an upgrade to a supported major version. Existing deployments continue to run as normal.

Restoration of existing databases into new deployments of the deprecated major version is available during the six-month deprecation, although we recommend upgrading to a nondeprecated major version as soon as possible.

At the end of the transition window, deprecated major versions cannot be deployed on IBM Cloud Databases. A backup of the deployment is taken and access to databases that are running a deprecated version is removed or automatically upgraded to the next major version. See table 1 for which databases are upgraded or removed. Regardless, the backup is available to be restored into a new supported database version.

Failure to act can result in compatibility issues with your apps when IBM upgrades in-place. On rare occasions, failure can result, impacting your availability. If a failure occurs, the database is disabled, and you need to restore from backup. We recommend self-migrating before the end of support date.





 Major versions defined 



Table 1. Major versions for Cloud Databases

 Database Versioning Schema Next Known End of Life Version and Date End of life procedure 

 DataStax Major versions are the first number in a major.minor.patch version number.
: You can now specify the time zone for the date and time that is returned by the now() method. See [Now()](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-methodsdialog-methods-dates-now).





 24 October 2019 

Testing improvement
: You can now see the top three intents that were recognized in a test user input from the "Try it out" pane. For more details, see [Testing your dialog](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-tasksdialog-tasks-test).

Error message when opening an instance
: When you launch Watson Assistant from the IBM Cloud® dashboard, you might see an error message that says, Module 'ui-router' is not available! You either misspelled the module name or forgot to load it. You can ignore the message. Refresh the web browser page to close the notification.





 14 October 2019 

Deploy your assistant in minutes
: Create a web chat integration to embed your assistant into a page on your website as a chat widget. See [Integrating with your own website](https://cloud.ibm.com/docs/assistant?topic=assistant-deploy-web-chat).

UI changes
: The main menu options of Assistants and Skills have moved from being displayed in the page header to being shown as icons on the side of the page. The tabbed pages for the tools you use to develop a dialog skill were moved to a secondary navigation bar that is displayed when you open the skill.

Rich response types are supported in a dialog node with slots
: You can display a list of options for a user to choose from as the prompt for a slot, for example.

Change to switching service instances
: Where you go to switch service instances has changed. See [Switching the service instance](https://cloud.ibm.com/docs/assistant?topic=assistant-assistant-settingsassistant-settings-switch-instance).

Known issue: Cannot rename search skills
: You currently cannot rename a search skill after you create it.





 9 October 2019
* Expanding the types of resources that could be referenced by an href or embedded reference schema within the context of another resource.







 Changing default values 

Additionally, a default value for a property in a request MAY be changed if the new default has no increase in price or regressions in performance or supported features at the time of the change.

For example, the default pricing profile for a new resource may be changed if the new default is considered better in all respects and is an equal or lower price at the time of the change. (The profile that was previously default may be made less expensive at the same time, or after, but not before the change.)





 Resolving API definition errata 

If the implementation for an API is well-designed and functional, but the API definition differs from the implementation in an incompatible way, the definition SHOULD be updated to match the implementation, despite the resultant appearance of an incompatible change.







 Backward-incompatible changes 

A change that meaningfully alters the outcome or response format of any currently valid request MUST be considered backward-incompatible. Backward-incompatible changes SHOULD be supported in versioned updates.

The following kinds of changes SHOULD be considered backward-incompatible unless [a special case](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-change-compatibilityspecial-cases-for-backward-compatibility) applies:



* Removing or renaming an existing path
* Removing support for an existing method on an existing path
* Removing or renaming an existing query parameter
* Removing or renaming an existing property in a request or response schema
* Adding a new required query parameter, header, or property in a request schema
* Changing the status code for a particular scenario (except when the existing status code is 404)
* Reducing acceptable values for an existing query parameter, header, or property in a request schema
* Changing the semantics of a value for an existing query parameter, header, or property in a response schema
* Changing a default value or behavior for an already-valid request
* Redefining the nature of any relationship between resources





 Migrating to updated robustness best practices
For any billable services that you use beyond any free allowances, you receive a monthly invoice.

If you're upgrading to reactivate a deactivated account, your account might take a few days to be fully available. If your account continues to be in a pending state, see [Why can't I upgrade my account?](https://cloud.ibm.com/docs/account?topic=account-ts_upgrade_cc) for help.

If you can't upgrade your account because of an issue with your credit card, see [Troubleshooting credit card error messages](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-cc-error-messages) for more information.





 Promotional credit for upgrading your account 

After you sign up for a new Pay-As-You-Go account or upgrade your free account, you'll receive a promotional credit to use on any IBM product. To view the list of eligible products, go to the IBM Cloud console and select Catalog > Provider > IBM.

The credit might take a few hours to appear in your account. Any unused upgrade credit expires after the 30 day period ends. You are invoiced for any usage that exceeds the promotional credit. To view the promotional credit, go to the [Promotions and credits](https://cloud.ibm.com/billing/promotions) page or the [Invoices](https://cloud.ibm.com/billing/invoices) page in the console.

The following table lists the current upgrade promotional amounts for different currencies:



Table 1. Promo price for different currencies

 Country Currency Converted Promo Amount 

 United States USD 200.00 
 Australia AUD 279.94 
 Brazil BRL 862.84 
 Canada CAD 260.96 
 Switzerland CHF 190.85 
 China CNY 1,836.38 
 Denmark DKK 1,258.68 
 Euro EUR 168.67 
 UK GBP 151.96 
 Indonesia IDR 3,128,000.00 
 India INR 14,390.14 
 Japan JPY 22,400.62 
 South Korea KRW 232,999.57
1.39.5 06 October 2022 <br><br> * Fixed various bugs.<br><br><br> 
 1.39.3 15 September 2022 <br><br> * Fixed various bugs.<br> * Updated translations for the CLI.<br><br><br> 
 1.39.2 31 August 2022 <br><br> * Fixed various bugs.<br> * Upgraded to Go 1.19.0.<br><br><br> 
 1.39.1 18 August 2022 <br><br> * Updated the --maxexecutiontime option for the job create, job update, jobrun submit, and jobrun resubmit commands to change the maximum execution time from 43200 seconds (12 hours) to 86400 seconds (24 hours).<br> * Fixed various bugs.<br><br><br> 
 1.38.2 04 August 2022 <br><br> * Fixed various bugs.<br><br><br> 
 1.38.1 28 July 2022 <br><br> * Added support for increased default maximums for apps and jobs, and for additional memory and CPU combinations. See [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits) and [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo).<br> * Fixed various bugs.<br><br><br> 
 1.38.0 21 July 2022 <br><br> * Added support for the --binding-resource-group-id option on the project update command. Use this option to configure service binding access for all service instances in a resource group by specifying the ID of the resource group.<br> * Fixed various bugs.<br><br><br> 
 1.37.0 14 July 2022 <br><br> * Added support for running a Code Engine job indefinitely so that the job does not time out by specifying --mode daemon.
Deprecation of IBM Cloud Foundry 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).



 Overview 

IBM Cloud® is announcing the full deprecation of IBM Cloud Foundry on June 1, 2023. At that time, any IBM Cloud Foundry application runtime instances running IBM Cloud Foundry applications will be permanently disabled and deprovisioned. See the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details) for specific implications.

IBM Cloud® was started on Cloud Foundry, and has hosted many millions of gigabyte-hours of Cloud Foundry customer workloads over many years. At the time, Cloud Foundry brought the simplest ease-of-use and cloud PaaS deployment possible for our users. But as technology moves on, newer and more sophisticated technologies have become available for our IBM Cloud® users.

The following describes the details of the deprecation, possible migration targets for your applications, and additional information.





 Timeline 

The timeline for this deprecation is as follows:



Table 1. Deprecation timeline

 Stage Date Description 

 Announcement 31 May 2022 Announcement of the IBM Cloud Foundry deprecation. All current IBM Cloud Foundry users as of early June 2022, will receive an email with information about the deprecation. Notifications will be put into the IBM Cloud® console and related screens. 
 End-of-Marketing 30 November 2022 All IBM Cloud® users, other than those who have an IBM Cloud Foundry application deployed, will be blocked from new application deployments. As of 30 November 2022, new Cloud Foundry Organizations (Orgs) cannot be created by any user. 
 Reminders Ongoing Periodic reminders will be sent to all users with running IBM Cloud Foundry applications that the end-of-support date is coming, with increasing frequency as the date approaches.