Work with TRM lifecycle with wildcard
You can use Technology Reference Model (TRM) lifecycles with wildcards to update multiple TRM software product lifecycles simultaneously without having to specify the exact minor version details of individual TRM software products.
A TRM lifecycle with a wildcard is a TRM software product that has lifecycle version that ends with a '*'. The '*' means that exact specific version details aren’t provided.
Use of TRM lifecycle with wildcard
The TRM lifecycle with wildcard helps you to automatically identify, categorize, and update TRM software products.
You can also create technical debts in bulk for multiple unapproved TRM software product versions, simultaneously.
Suppose you use Microsoft PowerPoint and have multiple versions like 1.1, 1.2, 1.3 installed for your organization. You create a TRM wildcard with the version ending 1.*. Now, you update some details of the TRM lifecycle with wildcard. When the Populate TRM technical debts in the EA Workspace job runs for the TRM wildcard, the updated data from the TRM lifecycle with wildcard is passed on to versions 1.1, 1.2, 1.3.
Create a TRM lifecycle with wildcard
A TRM lifecycle with wildcard is created in a similar process as to how you would request a TRM product lifecycle. For information on how to add a TRM product lifecycle, see Add a TRM product lifecycle.
The only difference is, the TRM wildcard version ends with a ‘*’.
You must be a part of the enterprise architects group to be able to create a TRM wildcard.
Limitations of TRM lifecycle with wildcard
A TRM wildcard can’t create technical debts when the full version of a particular TRM software product exists.