Advisory: Support Portal Maintenance. Login is currently unavailable, more info available here.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Service cannot be updated. It is currently being used in Business Application Rule(s)

Hallo,

wenn I try to edit or change a service in a existing firewall Rule I got the massage "Service cannot be updated. It is currently being used in Business Application Rule(s)"

So everytime I have to remove the service, safe the rule an now I can edit the service. This workaround is very annoying.

My Customers appliances are on Version SFOS 17.0.5 MR-5 and I think the problem exists since version 17.x.x

 

Kind regrets



This thread was automatically locked due to age.
Parents
  • Yes, since static Ports it was converted to Services Objects the management it is terrible.

    - To upgrade a service objects, it is needed remove from Business Application Rule, upgrade Service Object and after this add again on Business Application Rule

    - On Business Application Rule list, it is impossible to know (when you move mouse over rule) which ports are being used in rule. (it is needed check Service Objects to check the ports)

     

    IMHO the old method (fill the ports in usiness Application Rule) it was more more easy and less complex. THis current way require a lot of effor to a simple acction.

     

    Best regards

  • Wow, this is terrible. Wenn I have a Service Object which is part of 10 or more Objects I have to remove it from all the Rules.

    This can't we the way!!!

  • Ran into this bad behavior in SFOS 17.0.8 MR-8.  Anyone know if it's on the roadmap yet to be improved in newer versions?

Reply Children
  • I'm bumping this as well. There is no way that you should have to disable every single rule to make a simple service rule change. Why was this considered acceptable in development?

     

    The other question is, why does it allow you to edit the service if it knows you are using it elsewhere and it's not allowed, not even from the rule you are using it with?