[Index]
Overview
You'll need to set up an LDAP user sync to sync in users from a specified LDAP directory into Automate.
Users synced in from LDAP appear at the hierarchy node where the LDAP user sync object exists. Once synced in, you can manage these users in Automate (via the User Management menu). For example, you may want to move users to other hierarchies, or to push users to CUCM.
When syncing in from LDAP, some fields are always imported into Automate, while others are excluded. For details, see LDAP Integration
Delete or Retain Associated Accounts at User Sync
You can configure (via Customizations > Global Settings) the LDAP user sync to delete or retain Cisco (CUCM) subscriber voicemail and Webex accounts when running syncs after deleting a subscriber.
Related Topics
Add LDAP Sync
This procedure adds a LDAP sync to prepare for syncing users in from LDAP to Automate.
Field | Description |
---|---|
LDAP Server | Mandatory. The LDAP server you're syncing from. |
LDAP Authentication Only | This setting is available only in Automate, and is disabled by default. Leave unchecked (clear) to sync in users from LDAP (from a predefined LDAP directory). In this case, the user passwords are authenticated against this LDAP directory. Select this checkbox (enable) to prevent user sync from the predefined LDAP directory. In this case:
|
User Model Type | Defines the LDAP object (from the configured LDAP server), and is used to import and authenticate users.
Contact the LDAP server administrator if you need to identify a non-default User Model Type to use. |
LDAP Authentication Attribute | The attribute used for creating an LDAP user. When Server Type is Microsoft Active Directory, options are: employeeNumber, mail, sAMAccountName, telephoneNumber, userPrincipalName. When Server Type is OpenLDAP, options are: employeeNumber, mail, telephoneNumber, uid. Custom values for a deployment are also allowed. |
Attribute | This value is used for LDAP authentication against LDAP when LDAP Authentication Only is enabled. |
User Entitlement Profile | Choose the User Entitlement Profile that specifies the devices and services to which users synced in from the LDAP server are entitled. The chosen entitlement profile is assigned to each synced in user. It is checked during user provisioning to ensure the user's configuration does not exceed the allowed services and devices specified in the entitlement profile. |
User Role (default)* | The default role to assign to the synced user (if no other LDAP custom role mappings are applicable for the synced user, then this fallback/default role will be applied). Mandatory. |
User Move Mode | Defines whether users are automatically moved to sites based on the filters and filter order defined in User Management > Manage Filters. |
User Delete Mode | Defines whether users are automatically deleted from Automate if they are deleted from the LDAP directory. If set to automatic, all subscriber resources associated with the user, such as a phone, are also deleted. Warning Setting this option to Automatic will delete all users from the LDAP server (in Automate and in the UC apps, phones, services, and so on). |
User Purge Mode | Defines whether users are automatically deleted from Automate if they are purged from the LDAP device model. An administrator can remove the LDAP user from the device layer even if the user has not been removed from the LDAP directory. Warning Setting this option to Automatic will delete all users from the LDAP server (in Automate and in the UC apps, phones, services, and so on). |
Inspect the default mappings and modify if required, see User Field Mapping.
Click Save to add the LDAP sync.
Note
By default, the new LDAP sync is initially inactive. See Synchronize Users from LDAP.
In the Global Settings, define whether to retain or delete associated webex and/or voicemail accounts in the user sync that runs after deleting a subscriber. See topic Global Settings (Webex App tab, Voicemail tab)
Related Topics
Global Settings in the Core Feature Guide
LDAP Sync Scenarios (Top-Down and Bottom-Up)
The table summarizes the two LDAP user sync scenarios that Automate supports:
Note
Although you can have different LDAP sync types at different parts of the hierarchy, it is recommended that you run either top-down or bottom-up LDAP syncs.
Sync scenario | Description |
---|---|
Top-down | Users are synced directly from the LDAP directory. User data is sourced from one or more LDAP directories. This setup defines how users are matched to be pulled in (for example, OU definition, LDAP filter, field filters, etc). Recommended for flow-through provisioning. |
Bottom-up | Users are synced indirectly from the LDAP directory, that is, where applications are integrated and syncing the users from the LDAP directory. For example, the system syncs via the CUCM, which is syncing to LDAP. |
Note
In a top-down or bottom-up LDAP sync, a system configuration template sets the CUCM (LDAP) user's identity field (userIdentity) to the user principal name (UPN), userPrincipalName, if it exists; otherwise it uses the email address. This is useful where a user has a different email address to the UPN and needs to be correctly mapped following a LDAP sync, and then the user is moved to a site.
LDAP Sync Lists
The table describes, for LDAP sync, LDAP sync lists, arranged in override order:
|
Fields required to list LDAP Users on the GUI |
|
Fields never imported from LDAP |
|
A change in these fields does not trigger an update |
|
From the LDAP data sync. Set up and used in scheduled syncs |
|
Fields to be imported from LDAP as set up with the LDAP server |
The following fields are always synced in an LDAP sync as their values are required to list LDAP users on the GUI:
Column Name | Field Name |
---|---|
Cn | cn |
Uid | uid |
Description | description |
User Principal Name | userPrincipalName |
SAM Account Name | sAMAccountName |
Any items in the LDAP Sync List from DROP_FIELD_LIST are excluded from the sync. This list is read-only.
DROP_FIELD_LIST=[ 'photo', 'jpegPhoto', 'audio', 'thumbnailLogo', 'thumbnailPhoto', 'userCertificate', 'logonCount', 'adminCount', 'lastLogonTimestamp', 'whenCreated', 'uSNCreated', 'badPasswordTime', 'pwdLastSet', 'lastLogon', 'whenChanged', 'badPwdCount', 'accountExpires', 'uSNChanged', 'lastLogoff', 'dSCorePropagationData' ]
See Data Sync Blacklist in the Advanced Configuration Guide.
An LDAP Sync List won't override any of the Data Sync Blacklist attributes (default or custom) in data/Settings. That is, for fields that appear in both the LDAP Sync List and in the Data Sync Blacklist, where the field value is different on the LDAP server, the LDAP sync won't trigger any update for the LDAP entity during a sync.
Given an existing LDAP server with a LDAP Sync List configured, when executing a data sync against the LDAP server, the existing Model Type List functionality from the LDAP data sync is maintained and takes precedence over the LDAP Sync List.
See:
A new LDAP server or one that existed in the system prior to release 19.3.4 allows you to choose the LDAP Sync List Option:
The configuration template (CFT) can also be created and applied to a server. See LDAP Sync List Configuration Templates.
Important
Besides the sync override order indicated above, manual or template sync lists are bound by the following considerations:
If no sync list is set up, LDAP sync is not affected by this list.
When updating the default sync list (or any sync list you choose), a full sync is required (during the next scheduled, or a manual sync). See the Sync and Purge menu, and for more information about data sync and data sync cache, see Data Sync Types.
Until a full LDAP user import is performed, user details are updated in the local cache (when opening a management page).
For these reasons, it is recommended that such updates and syncs should be scheduled for off-peak times, particularly where a large number of users requires a large sync.
For users targeted for Cisco-based services, a field must be mapped to the surname field for users. It is therefore important to include a field in the Sync List that is mapped to the 'surname' field, typically sn.
For details on the LDAP Sync List on the LDAP server, see: Set up an LDAP Server.
Note
By default LDAP user details shown on the GUI display all device/ldap/user fields. It is recommended that you create a FDP for device/ldap/user to contain only the fields from your LDAP Sync List in order to view LDAP user details according to your configuration.
LDAP Sync List Configuration Templates
Administrators can clone the default sync list Configuration Templates (CFTs) to a hierarchy, and modify them for use during initial LDAP server setup. Modified CFTs are available at the hierarchy on the Sync List tab (from the LDAP Sync List Template drop-down).
Two default CFTs are provided. Both can be cloned:
The table describes the default CFT fields:
Ldap Sync List Microsoft Active Directory | Ldap Sync List Open Ldap |
---|---|
Model Type: device/ldap/user | Model Type: device/ldap/InetOrgPerson |
sAMAccountName | uid |
givenName | givenName |
sn | sn |
title | title |
department | departmentNumber |
displayName | displayName |
employeeNumber | employeeNumber |
employeeType | employeeType |
homePhone | homePhone |
ipPhone | |
telephoneNumber | telephoneNumber |
mobile | mobile |
otherMailbox | |
facsimileTelephoneNumber | facsimileTelephoneNumber |
l | l |
c | |
streetAddress | |
st | street |
postalCode | postalCode |
physicalDeliveryOfficeName | physicalDeliveryOfficeName |
manager | manager |
memberOf | memberOf |
objectClass | objectClass |
o | o |
ou | ou |
If new LDAP attribute names are added to the cloned CFT and modified on the GUI, type the names in. Initially, all attribute names are imported. The full attribute list and naming is available on the GUI Sync List tab from the default sync list for the server. See: Set up an LDAP Server.
Enter a descriptive name for the cloned CFT, which will then show in the hierarchy on the drop-down list of Sync List CFTs that are available when you modify an LDAP server or create a new server.
Multiple LDAP Organization Units Per Hierarchy
Large corporations and institutions with multiple domains or agencies may require more than one LDAP Organizational Unit (OU) to be configured at a hierarchy.
Automate allows for multiple LDAP OUs at a hierarchy by providing for a unique combination of the following LDAP server properties at the hierarchy:
Multiple search base DNs can therefore be configured at the same hierarchy for different organizations within the same company, so that administrators and self-service users can successfully authenticate. For example:
LDAP server setup:
IP | Port | Search base DN | Hierarchy |
---|---|---|---|
1.2.3.4 | 389 | ou=SharedOUA,dc=voss-solutions,dc=com | Provider.Customer |
1.2.3.4 | 389 | ou=SharedOUB,dc=voss-solutions,dc=com | Provider.Customer |
Users:
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
LDAP Server | The assoicated LDAP server host. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
LDAP Authentication Only | This LDAP Server is only used for Authentication purpose. Default: false |
|
|||||||||||||||||||||||||||||||||||||||||||||||
LDAP Write Back Only | This LDAP Server is only used for write back purpose. This setting can be used when using a Microsoft AD onprem server that is synced to Microsoft Azure. Default: false |
|
|||||||||||||||||||||||||||||||||||||||||||||||
LDAP Write Back Template | The LDAP Configuration Template to use for Write Back. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Model Type | The LDAP model type for users. Default: device/ldap/user |
|
|||||||||||||||||||||||||||||||||||||||||||||||
LDAP Authentication Attribute | The selected attribute of the LDAP user login. When Server Type is Microsoft Active Directory, the following default choices are populated employeeNumber, mail, sAMAccountName, telephoneNumber, userPrincipalName. When Server Type is Open LDAP, the following choices are populated employeeNumber, mail, telephoneNumber, uid. If the default choices do not fit the deployment, custom values are allowed for this field. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Entitlement Profile | The default user server profile for users added via sync. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Role (default) | The default role to assign to the synced user (if no other LDAP Custom Role Mappings are applicable for the synced user, then this fallback/default role will be applied). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Language | The default user language for users added via sync. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Move Mode | The behavior for moving users to site. Setting this value to Automatic will trigger the system to apply the move filters (refer to User Management) automatically when users are sync'd into the system. Automatic is only applicable to creating new users. Setting this value to Manual means that users must be moved to site by an Adminstrator (refer to User Management). Default: Automatic |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Delete Mode | The behavior for handling users who are deleted from the LDAP directory. Setting this value to Automatic will trigger the system to automatically delete system settings associated with the user. Setting this value to Manual means that users deleted from the LDAP directory are no longer LDAP Integrated. Manual action by an Administrator is required to remove user settings. Default: Manual |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Purge Mode | Default: Automatic |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Information | Information regarding the specified action. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Field Mapping |
|
||||||||||||||||||||||||||||||||||||||||||||||||
LDAP Username * | The LDAP field mapped to the user's login attribute. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Data Username | The LDAP field mapped to the user's login attribute for local authentication. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Building Name | The LDAP field mapped to the user's building name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
C | The LDAP field mapped to the user's country. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Department Number | The LDAP field mapped to the user's department number. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Directory URI | The LDAP field mapped to the user's directory URI. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Display Name | The LDAP field mapped to the user's display name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Employee Number | The LDAP field mapped to the user's employee number. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Employee Type | The LDAP field mapped to the user's employee type. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Facsimile Telephone Number | The LDAP field mapped to the user's FAX number. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Given Name | The LDAP field mapped to the user's first name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Home Phone | The LDAP field mapped to the user's home phone number. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
IP Phone | The LDAP field mapped to the user's IP phone number. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Jabber ID | The LDAP field mapped to the user's Jabber ID. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
L | The LDAP field mapped to the user's city. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The LDAP field mapped to the user's email address. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Manager | The LDAP field mapped to the user's manager. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Member Of | The LDAP field mapped to the user's groups. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Mobile | The LDAP field mapped to the user's mobile phone number. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
O | The LDAP field mapped to the user's organization name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Object Class |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Other Mailbox |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Ou | The LDAP field mapped to the user's organization unit name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Photo URL | The LDAP field mapped to the user's photo URL. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Physical Delivery Office Name | The LDAP field mapped to the user's post office. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Postal Code | The LDAP field mapped to the user's postal code. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Preferred Language | The LDAP field mapped to the user's preferred language. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Sn * | The LDAP field mapped to the user's last name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
St | The LDAP field mapped to the user's state. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Street | The LDAP field mapped to the user's street. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Telephone Number | The LDAP field mapped to the user's telephone number. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Timezone | The LDAP field mapped to the user's time zone. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Title | The LDAP field mapped to the user's title. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Uid | The LDAP field mapped to the user's userid. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Unverified Mail Box | The LDAP field mapped to the user's unverified mailbox. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 1 | The LDAP field mapped to a custom string. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 2 | The LDAP field mapped to a custom string. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 3 | The LDAP field mapped to a custom string. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 4 | The LDAP field mapped to a custom string. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 5 | The LDAP field mapped to a custom string. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 1 | The LDAP field mapped to a custom list of strings. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 2 | The LDAP field mapped to a custom list of strings. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 3 | The LDAP field mapped to a custom list of strings. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 4 | The LDAP field mapped to a custom list of strings. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 5 | The LDAP field mapped to a custom list of strings. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Shadow |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Name * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
User Field Mapping |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Name * | The name of the user mapping object. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description | The description of the user mapping object. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Application name * | Application name like CUCM, LDAP, CUC |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Model Type | The model type used for this LDAP server. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Data Exist | Flag to see if data exists for the server. If data exist the username and email fields will be disabled. These mappings cannot be changed once data exists. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Name | The username corresponding to the the Username in Cisco Unified Communications Manager and Cisco Unity Connection server. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Email Address | The email address corresponding to the the Username in Cisco Unified Communications Manager and Cisco Unity Connection server. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
First Name | The first name corresponding to the user first name in Cisco Unified Communications Manager and Cisco Unity Connection server. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Last Name | The last name corresponding to user last name in Cisco Unified Communications Manager and Cisco Unity Connection server. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Password | The password corresponding to the user password in Cisco Unified Communications Manager. The password is hidden. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Building Name | Building name or number. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Country | Country name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Department | Department names and numbers. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Directory URI | Alphanumeric Directory URI (e.g. SIP URI) |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Display Name | Display name of the user |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Employee Number | Employee number of the user |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Employee Type | Employee type |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Facsimile Telephone Number | Facsimile Telephone Number |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Home Phone | Contains strings that represent the user's home phone number(s). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
IP Phone | Contains strings that represent the user's IP phone number(s). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Jabber ID | Jabber ID |
|
|||||||||||||||||||||||||||||||||||||||||||||||
City | Contains the name of a person's locality. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Manager | Manager. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Member Of | The user can be a member of a variety of groups. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Mobile | Contains strings that represent the user's IP mobile number(s). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Organization | The name of the person's organization. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Object Class | Object Class. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Other Mailbox | Other Mailbox. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Organizational Unit | The name of the person's organization unit. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Photo URL | Photo URL. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Physical Delivery Office Name | Physical Delivery Office Name. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Postal Code | Contains code used by a Postal Service to identify postal service zones. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Preferred Language | Preferred Language. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
State | Contains full names of state or province. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Street | Contains site information from a postal address. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Telephone Number | Telephone Number. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Timezone | Timezone. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Title | Title. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Unverified Mail Box | Unverified Mail Box. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 1 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 2 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 3 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 4 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 5 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 6 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 7 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 8 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 9 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom String 10 | Custom String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 1 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 2 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 3 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 4 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 5 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 6 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 7 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 8 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 9 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom List of Strings 10 | Custom List of Strings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom Boolean 1 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom Boolean 2 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom Boolean 3 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom Boolean 4 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom Boolean 5 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom Boolean 6 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom Boolean 7 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom Boolean 8 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom Boolean 9 | Custom Boolean |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Custom Boolean 10 | Custom Boolean |
|