Feature Requests

Feature Request for selecting Line CSS at time of provisioning

Feature requested by Gareth from Newmont Goldcorp Inc. He would like APM to have the option to select the CSS at the line level when provisioning. Currently this is available when doing an edit job, but there isn't an option if it were an add. This is the description of what he is looking for:


We need the ability to select the available Line level CSS when running provisioning jobs. The reason being is that we have a 4 tier Line Level CSS depending on the user/location (Local/TollFree – National – International – FAC). Currently we have been setting it to a default CSS but this is becoming cumbersome as we have to change the line CSS to the correct one in CUCM after the Akkadian Job has been run. Ideally, we’d like to lock the available CSS’s to only show what’s relevant for the site that’s being provisioned and not show all CSS’s in the cluster.


I suggested using a site template since he mentioned location, but he said this would not be a good solution since each site has a default CSS and they change it based on the user type.

  • Joanna Niles
  • Jun 3 2021
  • Shipped
  • Attach files
  • Admin
    Tom Bamert commented
    January 26, 2023 14:05

    This feature is now available in APM 5.2.7. In a Site Template you can create and expose the CSS field with particular options for the site. For example, if each site has 4 CSSs, you can create a drop-down list with the applicable CSSs for that site and only those will be available at provision for that site.

  • Joanna Niles commented
    January 05, 2022 18:04

    Update from user:


    Unfortunately the suggested solution of using a site template isn’t really manageable as I have 40 + sites in this service group, with each site having 4 line CSS’s. If I were to use the suggestion below, I would then need 160 sites. This would be impossible to manage going forward, especially if there is something else within a specific site which would need updating. That would require making the change 4 times (once for each of the CSS sites). I’m sure you can imagine the nightmare that would be!