Application Functionality Sample Clauses

POPULAR SAMPLE Copied 4 times
Application Functionality. 9 1. Encryption; 10 a. Application is required to use encryption to protect sensitive data in both storage and 11 transit wherever technically possible 12 b. All encryption methods will be for storage and transit of data need to be defined by the 13 CONTRACTOR. 14 c. All data transmissions must be encrypted using a FIPS 140-2 certified algorithm, such 15 as Advanced Encryption Standard (AES), with a 128bit key or higher. Encryption can be end to end at 16 the network level. This requirement pertains to any regulated data in motion such as website access and 17 file transfers. 18 2. Network Communication: CONTRACTOR will provide information related to standards 19 and requirements for the deployment of the application including methods of secure implementation and 20 port requirements 21 3. Access Management; 22 a. Application/system controls access to and within the system at multiple levels (e.g. per 23 user, per user role, per area, per section of the chart) through a consistent mechanism of identification 24 and authentication of all users in accordance with the ‘Role Based Access Control’ (RBAC) standard. 25 b. Application will support measures to define, attach, modify and remove access rights 26 for all classes of users. 27 c. CONTRACTOR will work toward meeting the evolving standards for authentication as 28 they become available 29 d. Application will have the ability to create unique user accounts and passwords. 30 e. The application will disable or lock accounts after 90 days of inactivity or a date range 31 approved by COUNTY. 32 f. CONTRACTOR hosted solution will support client side certificates to restrict access to 33 known pc’s only. 34 4. Password Management; 35 a. Application will support password management measures including but not limited to 36 password expiration, account lockout and complex passwords. 37 // 1 b. CONTRACTOR will enforce strong passwords on all accounts that gain access to 2 County data. 3 c. Application will support session inactivity timeouts.
View SourceView Similar (3)
Application Functionality. Any modification of API Content/Services must comply with our Commercial Accounts API Specifications documents. Under no circumstances can you revise, change, modify or alter API Content/Services (or its appearance) to render the API Content/Services unfair, deceptive, abusive, false or misleading. If the API Content/Services includes hyperlinks to our website, the Application must use the complete, unaltered URL as the HREF or comparable functional link for proper tracking and functionality. Promptly upon request, you agree to provide us reasonable access to your Application, documents, information, employees, subcontractors, and your third party agents. You will diligently and promptly correct any material bugs or faults in your Application that cause it to incorrectly access the API or display API Content/Services.
View Source
Application Functionality. If you are using the UCA API as the UCA Interface, then, prior to launching a Licensee Application, you must submit all UCA-Related Pages to Licensor for review for compliance with Licensor’s requirements, including any required disclosures and legends, and, thereafter, you agree to not modify any UCA-Related Pages without Licensor’s prior written approval. Your Licensee Application may enhance the display of the UCA Content to best format the UCA Content. Any other modification of UCA Content must comply with the UCA Content License. If the UCA Content includes hyperlinks to a Licensor or Participating Program website, the Licensee Application must use the complete, unaltered URL as the HREF or comparable functional link given to the end user for proper tracking and functionality. Promptly upon request, you agree to provide Licensor reasonable access to any UCA-Related Pages for review of compliance with this Agreement and its requirements. You will diligently correct any material bugs or faults in your Licensee Application that cause it to incorrectly access the UCA API or display UCA Content. In addition, you will not, through your actions or omissions, cause the UCA API to fail to accurately deliver information, and you will be fully responsible for, and indemnify, defend and hold harmless the Licensor Indemnified Persons from, any Losses arising out of or relating to any failure of the UCA API to accurately deliver information as a result of your actions or omissions. Regardless of how you use the UCA API and UCA Content in your Licensee Application, you may not at any time, during and after the term of this Agreement, prevent or restrict Licensor from any use, functionality, or display of the UCA API or UCA Content in any manner, for any purpose, with any end user, in any application, or in any medium, now known or later developed.
View Source
Application Functionality. Any modification of API Content/Services must comply with the API Governing Documents. Under no circumstances can you revise, change, modify or alter API Content/Services (or its appearance) to render the API Content/Services unfair, deceptive, abusive, false or misleading. If the API Content/Services includes hyperlinks to Our website, the Application must use the complete, unaltered URL as the HREF or comparable functional link for proper tracking and functionality. Promptly upon request, you agree to provide Us reasonable access to your Application, documents, information, employees, subcontractors, and your third party agents. You will diligently and promptly correct any material bugs or faults in your Application that cause it to incorrectly access the API or display API Content/Services. Regardless of how you use the API and API Content/Services in your Application, you may not at any time, surviving termination of this Service Agreement to the maximum extent permitted by law, prevent or restrict Us from any use, functionality, or display of Our API or API Content/Services in any manner, for any purpose, with any user or End User, in any application, or in any medium, now known or later developed.
View Source
Application Functionality. 1.4.1. System shall support profiles for subcontract laboratories, each with lab-specific pricing per analysis. 1.4.2. System shall support cost tracking including, but not limited to: 1.4.2.1. Verify correct invoice totals based on the analyses performed, quantities and the lab; 1.4.2.2. Cost tracking is linked to specific sampling, events, programs, Entry Sets and lab report numbers; 1.4.2.3. Costs able to be tracked either in software or connected through ODBC to other business intelligence applications (e.g., R, Tableau, Power BI, etc.).
View Source
Application Functionality. Any modification of API Products must comply with the Governing Documents. Promptly upon request, you agree to provide us reasonable access to your Application, documents, information, employees, subcontractors, and your third-party agents. You will diligently and promptly correct any material bugs or faults in your Application that cause it to incorrectly access the API or display API Products. Regardless of how you use the API and API Products in your Application, you may not at any time, surviving termination of this Service Agreement to the maximum extent permitted by law, prevent or restrict us from any use, functionality, or display of our API and API Products in any manner, for any purpose, in any application, or in any medium, now known or later developed.
View Source
Application Functionality. The Application is designed to assist you to obtain information about Enercare’s product offers, services and information concerning energy cost savings and conservation measures, and to schedule and manage service appointments (the “Services”).
View Source

Related to Application Functionality

  • 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 February 1, 2017, the Division 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 Division to provide equally effective alternative access. The Plan for New Content will require the Division, 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, alternatives 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 Division 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 Division will officially adopt and fully implement the amended policies and procedures.

  • 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.

  • Mobile Application If Red Hat offers products and services through applications available on your wireless or other mobile Device (such as a mobile phone) (the "Mobile Application Services"), these Mobile Application Services are governed by the applicable additional terms governing such Mobile Application Service. Red Hat does not charge for these Mobile Application Services unless otherwise provided in the applicable additional terms. However, your wireless carrier's standard messaging rates and other messaging, data and other rates and charges will apply to certain Mobile Application Services. You should check with your carrier to find out what plans your carrier offers and how much the plans cost. In addition, the use or availability of certain Mobile Application Services may be prohibited or restricted by your wireless carrier, and not all Mobile Application Services may work with all wireless carriers or Devices. Therefore, you should check with your wireless carrier to find out if the Mobile Application Services are available for your wireless Device, and what restrictions, if any, may be applicable to your use of such Mobile Application Services.

  • 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.