vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Converts the object or field to the Double number type. You can call this method on any object or field. If the conversion fails, null is returned.





 toInt() 

Converts the object or field to the Integer number type. You can call this method on any object or field. If the conversion fails, null is returned.





 toLong() 

Converts the object or field to the Long number type. You can call this method on any object or field. If the conversion fails, null is returned.

To specify a Long number type in a SpEL expression, you must append an L to the number to identify it as such (for example, 5000000000L). This syntax is required for any numbers that do not fit into the 32-bit Integer type. Numbers that are greater than 2^31 (2,147,483,648) or lower than -2^31 (-2,147,483,648) are considered Long number types. Long number types have a minimum value of -2^63 and a maximum value of 2^63-1 (or 9,223,372,036,854,775,807).





 Standard math 

Use SpEL expressions to define standard math equations, where the operators are represented by using these symbols:



 Arithmetic operation Symbol 

 addition + 
 division / 
 multiplication * 
 subtraction - 







 java.lang.Math() 

You can use the functions of the java.lang.Math class to perform basic numeric operations.

You can use the the Class methods, including these:



* max():

T(Math).max(${step_297},${step_569})
* min():

T(Math).min(${step_297},${step_569})
* pow():

T(Math).pow(${step_297}.toDouble(),2.toDouble())
Instances (total) The number of active instances and the number of completed job and build instances cannot exceed 2500. 
 Jobs You are limited to 100 jobs per project. 
 Job runs You are limited to 100 job runs per project before you need to remove or clean up old ones. 
 Memory The total combination for all the app instances, running job instances, and running build instances cannot exceed 512 G of memory. 
 Secrets You are limited to 100 secrets per project. 
 Subscriptions (IBM Cloud Object Storage) You are limited to 100 (Object Storage) subscriptions per project. 
 Subscriptions (Kafka / IBM® Event Streams for IBM Cloud®) You are limited to 100 Kafka subscriptions per project. 
 Subscriptions (Periodic timer (cron)) You are limited to 100 periodic timer (cron) subscriptions per project. 



For example, you are limited to 128 vCPU or 250 active instances of an app or job. Since each limit applies independent of other limits, suppose you want to scale an app to 250 instances with 0.125 VCPU. These values result in about 32 vCPU, which works as this result is less than the maximum of 128 vCPU. However, you cannot use 512 instances with 0.125 vCPU, which would still meet the maximum of 128 vCPU, but would violate the limit for a maximum of 250 instances.





 Periodic timer (cron) subscription limits 

Code Engine limits the size of data for Periodic timer (cron) events with a maximum of 4096 bytes. When you create or update periodic timer (cron) events, Code Engine checks the size of the cron event data. If the Periodic timer (cron) event data exceeds the limit, a size limit exceeded error is given. If you receive this error, try reducing the cron event data size to less than 4096 bytes.

For more information about troubleshooting subscriptions, see [Debugging subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-subscriptions).





 Increasing limits
Debugging jobs 

Use the troubleshooting tips to learn how to troubleshoot IBM Cloud® Code Engine jobs and runs of your job.



 Job limits to consider 

The maximum number of jobs that you can have per project is 100. You are limited to a total of 100 job runs per project before you need to remove or clean up old ones.

For more information about limits for jobs including memory and CPU, see [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits).





 Getting logs for my jobs 

Logs can be helpful to troubleshoot problems when you run jobs. You can view job logs from the console or with the CLI.

When you view logs from the console, you must create an IBM Log Analysis instance in the same region as your Code Engine project. You are not required to create this instance before you work with your Code Engine job. Code Engine makes it easy to enable logging for your jobs. You can view job logs after you add logging capabilities. For more information, see [viewing job logs from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-joblogs-ui).

When working with the CLI, you can display logs of all the instances of your running job or display logs of a specific instance of your job.



1. Use the [ibmcloud ce jobrun list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-list) command to list all your defined job runs; for example,

ibmcloud ce jobrun list
2. Use the [ibmcloud ce jobrun get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-get) command to get the details of your job run, including the name of the instances for the job run; for example,

ibmcloud ce jobrun get --name myjobrun

Example output

Getting jobrun 'myjobrun'...
* The meals served
* The fact that the restaurant bakes cakes to order



For general, low-hanging fruit types of questions, a single, general answer is suitable.







 Step 4: Manage cake orders 

