/
Project Statuses

Project Statuses

Owned by Jared Fontenot
Dec 18, 2024
2 min read

Within the “Project Statuses” menu users have the ability to manage existing project status options AND create new ones. The Jurisdictions/Project Types that are accessible are limited to those assigned to the logged in user.

Explanation of Configuration Settings

  1. Description

    1. The display name for the status.

  2. Active

    1. Determines if a status will show in the dropdown on the project page/other areas of the software for selection

  3. Default

    1. This should already be set for your established project type implementation. Only one status can be the default for a project type. The default status will be set when manually creating projects or creating projects per acceptance of an online request submission.

  4. Color

    1. This setting is only additional/optional customization and has no “Functionality” attributed to it outside of coloring the project status in various search results.

  5. Allow CP Inspection Request

    1. Toggling this setting to “Yes” allows for customer portal users to submit inspection requests for a given project with the status set. A status configured with this set to “no” prevents the Customer Portal user from submitting an inspection request.

  6. Allow CP File Upload

    1. Allows Customer Portal users to upload files on a project that holds a status with this setting set to “Yes”.

  7. Customer Portal Visible

    1. If this setting is configured to be “no”, projects with the status will not be viewable in the customer portal in association projects.

  8. CP Search Visible

    1. If this setting is configured to be “no”, projects with the status will not be viewable in the customer portal.

  9. Allow Permit Printing (Fees)

    1. This setting will be used less and less for newer implementations - and eventually older ones once “modernized”.

    2. This setting presents customer portal users from printing Permit Documents that are associated/connected directly to a fee type in the customer portal.

  10. Queue Visible

    1. Controls whether projects for a given status are returned within the Department/Task queue in regards to Miscellaneous Requirements.

Explanation of Configuration Settings (Advanced Settings)

  1. Void Status

    1. This should already be set when viewed for a given project type; this is typically established at the initial phase of configuration by MGO Staff.

    2. This setting identifies the status that serves as the “VOID” status for the project type, excluding the projects set with it from reporting/etc.

  2. Lock Project

    1. Typically used in tandem with the void status, and for other restrictive statuses.

    2. Prevents users without administrative permissions from changing the project’s status once set into a “locked” status.

  3. Visible for Add to Existing Request Submissions

    1. When customer portal users apply for an add to existing online request type within the customer portal, projects that are in a status that has this setting to “no” will not be returned by the search for projects the submission can be filed under.

  4. Zero Balance Required

    1. If this setting is enabled for a specific status, a project will not be able to be moved into the status if there’s an outstanding balance to be paid.

    2. An example of this being used is if there needs to be a restriction in addition to automated requirements to ensure there’s not a zero balance prior to moving a project to “Permit Issued”.

Related content