Required Fields Sample Clauses

Required Fields. There are required fields on the eCVI. They must remain required and be completed in order for the certificate to be issued and official.
AutoNDA by SimpleDocs
Required Fields. In the Enterprise Permitting & Licensing software, some fields are “Required Fields,” and the associated columns must be populated for records to be written to the Enterprise Permitting & Licensing db. On occasion, these required fields will not be available in the legacy source data, so a simple default value can be written to the EG_Template db to fulfill any NOT NULL constraint. Dropdown picklist columns restrict the user from entering certain values in the Enterprise Permitting & Licensing db. Conversely, drop-down fields do not have a restriction on values written to the EG_Template db. Therefore, exact spelling or careful matching to the Enterprise Permitting & Licensing configured values is not a requirement for fields intended for Enterprise Permitting & Licensing drop-down fields. Tyler maps the values through a separate table to translate the values to the appropriate Enterprise Permitting & Licensing value during conversion and collaborates with the Jackson County to validate the resulting mappings during the development phase of the conversion. Custom Fields (any fields not available in the master table for the module in question) Most legacy systems have some attribute fields that are not specified in the corresponding master table within EG_Template. Xxxxx refers to these as custom fields. Within each module exists a child table for such custom fields. Since these fields are specific to the legacy system(s), the Jackson County may add columns to these tables in EG_Template to accommodate any needed custom fields in the migration. For example, ‘permit_additional_fields’ is the table for extra fields relating to the ‘permit’ records. Gap Handling (where legacy data doesn’t fit anywhere within EG_Template) On occasion, legacy systems contain special features for which Enterprise Permitting & Licensing does not account in the EG_Template db. As a result, the need may arise to develop a modified solution to address special cases. Contacts Contacts generally fall into two categories:
Required Fields. All required fields on the MI eCVI must be completed for the certificate to be issued and considered official.
Required Fields. Fields marked with an * are required on the eCVI to maintain uniformity in data collection, integration into data management systems and to meet USDA standards except State of License and License Number. These blocks are marked N/A. The required fields are: a. Inspection Date b. Consignor Info: First and Last Name, Physical Address, City, State, Zip, County and Phone Number c. Consignee Info: First and Last Name, Physical Address, City, State, and Zip d. Purpose of Movement e. Species/Species Number f. Veterinarian’s Signature g. Date of Signature h. Veterinarian Printed Name i. Veterinarian Contact Information: Address, Phone Number, Email j. Veterinarian Federal Accreditation Number
Required Fields. Fields in red are required on the eCVI and must be completed in order for the certificate to be issued and official.
Required Fields. Inform Medix Clients of those fields that must be completed in order to process the Lab Order. If such fields are not completed, Lab Order shall be rejected and a warning notice sent to Medix Client by Medix System.
Required Fields. The followingfields are required on the certificate, and are used to maintain uniformity in data collection, integration into data management systems and meet USDAstandards: a. Inspection Date b. Consignor Info: first and last name, physicaladdress, city, state, zip, county and phone number c. Consignee Info: first and last name, physical address, city, state and zip d. Purpose of Movement e. Species/Species Number x. x ] v ] v [ ^ ] P v g. Date of Signature h. Veterinari an Printed Name i. Veterinarian Contact Information: Address, Phone Number, Email j. Veterinarian Federal Accreditation Number
AutoNDA by SimpleDocs
Required Fields. There are required fields on the MN eCVI. They must remain required and be completed in order for the certificate to be issued and official. These required fields are highlighted in red on the form. States of destination may consider other fields to be required based on their import requirements. Note: Consignor/Origin Info and Consignee/Destination Info must include physical addresses of where the animals originated and are destined.

Related to Required Fields

  • Required Filings The Company will file the final Prospectus with the Commission within the time periods specified by Rule 424(b) and Rule 430A, 430B or 430C under the Securities Act, will file any Issuer Free Writing Prospectus to the extent required by Rule 433 under the Securities Act; and the Company will furnish copies of the Prospectus and each Issuer Free Writing Prospectus (to the extent not previously delivered) to the Underwriters in New York City prior to 10:00 A.M., New York City time, on the business day next succeeding the date of this Agreement in such quantities as the Representatives may reasonably request.

  • Competing Products The provisions of Section 21 are set forth on attached Exhibit H and are incorporated in this Section 21 by this reference.

  • Territory 33.1 This Agreement applies to the territory in which CenturyLink operates as an ILEC in the State. CenturyLink shall be obligated to provide services under this Agreement only within this territory. 33.2 Notwithstanding any other provision of this Agreement, CenturyLink may terminate this Agreement as to a specific operating territory or portion thereof pursuant to Section 6.7 of this Agreement.

  • Licensed Products Lessee will obtain no title to Licensed Products which will at all times remain the property of the owner of the Licensed Products. A license from the owner may be required and it is Lessee's responsibility to obtain any required license before the use of the Licensed Products. Lessee agrees to treat the Licensed Products as confidential information of the owner, to observe all copyright restrictions, and not to reproduce or sell the Licensed Products.

  • Competitive Products Competitive Products" means products that serve the same function as, or that could be used to replace, products the Company provided to, offered to, or was in the process of developing for a present, former, or future possible customer/partner at any time during the twelve (12) months immediately preceding the last day of Participant's employment (or at any time during Participant's employment if Participant was employed for less than 12 months), with which Participant had direct responsibility for the sale or development of such products or managing those persons responsible for the sale or development of such products.

  • Commercialization License Subject to the terms of this Agreement, including without limitation Section 2.2 and Theravance's Co-Promotion rights in Section 5.3.2, Theravance hereby grants to GSK, and GSK accepts, an exclusive license under the Theravance Patents and Theravance Know-How to make, have made, use, sell, offer for sale and import Alliance Products in the Territory.

  • New Products You agree to comply with NASD Notice to Members 5-26 recommending best practices for reviewing new products.

  • Required Filings and Consents None of the execution, delivery or performance of this Agreement by the Company, the consummation by the Company of the Offer, the Merger or any other transaction contemplated by this Agreement, or the Company’s compliance with any of the provisions of this Agreement will require (with or without notice or lapse of time, or both) any consent, approval, authorization or permit of, or filing or registration with or notification to, any Governmental Entity, other than (a) the filing and recordation of the Certificate of Merger as required by the DGCL, (b) the Company Stockholder Approval, (c) compliance with any applicable requirements of the HSR Act and other applicable foreign or supranational antitrust and competition laws set forth in Section 4.5 of the Company Disclosure Schedule, (d) compliance with the applicable requirements of the Securities Exchange Act of 1934 (the “Exchange Act”), (e) compliance with the applicable requirements of the Securities Act, (f) compliance with any applicable foreign or state securities or Blue Sky Laws, (g) filings with the United States Securities and Exchange Commission (the “SEC”) as may be required by the Company in connection with this Agreement and the transactions contemplated hereby, (h) such filings as may be required under the rules and regulations of the NYSE and (i) where the failure to obtain such consents, approvals, authorizations or permits of, or to make such filings, registrations with or notifications to any Governmental Entity, individually or in the aggregate, would not reasonably be expected to have a Company Material Adverse Effect.

  • Territorial application This Agreement shall apply, on the one hand, to the territories in which the Treaty establishing the European Community is applied, and under the conditions laid down in that Treaty and, on the other hand, to the territory of the United States.

  • Manufacturing and Marketing Rights The Company has not granted rights to manufacture, produce, assemble, license, market, or sell its products to any other person and is not bound by any agreement that affects the Company's exclusive right to develop, manufacture, assemble, distribute, market, or sell its products.

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