...

• Key Info: holds contact information, basic financial information, some representative information of the company, and goods and services provided by Vendors.
  Image Added
• Locations and Contacts: contains embedded tables for Location and Contact records that relate to the company.
• Sales Info: contains embedded tables for Opportunity, Quote, and Purchase Order records that relate to the company.
• Related Records: contains embedded tables for Support Case, Contract, Insurance Certificate, Assets, and Asset other records that relate to the company.
  

Image Removed

Use Case

Company records can be created in a variety of ways:

• Passively, via the Company Name field, whenever a new record gets created in the Leads table
• By members of the Admin, Admin Import, Business Admin, Contract Creator, Contract Manager, Contract Owner, Contract Requester, Marketing, Project Manager, and Sales groups directly in the Companies table
• Directly in the Contract Party Information section of a new Contract record: by clicking the New Company radio button, filling in the necessary information, and clicking Create Company
• Via the vendor onboarding module. Either triggered manually by a vendor manager, or created automatically when a vendor profile is approved.

Many other tables link to the information stored in the Company table, which is partially why Company records can be created in other places, and how Company records themselves can create new records in other tables. When a new Company record is created, the address information is inputted under the Locations and Contacts tab, and then stored as an individual Location record in the Locations background table. A Company with the Parent type may have several Location records, such as one for their billing office, for branch locations, and for their headquarters. If the location in question doesn't already exist as a Location record in the system, the new Location records are created automatically when Company records are created, similar to how Company records can be created when new Lead or Contract records are created. This connectivity allows workflows to run optimally while minimizing the potential for human error. For example:

...

Details on each rule are included in the list below:

• Creation for all companies: This rule runs when a company is created from any source. It sets the Company Roles to the Primary Role.
• Create: Vendor Profile Source Actions: This rule runs when a company is created from a Vendor Profile. There are two ways a company can be created from a Vendor Profile: (1) the Vendor Manager clicks the 'Create Company' button or (2) the Vendor Profile is approved. This rule copies the Source Vendor Profile ID to the Latest Vendor Profile ID. If the Source Vendor Profile is not Approved, it sets the Company's status to Pending. Finally, it performs linked record actions on the Source Vendor Profile and all Vendor Related Companies, Vendor Stakeholders, and Company Documents to update their Company ID to the new Company's ID.
• Create: Contract Source Actions (web, API): This rule runs whenever a new Company record is created by a user or by another rule in the systemfrom within a Contract record using the 'Create New Company' option. It consists of two actions: L: Set Company ID in source contract and U: Set Company Roles. L: Set Company ID in source contract is a Linked Field action that links the ID field in a Company record to the Company ID field in a related Contract record, and U: Set Company Roles is an Update action that updates the Company Roles field with the Company Type.
• Create: Sourcing Event Source Actions: This rule runs when a company is created from within a Sourcing Event. It sets the Status of the company to Pending. This rule only runs if the Vendor Management function is enabled.
• Create: Vendor Response Source Actions: This rule runs when a company is created from within a Vendor Response. It sets the Vendor ID in Vendor Response to this Company's ID. Additionally, if the Vendor Management function is enabled, it sets the Status to Pending.
  
• Edit: Contract Source Actions (web, API): This rule runs whenever a Contract Source ID field has been edited and changed to a non-zero value. It consists of a Linked Field action called L: Set Company ID in source contract.
• TB: Notify about expiring insurance certificates (disabled): This time-based rule runs every other day at 3 AM, and contains an action called E: Email Contract Owner of Upcoming Insurance Cert Expiration. This action uses a saved search to check if any active or in-progress Insurance Certificates records are set to expire within 14 days, and then emails the Contract Owner with results. This rule is comes disabled by default.
• TB Demo Data Update: This time-based rule runs once every month, updates Demo Date fields, and deletes History. It consists of two actions: "U: Update Demo Dates' and "D: Delete History for TB: Demo Data Update." "U: Update Demo Dates" is an Update action that replaces the Date Created, Date Updated, Original Start Date, and Reference As Of fields with a date one month in the future. "D: Delete History for TB: Demo Data Update" is a Delete action that deletes history entries that are created after "U: Update Demo Dates" updates the designated fields. This is a good example of ensuring that the actions in your rules are added in proper order, otherwise, the Delete action would have nothing to delete.

...