Example #2: The Timesheet Application
Analysis and Design
In our virtual company, an employee is required to fill out a weekly timesheet – see Figure 114. Their manager will either approve the hours worked for that week or reject the timesheet. If a timesheet is rejected the employee will need to amend their hours and resubmit it for approval.
|
Figure 114. |
Step 1: Design User Roles:
The first step is to work out how many different roles are at work here in our process;
- The Employee
The employee that is submitting the timesheet.
- The Employee’s Manager
The manager of the employee approves the timesheet.
So, there are two different roles in this work process.
Step 1: Design User Roles – Summary:
For this example, the need for two distinct user roles has been identified; Employee and Manager.
Step 2: Design Forms:
The next step in the analysis phase is to work out what the screens in our final system will look like. As all the relevant information in our process is represented on the existing timesheet itself, this will be the model for our forms.
Step 2: Design Forms – Summary:
For this example, the need for three screens has been identified. All the employees in our virtual company will be able to create a timesheet. Only managers will be able to approve or reject those timesheets.
Step 3: Design Workflow:
The final step in our analysis phase is to define the workflow itself.
In this example, the workflow is as follows:
|
Figure 115. |
Step 3: Design Workflow – Summary:
For this example, the workflow is a loop with an ‘Hours Approved?’ decision. If the decision is ‘Yes’ the workflow ends and becomes locked. If ‘No’, the workflow iterates through another pass allowing the employee to make changes to the timesheet.
This completes the analysis phase for the Timesheet system.
Implementation
Step 4: Implement User Types and Users:
For this example, the existing ‘Employee’ and ‘Manager’ user types from the previous example will be used. However, the ‘Employee’ user type needs some additional permissions:
|
To change the existing properties of the ‘Employee’ user type, click on ‘Employee’ and select ‘Properties’ in the context-sensitive menu that appears: |
Figure 116. |
|
|
|
|
The ‘User Types’ maintenance screen will appear in the right-hand pane of the browser. Add ‘Task List’ and ‘Item List’ permissions to the existing ‘Create New Instances’ permission by clicking on the checkboxes.
Click on the ‘Submit’ button.
Note: ‘Task List’ and ‘Items List’ will allow in-process workflows to be shown to the user. |
Figure 117. |
The access permissions already granted to the ‘Manager’ user type are adequate for this new example and remain unchanged. The users ‘Chris’ and ‘Paul’ will be reused for this example in their respective roles of ‘Employee’ and ‘Manager’.
Step 4: Implement User Types and Users – Summary:
At this point, the two user types have been defined and a single user exists under each of those types.
Note:
See previous example ‘Leave Form Application’ for a detailed description of adding user types and users.
Step 5: Implement Forms:
|
Select Admin → Forms from the top menu bar: |
Figure 118. |
|
|
|
|
Kontinuum’s form maintenance section will be displayed. Click on the ‘Forms’ node in the tree control in the left-hand pane of the browser. Select ‘Add Folder’ in the context-sensitive menu that appears: |
Figure 119. |
|
The ‘Folders’ maintenance screen will appear in the right-hand pane of the browser. Fill out the required fields and click on the ‘Submit’ button. |
Figure 120. |
|
Click on the newly created ‘Timesheets’ folder node in the tree control in the left-hand pane of the browser. Select ‘Add Folder’ in the context-sensitive menu that appears: |
Figure 121. |
Note:
The timesheet application requires three simple forms for the maintenance of ‘look-up codes’ for projects, activities and time types. These forms will be grouped under the sub-folder ‘Codes Maintenance’ within the main folder ‘Timesheets’.
|
The ‘Folders’ maintenance screen will appear in the right-hand pane of the browser. Fill out the required fields and click on the ‘Submit’ button. |
Figure 122. |
Under this folder, create a form called ‘Project Code Maintenance’ using the attributes listed in the tables below:
Form Name: Project Code Maintenance
Form Database Name: ProjectCodeMaintenance
Subform Details:
|
Subform |
Type |
Subform Name |
Subform Order |
Appear In Column |
Use data from Auxiliary Form |
HideDeleteButton |
Uneditable |
|
|
|
|
|
|
|
|
|
|
Project Code Details |
One |
ProjectCodeDetails |
1 |
1 |
|
|
|
Question Details:
|
Question |
Type |
Name |
PK |
Show In Task List |
Question Order |
Appear Column |
Column Width |
Data Type |
Size |
Input Mask |
Pixels from Left |
Pixels from Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project Code |
Text Box |
ProjectCode |
Yes |
Yes |
1 |
1 |
5 |
VARCHAR |
5 |
None |
|
|
|
Project Description |
Text Box |
ProjectDescription |
No |
Yes |
2 |
1 |
|
VARCHAR |
50 |
None |
|
|
Note:
See previous example ‘Leave Form Application’ for a detailed description of adding forms, subforms and questions.
Under the ‘Codes Maintenance’ folder, create two more forms called ‘Activity Code Maintenance’ and ‘Time Type Code Maintenance’ using the attributes listed in the tables below:
Form Name: Activity Code Maintenance
Form Database Name: ActivityCodeMaintenance
Subform Details:
|
Subform |
Type |
Subform Name |
Subform Order |
Appear In Column |
Use data from Auxiliary Form |
HideDeleteButton |
Uneditable |
|
|
|
|
|
|
|
|
|
|
Activity Code Details |
One |
ActivityCodeDetails |
1 |
1 |
|
|
|
Question Details:
|
Question |
Type |
Name |
PK |
Show In Task List |
Question Order |
Appear Column |
Column Width |
Data Type |
Size |
Input Mask |
Pixels from Left |
Pixels from Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Activity Code |
Text Box |
Activity Code |
Yes |
Yes |
1 |
1 |
5 |
VARCHAR |
5 |
None |
|
|
|
Activity Description |
Text Box |
ActivityDescription |
No |
Yes |
2 |
1 |
|
VARCHAR |
50 |
None |
|
|
Form Name: Time Type Code Maintenance
Form Database Name: TimeTypeCodeMaintenance
Subform Details:
|
Subform |
Type |
Subform Name |
Subform Order |
Appear In Column |
Use data from Auxiliary Form |
HideDeleteButton |
Uneditable |
|
|
|
|
|
|
|
|
|
|
Time Type Code Details |
One |
TimeTypeCodeDetails |
1 |
1 |
|
|
|
Question Details:
|
Question |
Type |
Name |
PK |
Show In Task List |
Question Order |
Appear Column |
Column Width |
Data Type |
Size |
Input Mask |
Pixels from Left |
Pixels from Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Time Type Code |
Text Box |
TimeTypeCode |
Yes |
Yes |
1 |
1 |
5 |
VARCHAR |
5 |
None |
|
|
|
Time Type Description |
Text Box |
TimeTypeDescription |
No |
Yes |
2 |
1 |
|
VARCHAR |
50 |
None |
|
|
|
At this point, the ‘look-up code’ maintenance screens have been completed and the forms designer tree control should look similar to Figure 123: |
Figure 123. |
Under the ‘Timesheets’ folder, create the three main forms using the attributes listed in the tables below:
Form Name: Timesheet Header
Form Database Name: TimesheetHeader
Subform Details:
|
Subform |
Type |
Subform Name |
Subform Order |
Appear In Column |
Use data from Auxiliary Form |
HideDeleteButton |
Uneditable |
|
|
|
|
|
|
|
|
|
|
Header |
One |
Header |
1 |
1 |
|
|
|
Question Details:
|
Question |
Type |
Name |
PK |
Show In Task List |
Question Order |
Appear Column |
Column Width |
Data Type |
Size |
Input Mask |
Pixels from Left |
Pixels from Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Employee Name |
Text Box |
EmployeeName |
Yes |
Yes |
1 |
1 |
50 |
VARCHAR |
50 |
None |
|
|
|
Week Ending |
Input Mask Box Calendar |
WeekEnding |
Yes |
Yes |
2 |
1 |
|
DATETIME |
|
Australian Date Format |
|
|
Question Rules:
|
Question Name |
Default Value / Selection |
Required |
Uneditable |
|
|
|
|
|
|
EmployeeName |
@@User.FullName |
1 |
1 |
|
WeekEnding |
|
1 |
|
Form Name: Timesheet Line Items
Form Database Name: TimesheetLineItems
Subform Details:
|
Subform |
Type |
Subform Name |
Subform Order |
Appear In Column |
Use data from Auxiliary Form |
HideDeleteButton |
Uneditable |
|
|
|
|
|
|
|
|
|
|
Header |
One |
Header |
1 |
1 |
TimesheetHeader |
|
|
|
Totals |
One |
Totals |
2 |
1 |
|
1 |
|
Question Details:
|
Question |
Type |
Name |
PK |
Show In Task List |
Question Order |
Appear Column |
Column Width |
Data Type |
Size |
Input Mask |
Pixels from Left |
Pixels from Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Total Hours: MON |
Label Not Stored |
Day1Total |
No |
No |
3 |
2 |
|
|
|
None |
303 |
87 |
|
TUE |
Label Not Stored |
Day2Total |
No |
No |
3 |
2 |
|
|
|
None |
436 |
87 |
|
WED |
Label Not Stored |
Day3Total |
No |
No |
3 |
2 |
|
|
|
None |
492 |
87 |
|
THU |
Label Not Stored |
Day4Total |
No |
No |
3 |
2 |
|
|
|
None |
549 |
87 |
|
FRI |
Label Not Stored |
Day5Total |
No |
No |
3 |
2 |
|
|
|
None |
609 |
87 |
|
SAT |
Label Not Stored |
Day6Total |
No |
No |
3 |
2 |
|
|
|
None |
665 |
87 |
|
SUN |
Label Not Stored |
Day7Total |
No |
No |
3 |
2 |
|
|
|
None |
721 |
87 |
|
WEEK |
Label Not Stored |
WeekTotal |
No |
No |
3 |
2 |
|
|
|
None |
800 |
87 |
Question Rules:
|
Question Name |
Default Value / Selection |
Required |
Uneditable |
|
|
|
|
|
|
Day1Total |
eval{agg{sum,@@Form.LineItem.All.Monday}} |
|
|
|
Day2Total |
eval{agg{sum,@@Form.LineItem.All.Tuesday}} |
|
|
|
Day3Total |
eval{agg{sum,@@Form.LineItem.All.Wednesday}} |
|
|
|
Day4Total |
eval{agg{sum,@@Form.LineItem.All.Thursday}} |
|
|
|
Day5Total |
eval{agg{sum,@@Form.LineItem.All.Friday}} |
|
|
|
Day6Total |
eval{agg{sum,@@Form.LineItem.All.Saturday}} |
|
|
|
Day7Total |
eval{agg{sum,@@Form.LineItem.All.Sunday}} |
|
|
|
WeekTotal |
eval{agg{sum,@@Form.LineItem.All.Monday} + agg{sum,@@Form.LineItem.All.Tuesday} + agg{sum,@@Form.LineItem.All.Wednesday} + agg{sum,@@Form.LineItem.All.Thursday} + agg{sum,@@Form.LineItem.All.Friday} + agg{sum,@@Form.LineItem.All.Saturday} + agg{sum,@@Form.LineItem.All.Sunday}} |
|
|
Subform Details:
|
Subform |
Type |
Subform Name |
Subform Order |
Appear In Column |
Use data from Auxiliary Form |
HideDeleteButton |
Uneditable |
|
|
|
|
|
|
|
|
|
|
Line Item |
Growing |
LineItem |
3 |
1 |
|
|
|
Question Details:
|
Question |
Type |
Name |
PK |
Show In Task List |
Question Order |
Appear Column |
Column Width |
Data Type |
Size |
Input Mask |
Pixels from Left |
Pixels from Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project |
List Box |
Project |
No |
No |
1 |
1 |
20 |
VARCHAR |
5 |
None |
|
|
|
Activity |
List Box |
Activity |
No |
No |
2 |
1 |
20 |
VARCHAR |
5 |
None |
|
|
|
Time Type |
List Box |
TimeType |
No |
No |
3 |
1 |
20 |
VARCHAR |
5 |
None |
|
|
|
MON |
Text Box |
Monday |
No |
No |
4 |
2 |
5 |
REAL |
|
None |
|
|
|
TUE |
Text Box |
Tuesday |
No |
No |
5 |
2 |
5 |
REAL |
|
None |
|
|
|
WED |
Text Box |
Wednesday |
No |
No |
6 |
2 |
5 |
REAL |
|
None |
|
|
|
THU |
Text Box |
Thursday |
No |
No |
7 |
2 |
5 |
REAL |
|
None |
|
|
|
FRI |
Text Box |
Friday |
No |
No |
8 |
2 |
5 |
REAL |
|
None |
|
|
|
SAT |
Text Box |
Saturday |
No |
No |
9 |
2 |
5 |
REAL |
|
None |
|
|
|
SUN |
Text Box |
Sunday |
No |
No |
10 |
2 |
5 |
REAL |
|
None |
|
|
|
Comments |
Text Box |
Comments |
No |
No |
11 |
3 |
20 |
VARCHAR |
100 |
None |
|
|
Question Rules:
|
Question Name |
Default Value / Selection |
Required |
Uneditable |
|
|
|
|
|
|
Project |
sqlset{select ProjectDescription, ProjectCode from ProjectCodes1v1.dbo.ProjectCodeDetails} |
1 |
|
|
Activity |
sqlset{select ActivityDescription, ActivityCode from ActivityCodes1v1.dbo.ActivityCodeDetails} |
1 |
|
|
Time Type |
sqlset{select TimeTypeDescription, TimeTypeCode from TimeTypeCodes1v1.dbo.TimeTypeCodeDetails} |
1 |
|
|
Monday |
0.0 |
|
|
|
Tuesday |
0.0 |
|
|
|
Wednesday |
0.0 |
|
|
|
Thursday |
0.0 |
|
|
|
Friday |
0.0 |
|
|
|
Saturday |
0.0 |
|
|
|
Sunday |
0.0 |
|
|
Form Name: Timesheet Approval
Form Database Name: TimesheetApproval
Subform Details:
|
Subform |
Type |
Subform Name |
Subform Order |
Appear In Column |
Use data from Auxiliary Form |
HideDeleteButton |
Uneditable |
|
|
|
|
|
|
|
|
|
|
Manager's Approval |
One |
ManagersApproval |
1 |
1 |
|
|
|
Question Details:
|
Question |
Type |
Name |
PK |
Show In Task List |
Question Order |
Appear Column |
Column Width |
Data Type |
Size |
Input Mask |
Pixels from Left |
Pixels from Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hours Approved? |
Radio Buttons |
HoursApproved |
No |
No |
1 |
1 |
|
BIT |
|
None |
|
|
Question Rules:
|
Question Name |
Default Value / Selection |
Required |
Uneditable |
|
|
|
|
|
|
HoursApproved |
[Yes,,1][No,,0] |
|
|
Subform Details:
|
Subform |
Type |
Subform Name |
Subform Order |
Appear In Column |
Use data from Auxiliary Form |
HideDeleteButton |
Uneditable |
|
|
|
|
|
|
|
|
|
|
Header Details |
Side Bar |
HeaderDetails |
2 |
1 |
|
1 |
|
Question Details:
|
Question |
Type |
Name |
PK |
Show In Task List |
Question Order |
Appear Column |
Column Width |
Data Type |
Size |
Input Mask |
Pixels from Left |
Pixels from Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Employee Name |
Side Bar |
hdEmployeeName |
No |
No |
2 |
1 |
|
|
|
None |
|
|
|
Week Ending |
Side Bar |
hdWeekEnding |
No |
No |
2 |
1 |
|
|
|
Australian Date Format |
|
|
|
Weekly Hours Total |
Side Bar |
WeeklyHoursTotal |
No |
No |
2 |
1 |
|
|
|
None |
|
|
Question Rules:
|
Question Name |
Default Value / Selection |
Required |
Uneditable |
|
|
|
|
|
|
hdEmployeeName |
@@Session.EmployeeName |
|
|
|
hdWeekEnding |
@@Session.WeekEnding |
|
|
|
WeeklyHoursTotal |
sqlset{select sum(Monday) + sum(Tuesday) + sum(Wednesday) + sum(Thursday) + sum(Friday) + sum(Saturday) + sum(Sunday) as WeeklyHoursTotal from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding'} |
|
|
Subform Details:
|
Subform |
Type |
Subform Name |
Subform Order |
Appear In Column |
Use data from Auxiliary Form |
HideDeleteButton |
Uneditable |
|
|
|
|
|
|
|
|
|
|
Line Item |
Growing |
LineItem |
3 |
1 |
TimesheetLineItems |
1 |
1 |
|
Hours By Project |
Side Bar |
HoursByProject |
4 |
1 |
|
1 |
|
Question Details:
|
Question |
Type |
Name |
PK |
Show In Task List |
Question Order |
Appear Column |
Column Width |
Data Type |
Size |
Input Mask |
Pixels from Left |
Pixels from Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project |
Side Bar |
Project |
No |
No |
1 |
1 |
|
|
|
None |
|
|
|
Monday |
Side Bar |
Monday |
No |
No |
2 |
1 |
|
|
|
None |
|
|
|
Tuesday |
Side Bar |
Tuesday |
No |
No |
3 |
1 |
|
|
|
None |
|
|
|
Wednesday |
Side Bar |
Wednesday |
No |
No |
4 |
1 |
|
|
|
None |
|
|
|
Thursday |
Side Bar |
Thursday |
No |
No |
5 |
1 |
|
|
|
None |
|
|
|
Friday |
Side Bar |
Friday |
No |
No |
6 |
1 |
|
|
|
None |
|
|
|
Saturday |
Side Bar |
Saturday |
No |
No |
7 |
1 |
|
|
|
None |
|
|
|
Sunday |
Side Bar |
Sunday |
No |
No |
8 |
1 |
|
|
|
None |
|
|
Question Rules:
|
Question Name |
Default Value / Selection |
Required |
Uneditable |
|
|
|
|
|
|
Project |
sqlset{select (select ProjectDescription from ProjectCodes1v1.dbo.ProjectCodeDetails where ProjectCode = li.Project) as Project from Timesheets1v1.dbo.LineItem li where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Project} |
|
|
|
Monday |
sqlset{select sum(Monday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Project} |
|
|
|
Tuesday |
sqlset{select sum(Tuesday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Project} |
|
|
|
Wednesday |
sqlset{select sum(Wednesday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Project} |
|
|
|
Thursday |
sqlset{select sum(Thursday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Project} |
|
|
|
Friday |
sqlset{select sum(Friday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Project} |
|
|
|
Saturday |
sqlset{select sum(Saturday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Project} |
|
|
|
Sunday |
sqlset{select sum(Sunday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Project} |
|
|
Subform Details:
|
Subform |
Type |
Subform Name |
Subform Order |
Appear In Column |
Use data from Auxiliary Form |
HideDeleteButton |
Uneditable |
|
|
|
|
|
|
|
|
|
|
Hours By Activity |
Side Bar |
HoursByActivity |
5 |
1 |
|
1 |
|
Question Details:
|
Question |
Type |
Name |
PK |
Show In Task List |
Question Order |
Appear Column |
Column Width |
Data Type |
Size |
Input Mask |
Pixels from Left |
Pixels from Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Activity |
Side Bar |
Activity |
No |
No |
1 |
1 |
|
|
|
None |
|
|
|
Monday |
Side Bar |
Monday |
No |
No |
2 |
1 |
|
|
|
None |
|
|
|
Tuesday |
Side Bar |
Tuesday |
No |
No |
3 |
1 |
|
|
|
None |
|
|
|
Wednesday |
Side Bar |
Wednesday |
No |
No |
4 |
1 |
|
|
|
None |
|
|
|
Thursday |
Side Bar |
Thursday |
No |
No |
5 |
1 |
|
|
|
None |
|
|
|
Friday |
Side Bar |
Friday |
No |
No |
6 |
1 |
|
|
|
None |
|
|
|
Saturday |
Side Bar |
Saturday |
No |
No |
7 |
1 |
|
|
|
None |
|
|
|
Sunday |
Side Bar |
Sunday |
No |
No |
8 |
1 |
|
|
|
None |
|
|
Question Rules:
|
Question Name |
Default Value / Selection |
Required |
Uneditable |
|
|
|
|
|
|
Activity |
sqlset{select (select ActivityDescription from ActivityCodes1v1.dbo.ActivityCodeDetails where ActivityCode = li.Activity) as Activity from Timesheets1v1.dbo.LineItem li where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Activity} |
|
|
|
Monday |
sqlset{select sum(Monday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Activity} |
|
|
|
Tuesday |
sqlset{select sum(Tuesday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Activity} |
|
|
|
Wednesday |
sqlset{select sum(Wednesday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Activity} |
|
|
|
Thursday |
sqlset{select sum(Thursday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Activity} |
|
|
|
Friday |
sqlset{select sum(Friday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Activity} |
|
|
|
Saturday |
sqlset{select sum(Saturday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Activity} |
|
|
|
Sunday |
sqlset{select sum(Sunday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by Activity} |
|
|
Subform Details:
|
Subform |
Type |
Subform Name |
Subform Order |
Appear In Column |
Use data from Auxiliary Form |
HideDeleteButton |
Uneditable |
|
|
|
|
|
|
|
|
|
|
Hours By Time Type |
Side Bar |
HoursByTimeType |
6 |
1 |
|
1 |
|
Question Details:
|
Question |
Type |
Name |
PK |
Show In Task List |
Question Order |
Appear Column |
Column Width |
Data Type |
Size |
Input Mask |
Pixels from Left |
Pixels from Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Time Type |
Side Bar |
TimeType |
No |
No |
1 |
1 |
|
|
|
None |
|
|
|
Monday |
Side Bar |
Monday |
No |
No |
2 |
1 |
|
|
|
None |
|
|
|
Tuesday |
Side Bar |
Tuesday |
No |
No |
3 |
1 |
|
|
|
None |
|
|
|
Wednesday |
Side Bar |
Wednesday |
No |
No |
4 |
1 |
|
|
|
None |
|
|
|
Thursday |
Side Bar |
Thursday |
No |
No |
5 |
1 |
|
|
|
None |
|
|
|
Friday |
Side Bar |
Friday |
No |
No |
6 |
1 |
|
|
|
None |
|
|
|
Saturday |
Side Bar |
Saturday |
No |
No |
7 |
1 |
|
|
|
None |
|
|
|
Sunday |
Side Bar |
Sunday |
No |
No |
8 |
1 |
|
|
|
None |
|
|
Question Rules:
|
Question Name |
Default Value / Selection |
Required |
Uneditable |
|
|
|
|
|
|
TimeType |
sqlset{select (select TimeTypeDescription from TimeTypeCodes1v1.dbo.TimeTypeCodeDetails where TimeTypeCode = li.TimeType) as TimeType from Timesheets1v1.dbo.LineItem li where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by TimeType} |
|
|
|
Monday |
sqlset{select sum(Monday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by TimeType} |
|
|
|
Tuesday |
sqlset{select sum(Tuesday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by TimeType} |
|
|
|
Wednesday |
sqlset{select sum(Wednesday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by TimeType} |
|
|
|
Thursday |
sqlset{select sum(Thursday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by TimeType} |
|
|
|
Friday |
sqlset{select sum(Friday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by TimeType} |
|
|
|
Saturday |
sqlset{select sum(Saturday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by TimeType} |
|
|
|
Sunday |
sqlset{select sum(Sunday) from Timesheets1v1.dbo.LineItem where EmployeeName = '@@Session.EmployeeName' and WeekEnding = '@@Session.WeekEnding' group by TimeType} |
|
|
Note:
See previous example ‘Leave Form Application’ for a detailed description of adding forms, subforms and questions.
|
The forms designer tree control should look similar to Figure 124 for the ‘Timesheet Header’ form: |
Figure 124. |
|
|
|
|
The forms designer tree control should look similar to Figure 125 for the ‘Timesheet Line Item’ form: |
Figure 125. |
|
|
|
|
The forms designer tree control should look similar to Figure 126 for the ‘Timesheet Line Item’ form: |
Figure 126. |
Step 5: Implement Forms – Summary:
At this point, six forms have been implemented. Three simple forms for look-up code maintenance and three forms for the main workflow.
Step 6: Implement Work Flow:
|
Select Admin → Work Flo from the top menu bar: |
Figure 127. |
|
|
|
|
Kontinuum’s work flo maintenance section will be displayed.
Click on the ‘Workflows’ node in the tree control in the left-hand pane of the browser. Select ‘Add Folder’ in the context-sensitive menu that appears: |
Figure 128. |
|
|
|
|
The ‘Workflow Folder’ maintenance screen will appear in the right-hand pane of the browser. Populate the fields as shown in Figure 129 and click on the ‘Submit’ button. |
Figure 129. |
Under this folder, create a workflow called ‘Project Codes’ using the attributes listed in the tables below:
Workflow Name: ProjectCodes
Database Name (Storage): ProjectCodes1v1
Add the ‘Manager’ user type to this workflow:
User Type: Manager
What can the User see: ALL
Design the workflow as follows:
Process Details:
|
X coordinate |
Y coordinate |
Display Name |
Process Name |
Gate Type |
Gate Name |
User Type Permissions |
|
|
|
|
|
|
|
|
|
1 |
1 |
Project Code Entry |
ProjectCodeEntry |
FORM |
ProjectCodeMaintenance |
Employee: DELETE, INSERT, UPDATE, VIEW |
|
2 |
1 |
wire |
wire |
STOP |
STOP |
|
Note:
See previous example ‘Leave Form Application’ for a detailed description of creating workflows.
Under the ‘Timesheets’ folder, create another two workflows called ‘Activity Codes’ and ‘Time Type Codes’ using the attributes listed in the tables below:
Workflow Name: ActivityCodes
Database Name (Storage): ActivityCodes1v1
Add the ‘Manager’ user type to this workflow:
User Type: Manager
What can the User see: ALL
Design the workflow as follows:
Process Details:
|
X coordinate |
Y coordinate |
Display Name |
Process Name |
|