Best Practices Rules and Automated Changes

Use this reference to learn about the multiple rules that apply and the changes that Specpoint makes to related content items when you set up best practices.

Navigate to the following contents:

• Rules for Project Parameter Best Practice
• Rules for Global Best Practice
• Rules for Tagging Best Practices
• Rules for Removing Best Practices
• Automated Changes in Applying Best Practices

Rules for Project Parameter Practice ()

For working with project parameter best practices, the following rules apply:

• Tagging from Source Project Parameters: You can tag a content item as a project parameter best practice () from any project that has the intended project parameters.
• Updating Best Practices Parameters: You can update the selected parameter combination of a project parameter best practice tag on a given content item from any project that has the set project parameters.

  When you update the parameters of a project parameter best practice tag, it may no longer apply to its previous projects.

• Multiple Existing Tags: A given content item can have multiple project parameter best practices () from different projects and different project parameters.
• Displaying Project Parameter Best Practice Tags: A project parameter best practice applies and displays only in projects that share all selected parameters.

  For example, A best practice applies to three parameters: City, State, and Building Type. The best practice tag will display only in projects that have the same three parameters.

• Updating Project Parameters: When you update the parameters of a project to parameters that do not fit a given project parameter best practice, the best practice stops displaying in the project.

  When you revert the parameters, the best practice displays again. No changes are made to any existing best practice.

Rules for Global Best Practice ()

For working with global best practices, the following rules apply:

• Tagging from Any Project: You can tag a content item as a global best practice () from any of your firm's projects.
• Global Tag Override:If you tag a given item as a project parameter best practice () in one project and then tag the same item in another project as a global best practice (), only the global best practice tag () displays.
  Note: In the project where the project parameter best practice item was set, the item displays a global best practice tag () but its best practice dialog box displays its original selections, which are the Set as Best Practice option and parameter options.

Rules for Tagging Best Practices

In setting best practices, the following rules apply:

• Permissions: Only administrators can set best practices.
• Supported Content: You can tag only supported content as best practices. These include:
  • Project Elements: Assemblies, families, sections, and product types
  • Content Items: Articles, paragraphs, pills/options, manufacturer pills under Manufacturers paragraphs and Basis-of-Design (BOD) Product paragraphs
  • Product Listings
• Required Addition: You can tag only content that are added and/or active in the project. These include:
  • Project Elements: Assemblies, families, sections, and product types must be added to the project.
  • Content Items:
    • Content items must be under added elements.
    • Articles and paragraphs must be active.
    • Pills/options and manufacturer pills under Manufacturers paragraphs and Basis-of-Design (BOD) Product paragraphs must be selected.
  • Product Listings: Product listing cards must be added to the project.
• Product Selection: Automation for Specpoint's intelligent product selection applies. These include:
  • When you tag a manufacturer pill in a Manufacturers paragraph, Specpoint tags the same manufacturer option set item in its corresponding BOD product paragraph as a best practice of the same type and vice versa.
  • When you tag a manufacturer pill, Specpoint tags its respective manufacturer product listing card as a best practice of the same type.
  • When you tag a product listing card, Specpoint tags the respective manufacturer option for the product listing in its corresponding manufacturer paragraph and BOD product paragraph as a best practice of the same type.
• Discontinued Inheritance: When you tag a content item, Specpoint no longer tags its parent content item with a best practice tag. For example, when you tag a family as a global best practice, its parent assembly will no longer receive the same global best practice tag.

Rules for Removing Best Practices

In removing best practices, the following rules apply:

• Permissions: Only administrators can remove best practices.
• Effect on Content: Removing a best practice tag does not remove any already added content item from any project.

• For all project elements, content items, and product listings, except pill/options:
  • When you remove a project parameter best practice tag () from an article, you remove the tag from all projects except projects that had the tagged article automatically activated:
  • When you remove a global best practice tag () from an article, you remove the tag from all projects.
• For pill/options, including manufacturer pills under Manufacturers paragraphs and BOD product paragraphs:
  • When you remove a project parameter best practice tag () or a global best practice tag () from a manufacturer option set item, you remove the tag from all projects except projects that had the tagged manufacturer option set item automatically selected for it during project creation.

Automated Changes in Applying Best Practices

After you set best practices, the following automated changes apply:

• Application Logic: Specpoint automatically adds a tagged best practice to a project only when you manually add the item's parent content to the project. Refer to the following:

  Tagged Content	Parent Content Requiring Addition or Activation
  Subassembly	Assembly
  Family	Lowest-level subassembly
  Article	Family
  Paragraph	Family
  Product Type	Family
  Product Listing Card	Product Type

• Discontinued Logic: Specpoint no longer adds all eligible tagged content during project creation.
• Automation Clashes: The automated addition and activation of tagged content are subject to Level of Specification and/or Sustainability requirements, if applicable.