TRM: How to map Software Product to TRM Product if Requester selected "Is New Product"

Manu15
Tera Contributor

Hi APM / TRM Experts,

we are using APM with SAM Professional on a Vancouver release and we are going our first steps in TRM.

 

As a requester you can select "Is New Product" in the out of the box request "Request TRM Product":

Request TRM Product_Is_New_Product.JPG

 

 

 

 

 

 

 

If approved, this will create a TRM Product without relation to a Software Product [samp_sw_product]. Neither in the approval step nor in the TRM Product the relation to a Software Product is editable.

Request TRM Product not editable.JPG

 

 

 

 

 

 

This looks quite a bit uncool, because there is no way to get this valuable relation and no possibility to sync it with Software Models (via Certified button in Software Model).

Is this an ACL issue or did I just miss the option to set this relation?

I've got the sn_apm.apm_admin role and I am member of the Enterprise Architect Group

 

Thanks for help 🙂

5 REPLIES 5

MarkPenn
Tera Contributor

I have the same question.

mcastoe
ServiceNow Employee
ServiceNow Employee

Hi @Manu15,

 

Indeed this is a missing feature.   We have a request into product to address the situation.  It is as you have determined, it is a set of ACL which makes "configuration" impossible as these are protected configurations.  For now, the best approach may be some sort Related link that via script unsets the Is New checkbox and then allows the Software/Hardware Product to be updated.  Based on the product name, it could do a lookup and set it.  Note that this is just a work-around.

Another work-around would be using the intake request, when the request is approved, auto-create a new Custom Software Product and associate it to the TRM Product and unset the Is New.

 

mark

Manu15
Tera Contributor

Thanks @mcastoe,

that makes the situation clearer for us. Then we will create a custom catalog item that includes a preceding step to create a custom product.
The disadvantage of this solution is of course the loss of time in the process, because the custom product has to be created by the SAM team first and the request cannot be routed immediately.
The advantage, however, is higher data quality. In our initial SAM phase, we created many custom products very sloppily and as quickly as possible. This was a bitter revenge because the product type (licensable) was often not set correctly and we had to create them again.
In the meantime, we have switched to creating custom products very carefully. This takes time, but then we have good data.

I look forward to this missing feature being fixed in the future 😉

 

Cheers

Manu

 Hi Mark,

It's been 9 months since your post.

Has this issue been addressed in Xanadu or Yokohama?  If not, when?

Thanks,

Phil