Details
-
Type:
Improvement
-
Status:
Committed
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 1.1
-
Component/s: None
-
Labels:None
-
Request Controller:Scheibe, Andreas
-
External Supervisor:Please select
-
Executing Programmer:Please select
Description
(I thought this had been implemented?)
This replaces/changes the spec in the ticket GFW-184. It is more more detailed explanation of GFW-45.
To approve an request, the user gets an email with a text similiar to:
"To approve the request, please reply to this email, enter "yes" and send the mail. To reject the email, reply with "no". The text following the "no" will be used as the reason for the rejection.
The process id and the node id should be in the subject of the email. they could be behind other text, so that the user does not get disturbed. Example:
"Approve Requisition 3245 (process=45665-345)"
The workflow engine reads the incoming email. The process and node id is taken from the subject. The engine then reads the first couple of lines of the email until it finds a "yes"/"ja"/"no"/"nein". The text after "no" will be interpreted as the rejection reason.
The email reader should map the text to the action, so when the user types "ja" (german) or "yes" (english), this should be mapped to an event id (eg. "approve"). We will not have any specific structures to store the mapping, so the mapping needs to be coded in Groovy and could be changed in the customer environment.
When the process has already moved on, eg. because the user sended the same email twice, he gets another email similiar to:
"The workflow process 2345 that you sended an email to, has already moved to the next state. Probably you or somebody else has already entered the necessary information via a web browser, or you may have sended the email to workflow twice."
The changes are required for the email approval process in PROC.