Customers place orders in person, over the phone, or by using the order form on the website. After the order is placed, users can cancel the order through the virtual assistant. First, define an entity that can recognize order numbers. Then, add an intent that recognizes when users want to cancel a cake order.



 Adding an order number pattern entity 

You want the assistant to recognize order numbers, so you will create a pattern entity to recognize the unique format that the restaurant uses to identify its orders. The syntax of order numbers used by the restaurant's bakery is two uppercase letters followed by 5 numbers. For example, YR34663. Add an entity that can recognize this character pattern.



1. Click the Entities tab.
2. Click Create entity.
3. Enter order_number into the entity name field.
4. Click Create entity.

![Shows the field for adding values for the @order_number entity.](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/gs-ass-entity-add-values.png)
5. Add order_syntax to the Value name field, and then click the down arrow next to Synonyms to change the type to Patterns.

![Shows the user choosing to add a pattern for the entity.](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/gs-ass-add-pattern.png)
6. Add the following regular expression to the Pattern field: [A-Z]{2}d{5}

!
You agree to release, defend, indemnify and hold harmless IBM Cloud and its contractors, agents, employees, officers, directors, shareholders and affiliates from and against any losses, damages or costs, including reasonable attorney's fees, resulting from any claim, action, proceeding suit or demand arising out of or related to Your (including Your agents, affiliates or anyone using Your account with IBM Cloud whether or not on Your behalf, and whether or not with Your permission) use of the services provided by IBM Cloud. Should IBM Cloud be notified of a pending lawsuit, or receive notice of the filing of a lawsuit, IBM Cloud may seek a written confirmation from You concerning Your obligation to indemnify IBM Cloud. Your failure to provide such a confirmation may be considered a breach of this Agreement.





 Representations and Warranties 

You warrant that all information provided by You as part of the registration process is complete and accurate. You also warrant that each registration You make is being done in good faith and that You have no knowledge of it infringing upon or conflicting with the legal rights of a third party or a third party's registration, trademark or trade name. You also warrant that the domain name being registered will not be used in connection with any illegal activity.

You agree that IBM Cloud makes no representations or warranties of any kind in connection with this Agreement and specifically makes no guaranty to You against the possibility of objection to, or challenge of, the registration or use of any domain name You register with IBM Cloud.

IBM Cloud expressly reserves the right to deny, cancel or transfer any registration that it deems necessary, in its discretion, to protect the integrity and stability of the registry, to comply with any applicable laws, government rules or requirements, requests of law enforcement, in compliance with any dispute resolution process, or to avoid any liability, civil or criminal, on the part of IBM Cloud, as well as its affiliates, subsidiaries, officers, directors and employees. IBM Cloud also reserves the right to freeze a domain name during resolution of a dispute.





 Disclaimer of Warranties 

IBM Cloud expressly disclaims all warranties of any kind, whether express or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose and non-infringement.
Use the Prometheus remote-write capabilities to push the metrics from the Windows system by running Prometheus as a client collector on Windows.



