Checklists node
The node can have one or more nodes and one or more nodes as children.
Category
You can use nodes to organize your checklists. A node can have one or more nodes and one or more other nodes as children. To set up checklists, you must add a CDR category with a child category for each CDR module.
Each node can have these attributes:
| Attribute | Description |
|---|---|
| AccessItem | List of permissions in Access Control that control access to this category. Enter one or more access IDs in a comma-separated list. |
| Description | Description of the category. |
| Id | Unique identifier for the category. To add checklists, first add a category with CDR as its ID. The category for each module has its ID set to the name of the module, such as Building. |
Group
To define a checklist, add a node to the category node for a CDR module. Each node has one attribute.
| Attribute | Description |
|---|---|
| Id | Unique ID for the group. |
Each node has one child node. The node has one or more nodes as children.
CheckList
Each node has one attribute.
| Attribute | Description |
|---|---|
| Id | Unique ID for the checklist. |
Each node has two children: and .
Groups
The node has one or more nodes as children. Each node represents an entry in the checklist. Note that checklist groups are defined in the configuration only. They do not correspond to code violation groups in Infor Operations and Regulations. Each node can have these attributes:
| Attribute | Description |
|---|---|
| Description | Description of the group. |
| Filter | Filter used to select the code violations for this group. You can also use nodes to add code violations to a group. |
| Id | Unique identifier for the group. |
| QuickEntryItem | ID of the code violation to add when the user taps the quick entry button. You can use the quick entry button to add a predefined code violation with a single tap. |
| QuickEntryText | Text that is displayed on the quick entry button for this group. |
Each node has one child node.
Items
The node has one or more nodes as children. Each node represents a specific code violation type in Infor Operations and Regulations. Each node can have these attributes:
| Attribute | Description |
|---|---|
| Description | Description of the item. |
| Id | Unique identifier for the item. This should match the ID of an existing code violation setup. |
ApplicableTypes
The node has one or more nodes as children. Applicable types are the application, case, or license types that the checklist applies to. Each node can have these attributes:
| Attribute | Description |
|---|---|
| Id | ID for the applicable type. This should match the ID of an existing application, case, or license type. |
| ProductFamily | Module or product family of the applicable type, such as Building or CodeEnforcement. |
Each node has one child node.
ActivityTypes
The node has one or more nodes as children. Activity types are specific inspection types that the checklist applies to. This should be existing inspections types defined for the application, license, or case type specified by the parent node.
| Attribute | Description |
|---|---|
| Id | ID for the activity type. This should match the ID of an existing inspection type. |