Endpoint Management User Group (Osterreich, Schweiz, Deutschland)

Expand all | Collapse all

How to associate new software release to existing software products?

  • 1.  How to associate new software release to existing software products?

    Broadcom Employee
    Posted 08-07-2014 02:47 AM

    Hello, community,

    I have a customer who has created lots of software releases and software products.

    Every time if they create a new software product in CMS 7.5 they open the console and based on the entered filter-criteria for the product different software releases will be associted with this product IF(!) they manually save this new filter-definition.

    But it turns out that if there is already a software product but some new software releases were created and/or detected these releases will NOT automatically associated with the existing product even if the filter is already correct.

    Only manual solution till now is to re-open the software product and to type a letter anywhere in the filter and to delete this letter immediately. This will force a refresh of the list of shown software releases for the product and only if you manually save this new result then the associations between the product and the new releases will be updated/created in the database.

    Is there any way to automate this process?

    We tried the OS-schedule "NS.Nightly schedule to associate Software component to software product.{a48d3b11-5169-464b-9773-6c0f476e7748}" but this is not doing the trick. Even exporting the software product in to a file, deleting it and re-importing it will not force a refresh associations.

    Any solutions and even ideas are more than welcome!

     

    Greetings,

    Carsten



  • 2.  RE: How to associate new software release to existing software products?

    Broadcom Employee
    Posted 08-08-2014 04:00 AM

    Hi, Carsten:

    It seems that the association between the software product and the releases is only made when saving the filter criteria, and this conditions are not evaluated again later.

    I would recommend you to open a support case (may be there is a step to follow in order to get this refresh to be done automatically) or to publish an idea so this is fixed in a patch.