Functionality and Features Clause Samples

The 'Functionality and Features' clause defines the specific capabilities, services, or attributes that a product, service, or software must provide under the agreement. It typically outlines the required functions, performance standards, and any unique features that distinguish the deliverable, such as compatibility with certain systems or inclusion of particular modules. This clause ensures both parties have a clear, mutual understanding of what is being delivered, reducing the risk of disputes over unmet expectations or ambiguous requirements.
Functionality and Features. Not all of the same functionality or features may be accessible or available at all times for all Services or Electronic Channels.
View SourceView Similar (5)
Functionality and Features. XRM Tokens uses, purpose, attributes, functionalities or features, express or implied are solely must be seen as a facilitating mechanism for building Aerum community and providing its members with a sample of delegated cross-chain proof of stake governance mechanism.
View Source
Functionality and Features. Not all of the same functionality or features may be accessible or available for all Accounts or other Services or Electronic Channels, or at all times. At the Customer’s request, Royal Bank will provide the Customer with more information about these limitations.
View Source
Functionality and Features. The Official CAS support is obsolete as Liferay is still using CAS Protocol 2 whereas neuGRID is using CAS Protocol version 3 and the ▇▇▇▇ assertions that are extensively used in the neuGRID SSO architecture to provide access to the users' attributes to the different neuGRID services. It required the development of a custom authentication handler based on the existing CAS integration, using the features provided by Liferay. It was updated to handle the CAS 3 protocol. This step required to create the class neuGRIDAutoLogin which implements com.liferay.portal.security.auth.AutoLogin. This class is responsible for extracting the user's attributes from the ▇▇▇▇ assertion that are returned by CAS once the user has been successfully authenticated. A Liferay user is created using these attributes if it does not already exist into the local Liferay database. The Distinguished Name (DN) of the user is normalized and used as the screen name. A Liferay hook was also developed in order to be able to customise the terms of use page. A new portal user has to accept these terms before being able to use the neuGRID portal. The former neuGRID portal developed using Ruby On Rails has been completely migrated to Liferay. The design has been migrated as a Liferay theme. The neuGRID menu has been ported into a portlet including the Grid load glowing brain that is updated using Ajax and the resource serving facility of the JSR 286. The portal is now ready to receive the neuGRID portlets.
View Source
Functionality and Features. The neuGRID pseudonymization Java library allows one to keep or remove a selected list of fields from DICOM images. The library is being implemented into the org.healthgrid.neuGRID.pseudonymize.Pseudonymization class providing the following public methods: The pseudonymization applet will allow users to select one or more local files and pseudonymize them in a manner configured for the neuGRID needs. It will take a list of images as input and will either output pseudonymized images into one chosen repository or send them to the neuGRID infrastructure according to the user's choice. The applet will also be handling the manual upload of files at the DACS level. Due to its applet nature when new features, bugs fixes or new pseudonymization rules are implemented, they will be immediately available for use. When running in standalone mode the applet will have an update facility allowing it to update itself and to apply automatically any possible new pseudonymization rules. In order to be able to create a nice and responsive applet that could live outside a browser, the JavaFX SDK has been used. JavaFX is a client platform developed by Sun allowing the creation of rich user interfaces for Internet applications. It is one of the main RIA (Rich Internet Application) frameworks. It allows reusing any existing Java library, and it is also capable of creating applets that could be deployed on a user's desktop just by dragging them from the browser.
View Source

Related to Functionality and 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.

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

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

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.