Spira 6.0: New Product based on another Product or Template?

Wednesday, June 19, 2019
Avatar

Here is an excerpt from the 6.0 Admin Guide that I am finding confusing:

  • decide what to base the product on. It can either be a new empty product, or be based on another product already in the system. Doing the latter will copy across its membership, settings and customizations;
  • select a template that will control the product. If you are creating an empty product (not based on an existing one) you can select any template in the system to use for this product, or you can start with a brand new template. If you are creating a product based on an existing one, then by default the template will be the same as the one the existing product uses. You can still create a new template in this case, which will effectively be a clone of the template the existing product uses.

So, this gets complicated, but my question is should I choose "new empty product" plus Template A or "another product" that uses the same template (Template A)? Will there be any difference in what copies over? Is there any advantage of adding a new product either way? Thank you.

1 Replies
Friday, June 21, 2019
Avatar
re: rcorvino Wednesday, June 19, 2019

Sorry if it is confusing, there is a slight difference:

  1. Creating a new product using an existing template, reuses all of the artifact configurations (types, priorities, workflows), custom properties/lists, notification events and templates.
  2. Creating a new product based on an existing one, does all of the items in bullet 1, plus it copies over the following in addition:
    1. Components
    2. Product membership
    3. Data synchronization data mapping
    4. Document Folders
Statistics
  • Started: Wednesday, June 19, 2019
  • Last Reply: Friday, June 21, 2019
  • Replies: 1
  • Views: 386