Beta Functionality Sample Clauses

Beta Functionality eGain may offer, and Customer may choose, to accept access to functionality that is not generally available and not validated and quality assured in accordance with eGain’s standard processes (“Beta Functionality”). Beta Functionality is described as such in the Documentation for Cloud Services. eGain may require Customer to accept additional terms to use Beta Functionality. Any production use of the Beta Functionality is at Customer’s sole risk. eGain does not warrant the correctness and completeness of the Beta Functionality, and eGain shall not be liable for errors or damages caused by the usage of the Beta Functionality.
AutoNDA by SimpleDocs
Beta Functionality. Coral grants to AirTouch the right of first refusal to test new applicable Coral Enhancements as such are ready for beta installation. Coral shall provide AirTouch with a minimum of 45 days prior written notice of the estimated date an applicable Coral Enhancement shall be available for beta installation and testing. AirTouch shall have 15 days within which to notify Coral of its desire to test the same in a beta installation in a mutually agreed upon AirTouch market. Upon receipt of the foregoing notice from AirTouch, the parties shall work together to install and test the beta version of the Coral Enhancement. SECTION TEN OBLIGATIONS OF AIRTOUCH
Beta Functionality. Customer may only use Beta Functionality for non-productive testing and evaluation. SAP may require Customer to accept additional terms to use Beta Functionality. SAP does not warrant or guarantee the correctness and completeness of the Beta Functionality, and Customer will use Beta Functionality at its own risk. SAP may discontinue providing Beta Functionality at any time and SAP makes no commitment that Beta Functionality will be generally available for productive use. Service level agreements and support obligations do not apply to Beta Functionality. No personal data may be processed using Beta Functionality.
Beta Functionality. Renaissant may designate certain functionality of the Platform as “Beta Functionality.” Customer acknowledges and agrees that Beta Functionality will be experimental and will not have been fully tested, and will not be appropriate for production use. Customer’s use of Beta Functionality will be (a) solely for purposes of evaluating and testing the new functionality and providing feedback to Renaissant; and (b) subject to all terms and conditions herein relating to the Platform. NOTWITHSTANDING ANY OTHER PROVISION OF THIS AGREEMENT, BETA FUNCTIONALITY IS PROVIDED “AS-IS” AND “AS-AVAILABLE,” WITHOUT WARRANTIES OF ANY KIND. Customer waives any and all claims, now known or later discovered, that Customer may have against Renaissant and its vendors and licensors arising out of Customer’s use of the Beta Functionality.

Related to Beta Functionality

  • Future Functionality You agree that Your purchases are not contingent on the delivery of any future functionality or features, or dependent on any oral or written public comments made by Us regarding future functionality or features.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • MIXED FUNCTIONS An employee engaged for more than two hours during one day or shift on duties carrying a higher rate than his or her ordinary classification shall be paid the higher rate for such day or shift. If for two hours or less during one day or shift he or she shall be paid the higher rate for the time so worked.

  • CUSTOMER SERVICE FUNCTIONS The Servicer shall handle all Customer inquiries and other Customer service matters according to the same procedures it uses to service Customers with respect to its own charges.

  • Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.

  • MANAGEMENT FUNCTIONS B.1 The Association recognizes that the management of the Hospital and the direction of working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement and, without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to: (a) maintain order, discipline and efficiency; (b) hire, assign, retire, discharge, direct, promote, demote, classify, transfer, lay- off, recall, and suspend or otherwise discipline nurses, provided that a claim of discharge or discipline without just cause may be the subject of a grievance and dealt with as hereinafter provided; (c) determine, in the interest of efficient operation and high standards of service, job rating and classification, the hours of work, work assignments, methods of doing the work, and the working establishment for the service; (d) generally to manage the operation that the Hospital is engaged in and, without restricting the generality of the foregoing, to determine the number of personnel required, methods, procedures, and equipment in connection therewith; (e) make, enforce, and alter from time to time reasonable rules and regulations to be observed by the nurses which are not inconsistent with the provisions of this Agreement. B.2 These rights shall not be exercised in a manner inconsistent with the provisions of this Agreement.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Telemedicine Services This plan covers clinically appropriate telemedicine services when the service is provided via remote access through an on-line service or other interactive audio and video telecommunications system in accordance with R.I. General Law § 27-81-1. Clinically appropriate telemedicine services may be obtained from a network or non- network provider, and from our designated telemedicine service provider. When you seek telemedicine services from our designated telemedicine service provider, the amount you pay is listed in the Summary of Medical Benefits. When you receive a covered healthcare service from a network or non-network provider via remote access, the amount you pay depends on the covered healthcare service you receive, as indicated in the Summary of Medical Benefits. For information about telemedicine services, our designated telemedicine service provider, and how to access telemedicine services, please visit our website or contact our Customer Service Department.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Customization The listed products are licensed for Customer Manager Suite use and customization only. Use of these tools to develop or customize non-Customer Manager Suite applications is not permitted without the express written authorization of PFPC.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!