Application Properties

This appendix describes application properties for Common Intake. These may be administered through the Cúram system administration application - see the Cúram System Configuration Guide for more information.

Table 1. Common Intake Environment Variables.

This table contains Common Intake environment variables.

Property Name

Description

Default

curam.case.product.registrars List of product registrars. curam.citizen.datahub
.holdingcase.holdingevidence
.fact.HoldingEvidence
RegistrarFactory,curam.
sample.sl.fact.SampleSporting
GrantEvidenceRegistrar
Factory,curam.core.sl.
infrastructure.fact.Participant
EvidenceRegistrarFactory
curam.applicationsearch
.applicationsearch
Whether intake applications should be included in the application banner search. YES
curam.application
.applicationtransfer
Whether the application transfer is enabled. YES
curam.address.intakeprospect
personregistrationdefault
addressdatalocale
Sets the locale for the address data while registering a prospect person when creating an address for which no details are provided. en_US
curam.intake.map.default
.zoom.level
This property is used to configure the initial zoom level of the Google Maps display on the Service Provider screen. Zoom levels between 0 (the lowest zoom level, in which the entire world can be seen on one map) to 21+ (down to individual buildings) are possible. 11
curam.intake.map.
default.center.latitude
This property is used to configure the default latitude of the center of the Google Maps display on the Service Provider screen. -89.40570831298828
curam.intake.bom.
milestoneconfiguration.
updatestartdate.enable
When specified to true, this flag will ensure that start date of milestone configuration entity will be set to current date while transporting. true
curam.assignment.of.
application.to.workqueue
.enabled
Indicates whether or not an application can be assigned to a work queue. Very importantly this variable will be used in conjunction with the user's Intake Configuration, so if this variable is enabled and the user's allocation target type is a work queue, then the application will be routed to the work queue. YES
curam.application.update.
person.details.from.script
.enabled
Indicates whether or not a person's participant details should be updated with information captured in the application script. NO
curam.application.person
.contact.details.set.to
.primary.from
.script.enabled
Indicates whether or not the contact details of a person captured via the application script should be set to the primary details of that type, e.g. phone number. NO