Forced redirect to a page or Portal bookmark?

I am thinking there are a number of ways to handle this...

1. Change your systems "portal role - home page"
2. If you have a link that associates use to get to Lawson ESS change that to have a direct link to the bookmark you want to open (https://www.lawsonguru.co...t/6137/Default.aspx)

There are probably a number of other solutions....

Joe,

We do this in order to prevent users from logging into the portal while we're performing any kind of maintenance. It's pretty simple and just requires the existence of a page called 'default.htm' in your \d$\Inetpub\wwwroot\webdocs\lawson\portal directory. If a page by this name exists, it is automatically displayed. Otherwise, 'index.htm' is displayed.

We also use this approach to notify users of upcoming planned outages. When we do this, we include a button, to then redirect them from this temporary default.htm page to their standard portal home/login page (index.htm). This way, they have to see our intended message but can easily go on to their "normal" page by clicking the button that is provided on the message page.

It sounds like this might be what you would want to do in oprder to accomplish the temproary redirect you describe. Feel free to contact me if you have any questions...

Thanks. I already do a flip of our login page when the system is down for maintenance, however in this case I need the user to log in first and then be taken to a page where they can complete a consent form. Since the data stored is specific by user it needs to happen after they log in. Ideally, we would only want to take individuals to the constent form if they have not yet completed it. I don't think changing everyones EMSS access url would not allow us to control the redirect by user.

Hi Joe - I did something similar that may be more trouble than it's worth but I'll be happy to share...
I set up a training course for an employee handbook sign-off and assigned all employees to that course. I then created a custom design studio form that was bookmarked and added to a role so that it would display when employees logged on. When they 'accepted' the terms of the handbook, it would mark the course as complete and re-direct them to 'home.htm'. I then set up a processflow that checked nightly to see who had completed the course and removed them from the role that included the bookmark. Again - may be more trouble than it's worth but it worked for our handbook sign-off - which we wanted to track in Lawson anyway...