To create a new application type

The procedure to create a new application type is as follows:

1. Navigate to Quick Menu > Allocations > Configuration > Application Type. The Application Type window is displayed.
2. Click on New Application Type. All fields are activated ready for data entry.
3. Enter a Description for the new application type into the field provided e.g. General Needs, Shared Ownership, etc. 1.
4. Using the Company drop-down field, select the company relevant to the operating boundaries of this application type.
5. Using the Form source drop-down field, select the delivery method to be employed for the collection of responses linked to this application type i.e. Form Template or Generic Form. Where Generic Form is selected, activate the adjacent For use externally attribute, as required, to ensure that each form instance is accessible to other stakeholder systems e.g. Tenant Portal.
6. Using the Enquiry form drop-down field, select the introductory question form template appropriate for this application type, as required 2. Conditionally, use the Enquiry form fail advice and Enquiry form pass advice drop-down fields to control the contextual notes displayed to the end user or housing applicant on submission of an enquiry form of this type.
7. Using the Application form drop-down field, select the main question form template appropriate for this application type, as required 3.
8. Using the Application advice drop-down field, select the appropriate parameter value for this application type i.e. the contextual notes displayed to the end user or housing applicant on submission of an application form of this type. See To define an application advice parameter value for more information on the compilation of these workflow notifications.
9. Using the Area need drop-down field, select the match criteria defining the area need requirements for this application type.
10. Using the Submit application case type and Update application case type drop-down fields, select the matching case classifications to be launched in response to an application form being either submitted or updated 4.
11. Where alternative applicant offers are permitted, even though an offer has already been made through this application type, activate the Allow multiple offers tick box provided.
12. Where a bespoke SQL stored procedure has been created to execute potentially complex refusal rules, enter the procedure name into the Unreasonable refusals complex rule field provided 5. Proceed to step 15.
13. Otherwise, enter the Number of unreasonable refusals allowed for applications of this type i.e. the number of offers an applicant can legitimately refuse before action is taken; the adjacent Unreasonable refusals time period (days) field is then used to capture the duration over which cumulative refusals are counted.
14. Additionally, using the Refusals exceeded action drop-down field, select an appropriate action to be taken should an applicant exceed the maximum number of unreasonable refusals i.e. Points Penalty, Suspend, Message or Create Case. Conditionally, where a points penalty action is selected, enter the number of points to be deducted from the application in the Points penalty field, together with the matching Points penalty priority weighting. Alternatively, where an application suspension action is selected, enter the number of days over which an application should be suspended from the waiting list in the Suspend application for field, together with the matching Suspension type classification. Similarly, where a message action is selected, enter the desired syntax in the Message Text field. Finally, where a Create Case action is selected, use the Refusals exceeded case type drop-down field to select the specific case classification to be launched in this scenario.
15. Using the Review method drop-down field, select the automatic review, where applicable, to be conducted on applications of this type.
16. Using the Contact group type and Contact type drop-down fields, select the desired classifications to be used when new contacts and their group memberships are created as part of the application process.
17. Choose an Effective from date for this application type i.e. the date on which it came into effect 6.
18. Choose an Effective to date if the application type is to be reviewed on a specific date or to capture a cha6nge of circumstances; a blank field means the application type will be continually valid.
19. Click on Save. The new record appears in the alphabetical list 7.

Note

1 System validation rules ensure that the description entered for each new application type is unique for the effective period.

2 The subset of displayed enquiry form options will be steered by the chosen Form source.

3 The subset of displayed application form options will be steered by the chosen Form source.

4 These options are only available in the instance where Generic Form is specified as the delivery method for applicant responses.

5 Where a SQL stored procedure is used to steer the refusal rule actions, the Number of refusals allowed field and associated elements become inactive.

6 The Effective from date defaults to the current system date and cannot be left blank.

7 To amend the details of an existing application type, select a record from the alphabetical list (or enter its name into the Search Application Types field) and repeat steps 3 through 19. By default the list is filtered to show Current application types. An alternative filter can be applied using the Select view drop-down field: Expired, Future or All combinations. Only a limited number of fields can be updated once a record has been created.

See related topics...

Application type maintenance overview

To define the default verification items for an application type

To define the default status progression reason codes for an application type

To create a new enquiry failure rule for an application type

To add an allocations list to an application type

To add a functional unit to an application type

To assign a communication definition to an application type