OBJ_M_TIMESTAMP
This table defines time constraints for user login or for Broadcast Agent actions.
Name | Null ? | Type | Values |
M_TMS_N_ID | NOT NULL | int10 | Timestamp identifier, generated with the "MAGIC_ID" mechanism. |
M_TMS_N_ENTITYTYPE | NOT NULL | int10 |
Contains the type of entity the timestamp is used for: BOSTET_UNDEFINED
= 0;
undefined |
M_TMS_N_ENTITYID | NOT NULL | int10 | Pointer to the OBJ_M_ACTORLINK table through the M_ACTL_N_ID field. |
M_TMS_N_BEGINTIME | int10 | Starting time, from which the user can log in (in the date format) | |
M_TMS_N_ENDTIME | int10 | Ending time until which the user can log in (in the date format) | |
M_TMS_N_REPVALUE | NOT NULL | int10 | "Repeat value": this is the periodicity of an action to be repeated (e.g. permission to log in every year...). See exemple after table... |
M_TMS_N_REPUNIT | NOT NULL | int10 |
Type of the period above : HOUR:
10
<unused> |
M_TMS_N_DURREPVAL | NOT NULL | int10 | "Repeat duration value": this is the duration of the permission (e.g. permission given every year for 2 weeks). See example after table. |
M_TMS_N_DURREPUNIT | NOT NULL | int10 | Type of the repeat duration (e.g. permission lasts for one week). Same values as M_TMS_N_REPUNIT above. |
M_TMS_N_OFFREPVAL | NOT NULL | int10 | "Repeat offset value": this is the starting date of the permission given repeatedly (e.g. permission given every year for 2 weeks, starting the 45th day (of the year)). See example after table. |
M_TMS_N_OFFREPUNIT | NOT NULL | int10 | Type of the offset (e.g. the permission holds for the 4th week). Same values as M_TMS_N_REPUNIT above. |
M_TMS_N_LAD | NOT NULL | int10 | Last Action Date |
M_TMS_N_LAT | NOT NULL | int10 | Last Action Type |
How are timestamps working?
When a month is selected in the ‘How’ combo box:
Repvalue |
Repunit |
Durrepval |
Durrepunit |
Offrepval |
Offrepunit |
|
January |
1 |
50 |
1 |
40 |
0 |
40 |
February |
1 |
50 |
1 |
40 |
1 |
40 |
… |
1 |
50 |
1 |
40 |
… |
40 |
December |
1 |
50 |
1 |
40 |
11 |
40 |
This
can be also explained as:
every 1 YEAR,
( for one year because Repunit = 50)
give permission for 1 whole
MONTH,
( for one month because Durepunit = 40)
starting the nth month
(where n=Offrepval+1, and applied to month because Offrepunit = 40)
OR
every M_TMS_N_REPVALUE
M_TMS_REPUNIT,
give
permission for M_TMS_N_DUREPVAL whole M_TMS_DUREPUNIT,
starting
the (M_TMS_N_OFFREPVAL +1)th
M_TMS_N_OFFREPUNIT
When a day of the week is selected in the ‘How’ combo box:
|
Repvalue |
Repunit |
Durrepval |
Durrepunit |
Offrepval |
Offrepunit |
Monday |
1 |
30 |
1 |
20 |
0 |
20 |
Tuesday |
1 |
30 |
1 |
20 |
1 |
20 |
… |
1 |
30 |
1 |
20 |
… |
20 |
Sunday |
1 |
30 |
1 |
20 |
6 |
20 |
Once
again, this can be also explained as:
every 1 WEEK,
( for one week because Repunit = 30)
give permission for 1 whole DAY,
( for one day because Durepunit = 20)
starting the nth DAY
(where n=Offrepval+1, and applied to day because Offrepunit = 20)
OR
every M_TMS_N_REPVALUE
M_TMS_REPUNIT,
give
permission for M_TMS_N_DUREPVAL whole M_TMS_DUREPUNIT,
starting
the (M_TMS_N_OFFREPVAL +1)th
M_TMS_N_OFFREPUNIT
When ‘Last day of the month’ or ’First day of the month’ is selected in the ‘How’ combo box:
|
Repvalue |
Repunit |
Durrepval |
Durrepunit |
Offrepval |
Offrepunit |
First day of the month |
1 |
40 |
1 |
20 |
0 |
20 |
Last day of the month |
1 |
40 |
1 |
20 |
-1 |
20 |
This
one too can be explained as:
every 1 MONTH,
( for one month because Repunit = 40)
give permission for 1 whole DAY,
( for one day because Durepunit = 20)
starting the nth DAY
(where n=Offrepval+1, and applied to day because Offrepunit = 20)
OR
every M_TMS_N_REPVALUE
M_TMS_REPUNIT,
give
permission for M_TMS_N_DUREPVAL whole M_TMS_DUREPUNIT,
starting
the (M_TMS_N_OFFREPVAL +1)th
M_TMS_N_OFFRELUNIT