CDR configuration

Note: The term "application" is used generically to refer to application, case, and license records in all CDR modules.

The CDR configuration stores settings for Infor Public Sector CDR. The root CDR node can have up to eight children: a General node and a node for each module (Building, Case, License, Planning, Project, Trade, and Use).

General node

The settings on the General node apply to all CDR modules. This node can have one attribute:

Attribute Description
Show Summary Set to True to enable the Summary tab in the application InfoViewers. This is an optional tab that displays summary information about the current application. Users can use their My Infor preferences to indicate whether they want to show this tab, and to configure the information that appears on it.

The General node can have three children: ContactSync, Electronic Plans, and Virtual Inspections.

The ContactSync node has these attributes:

Attribute Description
Add Alert Indicates whether Infor Public Sector will add an alert to an application's associated billing account if a contact sync fails.

This applies to application-based accounts. With application-based accounts, if you change an application's primary applicant, Infor Public Sector will update the contact information for the associated account as well. If this sync process fails, you may want to add an alert.
Alert Definition Type of alert to add to the billing account if a contact sync fails.

Electronic Plans node

The Electronic Plans node under the General node is used to configure the DigEplan integration for the Building Permits, Planning, Project, and Use Permits modules.

Note: The settings under the Electronic Plans node are not used for the Code Enforcement, Business License, or Trade License modules.

The Electronic Plans node has one child DigEplan node with three children: Profile - Customer, Profile - Reviewer, and Attachment Caching.

The Profile - Customer node is used to configured access to DigEplan for customers in Infor Rhythm for Civics. See the Infor Rhythm for Civics User and Administration Library on docs.infor.com for more information.

The Profile - Customer node has these attributes:

Attribute Description
Base Digital Services Application Url Base application URL for DigEplan.
Base DPC authentication Url Base URL for generating tokens.
DigEplan Tenant / Subdomain ID for a tenant or subdomain in DigEplan.
PatToken Personal access token. This is generated by a DigEplan administrator for a DigEplan tenant.
Product Name DigEplan product name. The default is APP.
Provider Type Information Specify the fully qualified class name and the assembly of the provider type. This is the electronic plan review provider, not the EDM provider.
Temporary Application Conversion API Url URL that is used to send the IDs of new instruments to DigEplan.
Token Expiration (In Minutes) Number of minutes before tokens expire. The default is 60.
Token Request Timeout (In Seconds) Number of seconds before token requests time out. The default is 100.

The Profile - Reviewer node is used to configure access to DigEplan for plan reviewers. This provides access to DigEplan from the review InfoViewers in Infor Public Sector. The Profile - Reviewer node has these attributes:

Attribute Description
Base Application Url Base application URL for DigEplan. This is the URL that the links in Infor Public Sector will use to open DigEplan.
Base Service Url Base service URL for DigEplan. This is the instance of DigEplan that Infor Public Sector will connect to.
Display Name Display name for the electronic plan review integration. This is the label that appears on the button in the Review InfoViewer. The default is DigEplan.
Provider Type Information Specify the fully qualified class name and the assembly of the provider type. This is the electronic plan review provider, not the EDM provider.

The Attachment Caching node is used to specify which attachments are cached and sent to DigEplan. Attachments are selected for caching based on the combination of an object moniker and a document type.

The Attachment Caching node has one or more attachment cache item nodes as children. Each item node has one attribute:

Attribute Description
Moniker Moniker of the Infor Public Sector object for which attachments will be cahced, such as Hansen.CDR.Building.BuildingApplication for building applications.

Each item node has a child Document Types node with one or more document type nodes as children. Each document type node has one attribute:

Attribute Description
Name Document type of the attachments that will be cached. Specify the reference ID of the document type, not the name.

Virtual Inspections node

The Virtual Inspections node under the General node is used to configure virtual inspection for the Building Permits module.

See "Configuring virtual inspections" in the Infor Public Sector Building Permits Administration Guide.

The Virtual Inspections node has one child VuSpex node. The VuSpex node has these attributes:

Attribute Description
Base Services URL Base URL for the VuSpex integration. This is the instance of VuSpex that Infor Public Sector will connect to.
Button Title Title to show on the button in the inspection InfoViewer that launches VuSpex for virtual inspections. The default is Launch VuSpex.
Provider Type Information Specify the fully qualified class name and the assembly of the virtual inspection provider type.

The VuSpex node has one child Authentication Information node with one attribute:

Attribute Description
API Key Specify the API key that is used for authentication to the base service URL specified on the VuSpex node.

Module nodes

The node for each CDR module has two children: Accounts and SupervisorApproval.

Each Accounts node can have these attributes:

Attribute Description
Hide Prior In a CDR Billing environment, if the account associated with an application changes, this setting determines whether the application InfoViewer will continue to show fee information from the old account. If set to True, the InfoViewer will only show fee information from the current account, and any fees remaining with the old account will no longer affect the application. If set to False, the InfoViewer will show all fees and payments from the old account, and the fees from the old account will still affect the application's milestone progression.

Each SupervisorApproval node can have these attributes:

Attribute Attribute
Pay Escrow Indicates whether supervisor approval is required to make an escrow payment if the payment will leave the escrow account balance below the defined minimum.
Note: The minimum balance for escrow accounts is not enforced in Cashiering. When using the Cash Register, supervisor approval is not required to accept a payment that will drop an escrow account below its minimum.
Refund Fee Indicates whether supervisor approval is required to refund a fee that is marked as non-refundable.
Refund Overpayment Indicates whether supervisor approval is required to refund an overpayment.
Transfer Move All Indicates whether supervisor approval is required to change the billing account associated with an application if the Move Everything option is selected. This options moves all fees and transactions associated with the application to the new account.