The appointments action type displays the following additional fields on the data entry screen;
The Court Attendance action type is designed to record each time a service goes to a court or tribunal.
A new Action can be created for each court / tribunal, or if detail is required, this action could be created for each day at court / tribunal – particularly where file notes are recorded each day within the Description text box.
Court Attendance is also designed for recording each court appearance where the court changes for an appeal etc. The idea is that at a minimum a new action would be created for each appearance at each court or tribunal. To achieve this the field “Court Type” should be used. “Court Type” is designed to show exactly which court / tribunal the client is at. This field is populated with generic courts and tribunals, but is also designed to be customised to add the named courts and tribunals relevant to your Centre, or to ‘hide’ those that are not relevant. Speak to your CLASS administrator if this is required.
This Action Type displays the following fields in addition to the usual Action fields:
Note about Court Attendances Action Type dates:
In general, attendance date works like due date in regards to appearing on critical dates list. If you remove an attendance date you may need to trigger a due date by adding a reminder date instead.
Currently a court attendance type may appear in Critical Dates lists without a date in the ‘due date’ field. This is because attendance date is being used instead of due date.
Court Attendances action type
The court attendances action type displays the following additional fields;
To all other action types
To the generic action types.
Some action types can be hidden from data entry, if that type is not required by your centre.
New action types can be created if your centre has a specific need for an action type not already available. You should assess whether a due date field is required and copy your new type from a similar existing type.
Customising action types in this way is covered in the Admin manual – Action Types – Managing
These are the action types that have a due date – and therefore will appear in critical dates lists.
NB. It is currently (at Sept 2017) possible to trick the system into adding due date for other actions but not recommended. This can occur when the action starts off as one type of action, and the user adds a due date and then changes the type. If you see non-due-date type actions in your lists, this may be how they came about.
The following fields are available for all action types.
More information about Actions Fields
If you want to record a limitation issue there is an action type specifically for that purpose.
The main reason you would create an action of type limitation issues is to record that there is a limitation issue and that the client was advised.
These two fields appear on the data entry in actions when limitation issue is selected as the type. It is the only action type that has these two fields.
KEEP IN MIND: Reminders and critical dates are handled as per all other actions types
NB. At time of writing, CLC’s Australia were considering a separate print template for limitation issues. ie if you don’t see the fields required you may need to choose the correct printout template at the time of printing.
Extra fields to all other action types
Extra fields to generic action type
The reminder action type displays the following additional fields on the data entry screen
This is a type of action and not to be confused with email Reminders functionality which are triggered by the reminder date field.