Skip to content

Commit

Permalink
Bleeding Edge
Browse files Browse the repository at this point in the history
  • Loading branch information
@AndrewDonkin-Gallagher
AndrewDonkin-Gallagher committed Nov 9, 2023
1 parent ef8f993 commit bb60827
Show file tree
Hide file tree
Showing 7 changed files with 201 additions and 172 deletions.
76 changes: 41 additions & 35 deletions ref/cardholders.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -680,40 +680,44 @@ <h1 id="topic-Documentation-suite" data-traverse-target="topic-Documentation-sui
<div class="panel">
<div class="doc-row">
<div class="doc-copy">
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, and non-cardholder items</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
<p align=center>
<img width=44 src="https://www.google.com/chrome/static/images/chrome-logo-m100.svg">
<img width=44 src="https://upload.wikimedia.org/wikipedia/commons/a/a0/Firefox_logo%2C_2019.svg">
<p>Best viewed in Chrome or Firefox. Microsoft Edge does not render the table of contents correctly in the orange column on the left, making navigation difficult.</p>
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, and non-cardholder items</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
</div>
</div>
</div>
Expand Down Expand Up @@ -9210,7 +9214,9 @@ <h2 class="panel-title">
</dt>
<dd>
<p>The last zone the cardholder entered. If the cardholder is a visitor and their last movement was to leave the site, this will be their visit&#39;s reception, not an access zone. 8.50 and later will present only the name of the reception and withhold the href in that case.</p>
<p>** Change is coming. **</p>
<p>
<strong>Change is coming.</strong>
</p>
<p>A future version of Command Centre will add the href field even if the item is a reception. So you can tell the difference, it will add a field called <code>canonicalTypeName</code> which will have one of two values: <code>accesszone</code> or <code>reception</code>.</p>
</dd>
<dt data-property-name="serverDisplayName" class="has-description">
Expand Down
72 changes: 38 additions & 34 deletions ref/events.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -356,40 +356,44 @@ <h1 id="topic-Documentation-suite" data-traverse-target="topic-Documentation-sui
<div class="panel">
<div class="doc-row">
<div class="doc-copy">
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, and non-cardholder items</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
<p align=center>
<img width=44 src="https://www.google.com/chrome/static/images/chrome-logo-m100.svg">
<img width=44 src="https://upload.wikimedia.org/wikipedia/commons/a/a0/Firefox_logo%2C_2019.svg">
<p>Best viewed in Chrome or Firefox. Microsoft Edge does not render the table of contents correctly in the orange column on the left, making navigation difficult.</p>
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, and non-cardholder items</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
</div>
</div>
</div>
Expand Down
72 changes: 38 additions & 34 deletions ref/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -57,40 +57,44 @@ <h1 id="topic-Documentation-suite" data-traverse-target="topic-Documentation-sui
<div class="panel">
<div class="doc-row">
<div class="doc-copy">
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, and non-cardholder items</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
<p align=center>
<img width=44 src="https://www.google.com/chrome/static/images/chrome-logo-m100.svg">
<img width=44 src="https://upload.wikimedia.org/wikipedia/commons/a/a0/Firefox_logo%2C_2019.svg">
<p>Best viewed in Chrome or Firefox. Microsoft Edge does not render the table of contents correctly in the orange column on the left, making navigation difficult.</p>
<p>The API&#39;s reference documentation divides into:</p>
<table>
<tr>
<td valign=top>
<a href=events.html>Alarms, events, and non-cardholder items</a>
</td>
<td>
<p> The alarms and events APIs let you download, monitor, and create events, and download, monitor, and manage alarms.</p>
<p> The alarms and events documentation also covers API calls that support divisions and items as they relate to events, as well as bulk status monitoring.</p>
</td>
</tr>
<tr>
<td valign=top>
<a href=cardholders.html>Cardholders and related items</a>
</td>
<td> The cardholder parts of the API let you manage your users, their personal data and credentials (cards), and their links to associated items such as access groups, roles, operator groups, competencies, and lockers. </td>
</tr>
<tr>
<td valign=top>
<a href=rest.html>Status and overrides</a>
</td>
<td>
<p> These functions let you monitor and override the types of Command Centre items that have their own status, including access zones, alarm zones, doors, fence zones, inputs, outputs, macros, elevator groups, interlock groups, and schedules.</p>
<p> Despite its name this section does not cover
<a href="events.html#status-subscriptions">mass-monitoring item status</a>. </td>
</p>
</tr>
<tr>
<td valign=top>
<a href=piv.html>PIV cards</a>
</td>
<td> This supplement describes how to work with PIV and PIV-I cards. It is separate from the main cardholder documentation in the interest of brevity. </td>
</tr>
</table>
</div>
</div>
</div>
Expand Down
Loading

0 comments on commit bb60827

Please sign in to comment.