| Excerpt |
|---|
This article describes how to set up a Customized Topics data together with a Crew List View to help users to follow up persons on Sick Leave. |
Description
In many countries the government tasks the Employer to follow-up employees that are on Sick Leave. In this article we describe how to set up a Data group in Customized Topics, and how to get the information out into a Crew List View.
After the set up is completed the user should have a Data group where information about the Sick Leave can be registered, and with a Crew List view assisting in following up the sick persons on given due dates.
Customized Topic and fields
Full manual on how to set up and use Customized Topics can be found in this article, Customized Topics.
Below is a sample on the set up of the most used fields.
Editor Form Layout
Under the Editor Form Layout we have used the Customize tool to group fields and to give the groups a name
Crew List View
A Crew List View with the following fields and information is included. This Crew List View will pick up information for any person where a record of Sick Leave has been added.
| Column No | Column Name | Description |
|---|---|---|
| 1 | PIN | |
| 2 | Name | |
| 3 | Sick Leave From | The date is fetched from the field Sick Leave From in the Sick Leave customized Data Group |
| 4 | Sick Leave To | The date is fetched from the field Sick Leave To in the Sick Leave customized Data Group |
| 5 | First Response | The field indicates with-in, which date the nearest leader should make the First Response. In this view, the date is auto-calculated to be 3 days after the Sick Leave From date. When a date is entered in the First Response Performed, this field will become empty, |
| 6 | First Response Performed | The date is fetched from the field First Response Performed in the Sick Leave customized Data Group |
| 7 | Notes from First Response | The notes are fetched from the field Notes from First Response in the Sick Leave customized Data Group |
| 8 | Follow-up Plan | The field indicates with-in, which date the nearest leader should make the Follow-up Plan. In this view, the date is auto-calculated to be 28 days after the Sick Leave From date. When a date is entered in the Follow-up Plan Created, this field will become empty, |
| 9 | Follow-up Plan Created | The date is fetched from the field Follow-up Plan Created in the Sick Leave customized Data Group |
| 10 | Notes from Follow-up Plan | The notes are fetched from the field Notes from Follow-up Plan in the Sick Leave customized Data Group |
| 11 | URL to Follow Up Plan | The URL is fetched from the field URL to Follow Up Plan in the Sick Leave customized Data Group |
| 12 | Dialogue Meeting I NAV | The field indicates with-in, which date the Dialogue Meeting with NAV should be held. |
| 13 | Notes from Dialogue Meeting I | The notes are fetched from the field Notes from Dialogue Meeting I in the Sick Leave customized Data Group |
| 14 | Info to NAV | The data in this field is fetched from the field Info to NAV in the Sick Leave customized Data Group |
| 15 | URL to NAV info | The URL is fetched from the field URL to NAV info in the Sick Leave customized Data Group |
| 16 | Dialogue Meeting II NAV | The field indicates with-in, which date the Dialogue Meeting with NAV should be held. In this view, the date is auto-calculated to be 182 days after the Sick Leave From date. |
| 17 | Follow-up II" | The field indicates with-in, which date the Dialogue Meeting with NAV should be held. In this view, the date is auto-calculated to be 365 days after the Sick Leave From date. |
| 18 | Additional Notes | The notes are fetched from the field Additional Notes in the Sick Leave customized Data Group |
| 19 | Other Enclosures I | The URL is fetched from the field Other Enclosures I in the Sick Leave customized Data Group |
| 20 | Other Enclosures II | The URL is fetched from the field Other Enclosures II in the Sick Leave customized Data Group |
| 21 | Other Enclosures III | The URL is fetched from the field Other Enclosures III in the Sick Leave customized Data Group |
| 22 | Fit for Duty From | The date is fetched from the field Fit for Duty From in the Sick Leave customized Data Group |
| 23 | NUMORGID | Mandatory by the system for all Crew List Views |
| 24 | EMPLOYMENTSTARTDATE | Mandatory by the system for all Crew List Views |
| 25 | EMPLOYMENTENDDATE | Mandatory by the system for all Crew List Views |
High-lighting expiry dates
In the Crew List View, it is possible to set up color coding for fields that indicates a deadline. In this sample, the fields "Follow-up Plan", "Dialogue Meeting I", "Dialogue Meeting II NAV" and "Follow-up II" is set to have the cell display color as follows:
Cell will display in yellow when it is 7 days until the date in the field.
Cell will display in red when it is 1 day until the date in the field and until the Grey color field kicks-in.
Cell will display in grey when it is 365 days after the date in the field.
These days are customizable and can be set in General Codes | Crew List | Crew List View and by going in to the specific Crew List View.
SQL Statement
CREATE VIEW dbo.PW001SRV12as
select p01.Pin,
p01.Name,
u02.UField1 AS "Sick Leave From",
u02.UField2 AS "Sick Leave To",
Case when u02.UField3 is null then Dateadd (Day,3,u02.UField1) else null end AS "First Response",
u02.UField3 AS "First Response Performed",
u02.UField4 AS "Notes from First Response",
Case when u02.UField5 is null then Dateadd (Day,28,u02.UField1) else null end AS "Follow-up Plan",
u02.UField5 AS "Follow-up Plan Created",
u02.UField6 AS "Notes from Follow-up Plan",
u02.UField7 AS "URL to Follow Up Plan",
Dateadd (Day,49,u02.UField1) AS "Dialogue Meeting I NAV",
u02.UField8 AS "Notes from Dialogue Meeting I",
Dateadd (Day,63,u02.UField1) "Info to NAV",
u02.UField9 AS "URL to NAV info",
Dateadd (Day,182,u02.UField1) AS "Dialogue Meeting II NAV",
Dateadd (Day,365,u02.UField1) AS "Follow-up II",
u02.UField10 AS "Additional Notes",
u02.UField11 AS "Other Enclosures I",
u02.UField12 AS "Other Enclosures II",
u02.UField13 AS "Other Enclosures III",
u02.UField14 AS "Fit for Duty From",
P01.CLIENT NUMORGID,
P01.EMPLOYMENTSTARTDATE,
P01.EMPLOYMENTENDDATE
from pw001p01 p01
join pw001u23 u02 on u02.pin = p01.pin