Personal Housing Plans (PHPs) are comprised of a number of Actions. These Actions can be assigned to either the applicant or the organisation.
For an Action to be included in the PHP then the Personal housing plan action field must be set to Yes.
A PDF version of a Plan can be generated through the Case Comms centre. Information related to all PHP actions at that point in time will be merged into the PHP template and created as a document that can be viewed and printed if required.
Applicants can view all of their PHP actions on the Public Portal through their My Account page.
If an applicant has at least one PHP action associated with their Case then they will see the My Plan option on the public portal when they login.
The content of the Personal Housing Plan is made up of the Action data as well as any static content you wish to add to it. This can be configured for both the PDF version and the My Plan page on the public portal.
The Public Portal version of the plan is configured through the Website Administration menu option. In the Contents section there is a My personal housing plan page.
Each field can be switched on/off independently
The Case fields section allow the names of these fields to be changed if required.
Item |
Details |
Top contents |
Text is displayed at the top of the My Plan page and above the Case fields (if being displayed) |
Action contents |
Text is displayed above the list of Actions. |
Bottom contents |
Text is displayed underneath the list of Actions. |
The Personal Housing Plan wrapper is setup with special field codes to allow the PHP action information to be merged into the document.
These codes are used to determine which actions are displayed and what information related to each action is shown.
The field codes can be placed inside a table to allow the action information to be presented in an organised format.
Code |
Details |
Action.Name |
The contents of the Name of the action field |
Action.PublicInstruction |
The contents of the Instruction message to public field |
Action.PublicComment |
The contents of the Public comment field |
Action.Status |
The current state of the action |
Action.TargetDateTime |
The target date and time of the action |
Codes are also inserted at the start and end of the table to determine what selection of actions are to be displayed in the table.
Code |
Details |
TableStart:YourActionsCurrent + TableEnd:YourActionsCurrent |
Display all current actions that are assigned to the applicant |
TableStart:YourActionsAll + TableEnd:YourActionsAll |
Display all actions that are assigned to the applicant |
TableStart:OurActionsCurrent + TableEnd:OurActionsCurrent |
Display all current actions that are assigned to the organisation |
TableStart:OurActionsAll + TableEnd:OurActionsAll |
Display all actions that are assigned to the organisation |
The following example show how the codes are inserted into a table:
Action |
Due date |
Notes |
|
«TableStart:YourActionsAll» |
«Action.Name» «Action.PublicInstruction» |
«Action.Status» «Action.TargetDateTime» |
«Action.PublicComment» «TableEnd:YourActionsAll» |
The table will display all PHP actions that are assigned to the applicant regardless of being Active or Completed.
The Name and Public Instruction fields will be displayed in the Action column, the Status and Target Date in the Due Date column, and the Public Comments in the Notes column.