This article provides information about the Settings/Configuration/Lists page.
...
List Type | Summary Usage |
Construction Type | For Projects (optional). The classification and fire rating for the project's buildings or structures. |
Contact Role | For Projects (optional). A reference person's association to a project. |
Country | For Projects, users and contacts (optional). Used for address records. |
| Occupancy | For Projects, building occupancy classifications refer to categorizing structures based on their usage and are primarily used for building and fire code enforcement. |
Source | For Standard Comments (optional). Typically, the year and name of code base from which content is sourced for Standard Comments (IBC 2012); see Standard Comment Library. |
State | Optional. Used for address records. States are filtered by Country. |
Street Direction | Optional. Used for address records. |
Street Type | Optional. Used for address records. |
...
Because ‘terminology’ often varies based on the purpose of the projects, we provide the ability to configure list records by Purpose, and rename List Types Display Nameto rename Lists, as desired.
List Type | Summary Usage |
| Application Type | For Projects. Optional list. |
Assignment Status | Required. Denotes the current standing of assignment records. There must be exactly one active and 'default' record mapped to each Parent List Item internal mapping for controlling workflow. Additional, non-default statuses may also be created. |
Category | Optional. If used, sort order is important. A comment affiliation; used as the primary heading and to sort comments within Correction Reports. Ex: comments in the General Requirements category (Sort Order = 1) typically sort first on Correction Reports. See Standard Comment Library. |
Comment Disposition | Required. Denotes the current standing or evaluation of the project comment record. There must be exactly one active and 'default' Disposition list record mapped to each Parent List Item internal mapping for controlling workflow. Additional, non-default dispositions may be created. |
Document Cycle | Required. Sort Order must be incremental. Denotes the current review cycle for the document. During intake, new document versions will automatically increased the document cycle by one, to the next available value based on Sort Order. We recommend creating document cycle records for the highest cycle you anticipate needing. For example, in some permitting agencies, a maximum of 4 cycles (submittals) is allowed per document. |
Groups | Required. Denotes user affiliation; often a discipline, division, department, or equivalent. Users who conduct plan review must belong to at least one group. Each plan review assignments must be assoiciated to a Group. Select Configuration/Settings/Group to open the Group lists. Plan review markups use the Group's color. Select a color for each Group list record. |
Impact | Optional. Denotes relative importance of a project comment. |
Priority | Optional. Denotes relative urgency of a project. |
Project Cycle | Required. Sort Order must be incremental. Denotes the Projects cycle/phase. |
Project Status | Required. Denotes the current standing or evaluation of the project record. There must be exactly one active and 'default' record mapped to each Parent List Item internal mapping for controlling workflow. Additional, non-default statuses may also be created. |
Project Type | Required. A project classification, usually based on the type of work expected. Automated (assignment) Distribution workflows are configured for Project Types. |
| Report Type | 'Corrections' as a report type for Correction report templates generated in the Project Comments page. 'Submittal Recommendations' is the report type for the Document Submittal Recommendations reports generated in goPost and from the Project/Documents upload page. |
Review Type | Optional. Denotes a specific discipline affiliation for assignments when multiple assignments must exist within a single Group for the same document. Additionally, Distributions rely on the 'abbreviation' to distribute plans during intake. Ex: a file named ‘ELEC_WiringDiagrams.pdf’ can trigger assignments to designated groups or users if the 'Electrical' Review Type abbreviation = 'ELEC'. |
Service Area | Optional. Regional/geographical area of a project site/address. |
Subcategory | Optional. If used, sort order is important. A comment sub-affiliation; used as a secondary heading and to sort comments within Correction Reports. Ex: comments in the General Requirements category may have a sub-heading for 'Building Envelope Requirements', followed by other subcategory headings. Standard Comment Library |
...
| Info |
|---|
When a new project is created, either the For Permitting or For Design Review ‘Purpose’ is chosen. This determines which set of lists will be used for the project going forward. Changing the purpose is not allowed once the new project record is saved. |
Adding List Records
- From the Configuration/Lists page, choose the appropriate Purpose and List Type.
- Select the + button to open the List record detail form.
- Enter a descriptive Label.
- Enter a four (4) character Abbreviation. (Alpha and numeric characters only.)
...
| Info |
|---|
New assignments will be created with the default, active 'Not Started' status. The assignment status will automatically change to the default, 'Active' status when users begin their plan review. |
...
Inactivating or Deleting List Items
- Toggle off the List Item is Active option to prevent it from being used in the future.
- List records that are inactivated will not appear in the dropdown controls.
- When a list record is inactivated, any project, document, assignment records that rely on the list record will show the list abbreviation and or list Label as a read-only value.
- In this situation, we recommend choosing another active list record.
- Inactivated records can be restored at anytime by toggling the 'Is Active' setting to On.
...