Hi
I have a problem using Timestamp login. I want to prevent users logging into business objects between 8.00pm to 4.00am everyday. I tried to use timestamp login. I can set the time the users are allowed to login but I want Business Objects to automativally change the date to next day with each new date. Once I create a timestamp, the users are allowed to login between the start and End date.
The second problem is if the users are already logged in by the time the users are prevented to log then they are allowed to continue to log and do their work.
I am not familiar with scripting, but I would like to know if scripting is a solution to the problem.
In essence we want to prevent users working between 8.00pm to 4.00am to build some extract tables of the database.
For part 1 you will have to create 5 login times for a user. Monday 8-4, Tuesday 8-4, Wednesday 8-4, etc…
Part 2: There is nothing you can really do about this unless you force all connections off at a certain time or use a script to kill sessions. This means that you will have to use the advanced login feature to give each user a unique id (since you will undoubtedly want some people to be able to run jobs after 4pm).
If you use DocAgent, then DA is running a job under that users login. If you have your database killing all jobs by that person, then they will not be able to use DAS (and so, BO allows jobs to continue to run AFTER there login time). BO also does not check back with the repository to see if a user is exceeding their work time. The timestamp only prevents logins.
You would have to find a way to force users to have to log back in after inactive intervals, or throughout the day to be able to force them off the system.
I believe there is an enhancement request for WORKDAYS so you can set Start and Enddate and just select Workdays (which would Entail Monday-Friday). Nothing (that I know of) is in the works to force people out of BO.