Skip to main content

Infor Public Sector / Hansen Config – CDR – Reviews

606 Digital Logo Mark

Infor Public Sector / Hansen Config – CDR – Reviews

Reviews in Infor Public Sector / Hansen allow organizations to inject manual review processes into application workflows, and they are the entity within the system that captures all of the information that must be gathered during the review.  It is possible to define any number of Review Types within the system.  Each Review Type can have its own Detail Pages and Grids, and custom Review Results can be defined as well, for the ultimate in flexibility.

Defining Review Types

Here are some considerations when defining Review Types:

Review Types can be defined logically for each task they are meant to represent.  For example, if the Zoning Department must review a specific type of application, then a “Zoning Review” probably makes sense.  Or if the Transportation Department has to review an application for possible conflicts during the proposed project date range (such as parades, block parties, or other street repair), and they must also perform a plan review, then two Review Types might make sense even though it is the same staff performing the reviews.  This will assist both the organization and the applicant in knowing why an application is being held at a specific milestone – perhaps the plans are ok but there is a marathon scheduled at the beginning of the project.

It is possible to grant permissions to specific user groups based on Review Types, so if you have a user or group of users that are responsible for a specific review task this should be its own Review Type.

Custom content in the form of Detail Pages and Grids can be defined and added to specific Review Types.  Our discussion of Detail Pages and Grids provides pointers on how to define different Detail Pages for AP Types, and similar rules will apply for Review Detail Pages and Grids.  If you have multiple Review Types that all make use of the same Review Detail Pages, perhaps they could be combined.

Knowing the time it takes between Review creation, assignment, and completion can provide insights into any potential bottlenecks and help organizations improve their time to permit.  Defining different Review Types can assist with this analysis by providing more granular information that is easier to report.

Defining Review Results

Review Results are completely configurable.  You can define any number of result types, however we typically advise that you stick to the basics, such as:

Pass, Fail
It doesn’t get any more straightforward than a result of Pass or Fail, and at their core this is all you should ultimately expect from a review process.  If you need to capture more information than that while resulting a Review, consider using custom Detail Page questions.
Incomplete (Partial, etc.)
Many times a Review process will be started and it is determined that some additional information is required from the applicant or elsewhere before the Review can be completed.  In this scenario it can still be advisable to track that the Review has started, and the reviewer has determined some additional information is needed.  You could also track the fact that the review has started through the system’s Start and End Date/Time fields, however then you would lose track of the number of times a reviewer had to revisit the application for a single review process – you would only know when it started and when it was completed.  By generating another Review when an “Incomplete” result is entered you are now tracking the number of times a Review was revisited.  This is the kind of information that can help guide organizations towards more efficient processes.

If you want to take Review Results further, you can also create Review Results that tell the system where to go next in the workflow.  One simple example might be:

If the reviewer decides some enforcement action is required, your system might be configured to generate a Case in the Code Enforcement Module if this Result Type is selected.  Further, you might have some custom validation logic that requires the reviewer to answer some specific questions, or to answer them in a specific way (forcing them to select a reason, for example).

Permissions can come into play when defining Review Results as well.  Perhaps you only want someone in a supervisory role to be able to select Enforcement as a Review Result.  Limiting Result Types based on user roles is something can be easily configured in Infor Public Sector / Hansen.


We hope these pointers are able to assist you in defining your Review Types and Review Results in Infor Public Sector / Hansen.  If you have a specific Reviews design decision that you are working through, and you would like some input, please feel free to reach out.  We are always happy to help.

Where to Now?

Read our Introduction to Infor Public Sector / Hansen CDR Configurations

Have questions or want to learn more?

Connect With 606