To see the step by step installation and configuration refer to [Monitoring a Windows environment](https://cloud.ibm.com/docs/monitoring?topic=monitoring-windows).





 Log analysis 

The IBM Log Analysis service enables the management of event logs from resources in IBM Cloud. IBM Log Analysis offers features to filter, search, define alerts, and design custom views to monitor logs. Refer to [Overview](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-getting-startedgetting-started_ov) for an overview of the service. Log Analysis does not natively support Windows logging. Therefore, an alternative centralized logging service will need to be used.





 Backup 

Backup and restore on SQL Server can be categorized as either native or third party integration:



* Native - For more information, see [Quickstart: Backup and restore a SQL Server database](https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/quickstart-backup-restore-database?view=sql-server-ver15) which describes the process of creating a full database backup and restoring a backup using SQL Server Management Studio (SSMS). The backup is stored in the backup location configured during the SQL Server install or a user defined location, such as a file share. Backups can be scheduled by using a SQL Server Agent job. For a full description of SQL Server concepts, see [Backup Overview (SQL Server)](https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/backup-overview-sql-server?view=sql-server-ver15).
* Third party integration - There are a number of third party integrations available and here we describe just three; IBM Spectrum Protect, Veeam and IBM Spectrum Protect Plus:



* IBM Spectrum Protect - Data Protection for SQL allows you to perform online backups and restores of Microsoft SQL Server databases to an IBM Spectrum Protect Storage Manager Server.
Identity and Access Management (IAM) IBM Cloud Internet Services authenticates requests and determines authorization for all user actions based on platform and service access roles and policies in IAM. To learn more, see [Managing access for CIS](https://cloud.ibm.com/docs/cis?topic=cis-iam-and-cisiam-and-cis). 
 Object Storage (COS) Used to store edge logs for a customer's data path traffic. YOu can also use this service to store operational logs of IBM Cloud Internet Services itself. 







 Other dependencies 



Table 2. Other dependencies

 Service name Description 

 Certificate Manager Used to store the TLS certificates for IBM Cloud Internet Services. 
 IBM Cloud Container Registry Used to store the images that IBM Cloud Internet Services uses to run the service. 
 IBM Cloud Monitoring IBM Cloud Internet Services sends service metrics to IBM Cloud Monitoring. The service team uses these metrics to identify capacity and performance issues of the service and monitor the operational health of the service. 









 Dependencies to third-party services 

Review the list of third-party services that IBM Cloud Kubernetes Service connects to over the public network.



 Critical dependencies 



Table 3. Critical third party dependencies

 Service name Description 

 Cloudflare Cloudflare is the third party provider for all data path services that are offered by IBM Cloud Internet Services, such as WAF, DDoS protection, and global load balancing. 







 Other dependencies 



Table 4. Other third party dependencies

 Service name Description 

 PagerDuty PagerDuty is used to notify on-call support of emergency and non-emergency issues that are related to operating IBM Cloud Internet Services or its support.
This category does not extend to specifications of a party's obligations or rights regarding any purchased goods, services, licenses, and so on, as those goods are the party's own assets, rather than assets of another party. 
 Assignments Elements that describe the transfer of rights, obligations, or both to a third party. 
 Audits Elements referring to either the right of a party to examine or review compliance, or requirements that a party be available for inspection or compliance review. This category includes references to record keeping (primarily as it relates to the right of inspection) and the maintenance and retention of activity records that may be examined. 
 Business Continuity Elements referring to the consequences if the entire business of one of the parties is sold. 
 Communication Elements referring to requirements to communicate, respond, notify, or provide notice; contact information; or information regarding changes to the contract. Also includes references to details about communication methods, the act or process of exchanging information, and acceptable means of exchanging information between parties (and others who are not necessarily direct parties to the contract). 
 Confidentiality Elements describing how parties can or cannot use information that is learned in the course of completing the contract and going forward. Also includes discussion of information that must be kept confidential, such as maintaining trade secrets or nondisclosure of business information. 
 Deliverables Elements specifying the items, such as goods or services, that one party provides to another under the terms of the contract, usually in exchange for payment. Includes discussion of preparation of deliverables. 
 Delivery Elements that specify the means or modes of transferring deliverables (things, as opposed to personal services) from one party to another. Includes discussions of characteristics of delivery, such as scheduling or location. 
 Dispute Resolution Elements discussing provisions for settling any dispute (for example, regarding labor, invoices, or billing) arising between contracting parties. Provision examples may include settlement by a defined procedure such as an arbitration panel, a process for obtaining an injunction, waiving a right to trial, or prohibiting the pursuit of a class action. Also includes references to the contract's governing law or choice of law, such as a particular country or jurisdiction. 
 Force Majeure Elements that refer to unexpected or disruptive events outside a party's control that would relieve the party from performing their contractual obligation.
This specifically applies to one party having access to or using assets such as licenses, equipment, tools, or personnel of the other party while in the process of conducting their duties under the agreement, including permissions and restrictions thereon. This does not extend to specifications of a party's obligations or rights regarding any purchased goods, services, licenses, etc., as those are the party's own assets, rather than assets of another party. 
 Assignments Elements that describe the transfer of rights, obligations, or both to a third party. 
 Audits Elements referring to either the right of a party to examine or review compliance, or requirements that a party be available for inspection or compliance review. This includes references to record keeping, primarily as it relates to the right of inspection, and the maintenance and retention of activity records that might be examined. 
 Business Continuity Elements referring to the consequences if part of or the entire business of one of the parties is sold. 
 Communication Elements referring to requirements to communicate, respond, notify, or provide notice; contact information; or information regarding changes to the contract. Also includes references to details about communication methods, the act or process of exchanging information, and acceptable means of exchanging information between parties (as well as others who are not necessarily direct parties to the contract). 
 Confidentiality Elements describing how parties can or cannot use information that is learned in the course of completing the contract and going forward. Also includes discussion of information that must be kept confidential, such as maintaining trade secrets or nondisclosure of business information. 
 Deliverables Elements specifying the items, such as goods or services, that one party provides to another under the terms of the contract, usually in exchange for payment. Includes discussion of preparation of deliverables. 
 Delivery Elements that specify the means or modes of transferring deliverables (things, as opposed to personal services) from one party to another. Includes discussions of characteristics of delivery, such as scheduling or location. 
 Dispute Resolution Elements discussing provisions for settling any dispute (for example, regarding labor, invoices, or billing) arising between contracting parties. Provision examples might include settlement by a defined procedure such as an arbitration panel, a process for obtaining an injunction, waiving a right to trial, or prohibiting the pursuit of a class action.
SA-9 - External Information System Services 



 Control requirements 

The organization:

SA-9 (a)
: Requires that providers of external information system services comply with organizational information security requirements and employ [IBM Assignment: business continuity service level agreements] in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance;

SA-9 (b)
: Defines and documents government oversight and user roles and responsibilities with regard to external information system services; and

SA-9 (c)
: Employs [IBM Assignment: Continuous monitoring requirements must be met for external systems where customer information is processed or stored] to monitor security control compliance by external service providers on an ongoing basis.





 Additional IBM Cloud for Financial Services specifications 



* Requirements for contingency planning and business continuity must be negotiated with third party service providers.
* Degradation of performance by the same external vendor to the organization across different regions should be documented.
* Authorized individuals include Federal Regulators in the event of insolvency.







 Implementation guidance 

See the resources that follow to learn more about how to implement this control.



* [IBM Cloud account setup](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-setup)







 IBM Cloud for Financial Services profile 

The rules related to this control that follow are part of the IBM Cloud for Financial Services v1.2.0 profile in [IBM Cloud® Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-getting-started).



Rules for SA-9 in IBM Cloud for Financial Services v1.2.0 profile

 Requirement ID Rules 

 SA-9 (a) <br><br> * Check whether provisioned services are IAM enabled<br> * Check whether the Financial Services Validated setting is enabled in account settings<br><br><br> 







 NIST supplemental guidance 

External information system services are services that are implemented outside of the authorization boundaries of organizational information systems. This includes services that are used by, but not a part of, organizational information systems.
Morally objectionable activities include, but are not limited to: activities designed to defame, embarrass, harm, abuse, threaten, slander or harass third parties; activities prohibited by the laws of the United States and/or foreign territories in which You conduct business; activities designed to encourage unlawful behavior by others, such as hate crimes, terrorism and child pornography; activities that are tortious, vulgar, obscene, invasive of the privacy of a third party, racially, ethnically, or otherwise objectionable; activities designed to impersonate the identity of a third party; and activities designed to harm minors in any way. In the event IBM Cloud refuses a registration or deletes an existing registration during the first thirty (30) days after registration, You will receive a refund of any fees paid to IBM Cloud in connection with the registration either being canceled or refused, unless the deletion was the result of the domain name being used in association with spam or morally objectionable activities, in which case, no refund will be issued.







 Suspension of Services; Breach of Agreement 

You agree that Your ability to use the Services is subject to cancellation or suspension if there is an unresolved breach of this Agreement and/or suspension or cancellation is required by any policy now in effect or adopted later by ICANN.

You agree that Your failure to comply completely with the terms and conditions of this Agreement and any IBM Cloud rule or policy may be considered a material breach of this Agreement. In the event that You do not provide IBM Cloud with material evidence refuting such breach within ten (10) business days after receiving notice of the breach, IBM Cloud may terminate its relationship with You and take any remedial action available to IBM Cloud under applicable laws, including canceling the registration of any of Your domain names and discontinuing any services provided to You. No fees will be refunded to You should Your agreement be cancelled or services be discontinued because of a breach. IBM Cloud's failure to act upon or notify You of any event, which may constitute a breach, shall not relieve You from or excuse You of the fact that You have committed a breach.





 Dispute Resolution Policy 

You agree to be bound by our current Dispute Resolution Policy, which is incorporated herein and made a part of this Agreement. You can view the Uniform Domain Name Dispute Resolution Policy online.