Difference between revisions of "Internet Mail Archive System"

From PresenceWiki
Jump to: navigation, search
 
Line 1: Line 1:
 
{{Tutorials}}
 
{{Tutorials}}
 
  
 
<h2>Overview</h2>
 
<h2>Overview</h2>
  
This document describes the processes needed to autenticate a user accessing your pages by using
+
This document describes the IMAS system and how it was created using Presence.
their windows username and password.
+
 
 +
The Imas System currently performs 3 functions:-
 +
 
 +
The Mail Service connects to a POP(email) account and downloads attachments, based on conditions defined under the rules menu.
 +
 
 +
The Rule Service will then copy each attachment to a Network or AS400 location or place it in a folder to be processed by a task service.
  
This will then also enable you to track users through the site, so for instance, if they press a button on the site to action an event, you'll be able to log who actioned the event.
+
The Task Service will then process any attachments that need processing, custom tasks can be created for this purpose.
  
The advantages of this system are that:-
+
<h2>Specific DAS Solution</h2>
  
 +
 
* The user can use their windows username and password.
 
* The user can use their windows username and password.
 
* The httpsession variable is used so that the user only needs to login once.
 
* The httpsession variable is used so that the user only needs to login once.

Revision as of 10:28, 27 February 2012

Tutorial Pages > Internet Mail Archive System

Overview

This document describes the IMAS system and how it was created using Presence.

The Imas System currently performs 3 functions:-

The Mail Service connects to a POP(email) account and downloads attachments, based on conditions defined under the rules menu.

The Rule Service will then copy each attachment to a Network or AS400 location or place it in a folder to be processed by a task service.

The Task Service will then process any attachments that need processing, custom tasks can be created for this purpose.

Specific DAS Solution


  • The user can use their windows username and password.
  • The httpsession variable is used so that the user only needs to login once.
  • The username is stored against the ip address, so that it will only need to be entered once for a machine.
  • A session will automatically expire when no new requests have been made for a set time.

Importing

You can download the tasks for this example from:- http://www.international-presence.com/wikidocs/samples/On_Demand_Windows_Login.xml

Once imported they should look like:-

http://www.international-presence.com/images/docs/userlogin/tasks.png

To embed the task, we just place the Check Login Sub Task before our normal OnDemand task page as you can see below in Simple Task To Confirm Action.