| Description | Configures the basic settings required by CGF service | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 9.0 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures a VLAN on a physical port | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | vlan, interface | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 9.0 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures automated security updates for a box | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 9.0 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 1 |
| Description | Configures a value for a site specific object | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | CC | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | service | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Features required | firewall | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures layer 2 bridges | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | bridge, interface | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 9.0 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures the config backup daemon for a box | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | backupdaemon | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features exclusively implemented | backupdaemon | |
| Features used | 7 | |
| Release compatibility (min.) | 9.0 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Add additional IPv6 addresses. | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Access Control List | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 9.0 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Configures the local authentication scheme | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Configures the MSAD authetication scheme domains | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Routing | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | routing | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Routing | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | routing | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures a firewall by using a repository link to a ruleset | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | CC | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | firewall, service | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures the Redirect authentication scheme | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Configures the local authentication scheme Users | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures the number of virtual interfaces. | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | virtualInterfaces, interface | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 9.0 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 1 |
| Description | Configures the basic settings required by every box | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | systemaccess, license, serial, managementnetwork, core | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features exclusively implemented | core | |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 1 | |
| Repeated usage (max.) | 1 |
| Description | Configures a link to a repository entry | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | CC | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | ADVANCED | |
| Features implemented | repositorylink | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures the LDAP authentication scheme | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Allows to configure SSH. | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | ssh | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Configures the automatic HA pairing functionality of physical appliances. | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 9.0 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | DNS Settings | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 9.0 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Configures DHCP relay for IPv4 | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | service | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 9.0 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Allows to configure the log cycling basic settings. | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | logcycling | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Configures a remote management tunnel for a CC managed box | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | CC | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | managementtunnel | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 1 |
| Description | Configures the MSAD authentication scheme | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Configures the Radius authentication scheme | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Allows to configure the Message Board. | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | boxmisc | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Configures a DNS service | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | dns, service | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures the Radius authetication scheme authentication servers | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures shared (failover capable) IPs | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | sharednetwork | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Allows to configure the REST API Service. | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | restapi-service | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Configures DHCP relay for IPv6 | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | service | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 9.0 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 1 |
| Description | Configures the LDAP authetication scheme domains | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures shared (failover capable) IPs | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | sharednetwork | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Adds a GTI VPN Tunnel between boxes in a Hub and Spoke topology | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | CC | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | vpntunnel, service | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Allows to configure file specific log cycling actions. | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | logcyclingactions | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Features required | logcycling | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Configures a simple DHCP subnet | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | dhcp, service | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.2 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (min.) | 11 | |
| Repeated usage (max.) | 12 |
| Description | Allows to configure REST API Service Tokens. | |
|---|---|---|
| Product | CGF | |
| Services | 2 | These services created of this Configuration unit is used. |
| Scope | GENERAL | A configuration unit can be available on any platform (general), only on the control center (CC), or only on unmanaged firewalls (unmanaged). |
| Level | BASIC | |
| Features implemented | restapi-service-token | Every configuration unit implements certain features, some of them exclusively, and also might require some features from other configuration units. |
| Features used | 7 | |
| Release compatibility (min.) | 8.3 | A configuration can be required to be used in a configuration template and some can be used several times. |
| Release compatibility (max.) | 10 | |
| Repeated usage (max.) | 12 |