The Personal Weekly app relies on several configuration dependencies to determine which Daily Diary templates are available and which users are permitted to create forms.
These dependencies control both the templates that appear in app settings and the templates available to individual users.
| | |
|---|
| 1 | Template must be ACTIVE | Templates where Disable is enabled will be excluded from the template selection list. |
| 2 | Template must not be in ARCHIVED form group | Templates located in a form group called ARCHIVE are automatically excluded. |
| 3 | Template must be identified as a Daily Diary template | The Personal Weekly app identifies valid templates using the following field: This hidden system field is used by the application to recognise templates that represent Daily Diary forms. Templates without this field or where the value differs will not appear in the settings list. |
| 4 | Template must exist in the Forms template table | The template must exist in the Forms.templates table in Upvise. Templates created incorrectly or partially imported may not appear in the selection list. |
| 5 | Template name must be unique | Template names should be unique. The Personal Weekly app may reference templates by name if the template ID is not stored in configuration. Duplicate template names can lead to incorrect template selection or unexpected behaviour. |
| 6 | Labour Hours form Field | The Labour Hours Field must exist on the Daily Diary template for the app to work as intended. This field can be hidden in the daily diary, but not deleted. |
| 7 | Daily Diary Date field | Template should contain the Diary Date field for correct date filtering in the weekly view. |