Why Restrictions on Firewall tables?

[Suggy]

Why Firewalls related tables like

'Palo Alto Firewall Devices' [cmdb_ci_firewall_device_palo_alto]

Cisco Firewall Devices [cmdb_ci_firewall_device_cisco]

We want to create few firewalls in those tables, but NEW button is disabled OOTB.

We want to delete few entries, but Delete option is disabled

We wanted to see the audit (History-> List) but audit is disabled.

Why so?

PS - Its a new customer instance. Same behavior in all instances.

[M Iftikhar]

Hi  @Suggy ,

The Palo Alto Firewall Device table (cmdb_ci_firewall_device_palo_alto) and Cisco Firewall Device table (cmdb_ci_firewall_device_cisco) are vendor-specific extension tables that extend from the Firewall Device table. These tables are designed to be populated automatically by Discovery, using the respective vendor's Discovery pattern which is why New/Delete and Audit options are disabled out-of-the-box.

I found these official community doc which may help u :
https://www.servicenow.com/docs/bundle/zurich-it-operations-management/page/product/service-mapping/...

https://www.servicenow.com/docs/bundle/xanadu-it-operations-management/page/product/service-mapping/...

I also found a  a similar scenario question discussed in the community : 
https://www.servicenow.com/community/developer-forum/new-button-missing-on-newly-created-ci-class/m-...

Thanks & Regards, 
Muhammad Iftikhar 

If my response helped, please mark it as the accepted solution so others can benefit as well.

[Suggy]

@M Iftikhar There are several tables which Discovery populates.

Tables like Applications, Software installations etc all are meant to populated by discovery but still we have option of manually creating the CIs on those tables.

Why exclusive this firewall class this restriction is there? Thats my question.

And why AUDIT is disabled? Thats a basic function required.