Commander supports loading floor access group definitions en masse via the upload of a CSV file. After clicking the CSV Upload command button, Commander will display the upload dialog:
Like the upload of users via CSV, the upload of floor access groups
must confirm to the file format as indicated in the dialog. The easiest approach towards
creating an an intial CSV file is to copy-paste the example in the
dialog and modify according to one's needs. The fields in the CSV are:
Name. Indicates the floor access group to add, modify, or remove, contingent upon the Action value. See below for details.
Schedule. Indicates the schedule for the floor access group rule. The schedule must already exist for the record in the upload to be successfully processed.
Bank. Indicates the elevator bank for the floor access group rule. The elevator bank must already exist for the record in the upload to be successfully processed.
SrcFloors. Indicates the source floors from which the user may place a call. The floor values must match the Floor Marking values as specified by the deployer in the Floors component of the car group. Unrecognized floors will emit an error and will be ignored by the upload, whilst valid floors will still be proceesed. Note that two records in the CSV with the same schedule, bank, and source floors is not currently supported.
DstFloors. Indicates the destination floors from which the user may place a call. The floor values must match the Floor Marking values as specified by the deployer in the Floors component of the car group. Unrecognized floors will emit an error and will be ignored by the upload, whilst valid floors will still be proceesed.
Active.
Indicates whether the floor access rule is in effect. The value must be either true
or
false
. If false
, the rule will be created for the associated
floor access group, but will not be in effect until toggled on by the administrator.
Active.
Indicates whether the floor access rule is in effect. The value must be either true
or
false
. If false
, the rule will be created for the associated
floor access group, but will not be in effect until toggled on by the administrator.
Ban.
Indicates whether the floor access rule is a Ban rule. The value must be either true
or
false
.
Action.
Defines what the system should do with the record. Valid values are Merge
or
Remove
. The Action value must be consistent across all records
for the same floor access group (i.e.: you cannot indicate to remove a floor access group while also
indicating records to merge). If the Action value is Merge
,
the existing definition of the floor access group is replaced with the set of rules in the
CSV file. Existing membership in the group is preserved.
If the floor access group does not already exist, a new one is
created, and any relevant ACS users (i.e.: those who have been synchronized and verified) are
automatically placed within the floor access group. If the Action is
Remove
, the floor access group is removed from the building.
All changes to floor access group definitions made by the CSV upload go into effect immediately.
Note | |
---|---|
For Concert™-licensed buildings, Floor Access Group definitions in the CSV that do not match the access groups synchronized from the access control system will be ignored. |