View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000023 | Oberon Platform | Platform functionalities | public | 2011-04-25 09:36 | 2011-05-28 20:55 |
| Reporter | g_prajeesh | Assigned To | administrator | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 2.3 - DB build 0060 | Fixed in Version | 2.3 - DB build 0060 | ||
| Summary | 0000023: Notification Step in WF | ||||
| Description | We will have a new Step for Notification. Need To, CC and BCC Function Need from function. for eg. System can send mail using a help desk email id or using system admin email id. Will have subject and it can contain Business Information as a variable eg. Engineering Change Order <Link to ECO Object View> has been completed. The variable parameter can be defined as WF Parameter or if <ObjectID> is specified, it will create the Link to the view page and replaced with it Will have Body Content and similar to subject, it can contain variable parameter. | ||||
| Tags | No tags attached. | ||||
|
|
Notification step can have the following fields: To: can include actor names (i.e: user[<user.name>] assignment[<assign.name>] team[<team.name>] ) and email addresses Cc: the same of To field Subject: a text with replacement keywords <[dictionary key]> <object parameters> Body-Form: a form for the message text composition |
|
|
Need from function. for eg. System can send mail using a help desk email id or using system admin email id. |
|
|
Added new notification step, with following parameters: - Subject: can include a text with replacement keywords <[dictionary key]> (i.e. <[section,keyword]> ) <object parameters> (i.e. <class> <currentstage> <to.link[linkname].from.name> ) - Body-Form: this form generates the body text, can include dictionary labels, field values or step parameters (in action elements) - Language: define the language for the translation of subject and body; if specified the same mail will be sent to all recipients according to the recipient type (to,cc,bcc); if not specified system will generate one mail for each recipient (all will be considered as "to" type) and it will use the language declared for the user / team / assignment to translate subject and body - To,Cc,Bcc : can include actor names (i.e: user[<user.name>] assignment[<assign.name>] team[<team.name>] ) In the step parameters you can define the "SENDER" and the "OBJECTID"; the first will be used as mail sender while the object id will be used for the subject and body-form replacements. |
|
|
Added |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-04-25 09:36 | g_prajeesh | New Issue | |
| 2011-04-26 10:15 | administrator | Note Added: 0000024 | |
| 2011-04-26 10:15 | administrator | Assigned To | => g_prajeesh |
| 2011-04-26 10:15 | administrator | Status | new => feedback |
| 2011-04-26 10:20 | g_prajeesh | Description Updated | |
| 2011-04-26 10:21 | g_prajeesh | Status | feedback => assigned |
| 2011-04-26 10:25 | g_prajeesh | Assigned To | g_prajeesh => administrator |
| 2011-04-26 10:26 | g_prajeesh | Note Added: 0000026 | |
| 2011-05-01 13:37 | administrator | Target Version | => 2.3 build 0060 |
| 2011-05-06 21:53 | administrator | Note Added: 0000056 | |
| 2011-05-06 21:53 | administrator | Status | assigned => resolved |
| 2011-05-06 21:53 | administrator | Fixed in Version | => 2.3 build 0060 |
| 2011-05-06 21:53 | administrator | Resolution | open => fixed |
| 2011-05-07 00:52 | administrator | Category | Context Design => Platform functionalities |
| 2011-05-28 20:55 | g_prajeesh | Note Added: 0000079 | |
| 2011-05-28 20:55 | g_prajeesh | Status | resolved => closed |
