Sub-Status Overview - Configurations
As of version 12, NEXGEN modules will have status and sub-status options. Sub-statuses in NEXGEN allow users to create custom statuses while still benefiting from NEXGEN standard status functionalities. A sub-status inherits a parent status's properties to facilitate reporting, workflows, and dashboard functions. Review the article information below to learn more about statuses and sub-statuses.
Parent and Child Status Overview
Across NEXGEN, various records allow users to identify the progress of a task via a status indicator. The modules listed below allow for a user to identify a status:
- Agreements*
- Condition Assessment
- Cycle Count
- Inspections
- Inventory Requisition
- Projects
- Purchase Order
- Service Request
- Work Order
With NEXGEN release version 12, users will be able to group NEXGEN standard statuses together to form "child" statuses. As of NEXGEN web version 12, users will be required to group custom statuses under NEXGEN standard statuses. (*The Agreements module will not be affected by the Parent/Child sub-status feature as of yet and will maintain the existing status functionality).
New NEXGEN Standard Statuses
The new standard statuses and the modules affected can be found in the table below.
| Module | Standard Parent Statuses |
| Condition Assessment | New, Open, Complete, Hold, Cancel, Close |
| Cycle Count | New, Open, Complete, Hold, Cancel, Close |
| Inspection | New, Open, Complete, Hold, Cancel, Close |
| Inventory Requisition | In Approval, Approved, Open, Pick, Issue, Reject, Hold, Close |
| Projects | New, Open, Complete, Hold, Cancel, Close |
| Purchase Order | New, Open, Reject, Receive, Complete, Hold, Cancel, Close |
| Service Request | New, Open, WO in Progress, Complete, Hold, Cancel, Close |
| Work Order | New, Open, Complete, Hold, Cancel, Close |
Custom statuses not standard to NEXGEN will need to be placed in one of the standard status groups listed above. Moving forward, users will not be able to change the display name of any NEXGEN standard statuses. If standard NEXGEN status names were modified at some point, they will revert back to the standard names above (i.e. if Close was changed to Closed, Closed will be revered back to Close). Across the board, the following will apply to certain statuses:
Standard Status | Rules |
New | New will remain the default status when creating records in NEXGEN. New records created by the NEXGEN will fall under New and not any of its child statuses. |
Cancel* | Cancel and any of its child statuses will remain as "end-of-life" statuses for records and records in the Cancel status group will only be editable if the record is re-opened by a user with the proper permissions (i.e. "Cancel" permission box in User Groups module). |
Close* | Close will remain an "end-of-life" status for records and records in this status will only be editable if the record is re-opened by a user with the proper permissions (i.e. "Close" permission box in User Groups module). Users WILL NOT be able to add child statuses under the Close parent status. Close will remain as an individual status. |
WO in Progress | The WO in Progress status on Service Requests will only appear when the Service Request is linked to a Work Order. Users will no longer see the WO in Progress status bar on Service Requests until the proper linkage to a WO is established. |
*Inventory Requisition records will not allow the "Re-Open" functionality and will continue to remain as "view only" records upon closure or cancellation.
Status Configuration Features
In addition to allowing users to group statuses together under one parent status, users will also be able to decide if certain parent statuses are selectable or not. For example, take the use case below.
Work Order Hold Status Use Case
City of Margaritaville would like to create a series of statuses for their work orders. To standardize how they place WOs on hold, they would like users to pick a specific status when a WO is put on hold. For example, instead of simply selecting the parent status of Hold, they would like users to select either Waiting on Contractor, Waiting on Items, Weather Issue, or Resource Constraints. With the "Non Selectable" feature, City of Margaritaville would be able to force users to pick one of the child Hold statuses to accurately report on why WOs are placed on Hold.
As shown in the use case above, if an organization decides that certain statuses should not be selectable and should instead force users to pick a child status, users can turn the "Non Selectable" flag on for those statuses.
In the example below the "Open" parent status for Work Orders has been marked as "Non Selectable". Since that status was marked as "Non Selectable" on Work Order records, users will not be able to select Open. Instead, users will have to pick one of the child statuses: Started, Delayed.
Related Articles
Lookups Overview - Configurations & Advanced Features
NEXGEN users are able to modify dropdown menus (lookups) for organization-specific needs and uses. To learn more about the Lookups module and how to adjust any dropdown options, please review the information below. Users that are unable to view the ...Create/Edit Departments and Divisions - Advanced Configurations
Users making adjustments to their NEXGEN site can update their configurations and make changes to their Department/Division structure. To add new Department/Divisions to your NEXGEN site, users must have at least the following Lookup Table ...Mandatory UDFs at Status Change - User Defined
User-defined fields (UDFs) can now be made mandatory at any status change on service requests and work orders. For example, certain UDFs might be required in order to Complete the work order vs Close the work order. Navigate to Settings > Setup > ...User Defined Module Overview
NEXGEN software has many fields that can be customized to personalize your software. These fields are called UDFs or User Defined Fields. Within the "Settings" module, you can edit these UDFs to align with your current workflows. To learn more about ...Clone a Layer - Configurations
Cloning a layer saves time when setting up the GIS integration. If you are importing layers with the same rest URL, you can clone the layer and then specify the resource definition, layer name, unique column name, etc. Clone a Layer Navigate to the ...