OBEROn - Bug Trace - Oberon Platform
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
49 Context Design feature N/A 2011-05-09 18:49 2011-05-28 20:58
Reporter: g_prajeesh Platform:  
Assigned To: administrator OS:  
Priority: low OS Version:  
Status: closed Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2.3 - DB build 0060  
Summary: 0000049: Notification Step - Simple as well as advanced
Description: In notification step in WF, please define two type of notification

1. Simple

2. Advanced

In Simple Notification, the subject can contain Dictionary as well as parameter( Step / Process)

Body can contain simple message that can contain parameter as well as dictionary

In advanced

It can contain object information, form definition etc..
Steps To Reproduce:
Additional Information: I will add more info once I go through the current implementation
Relationships
Attached Files:
Issue History
Date Modified Username Field Change
2011-05-09 18:49 g_prajeesh New Issue
2011-05-10 17:18 administrator Assigned To => administrator
2011-05-10 17:18 administrator Status new => assigned
2011-05-12 01:08 administrator Note Added: 0000065
2011-05-12 01:08 administrator Status assigned => resolved
2011-05-12 01:08 administrator Fixed in Version => 2.3 build 0060
2011-05-12 01:08 administrator Resolution open => fixed
2011-05-12 01:08 administrator Target Version => 2.3 build 0060
2011-05-28 20:58 g_prajeesh Status resolved => closed

Notes
(0000065)
administrator   
2011-05-12 01:08   
In notification step it is possible to use a form for the body or a text.
If a form is specified the step is automatically an Advanced notification step, otherwise the body text will be used to send mail.
Subject and Body Text can include
- object information (i.e. <class> <currentstage>)
- dictionary keywords (i.e. <[mysection,mykeyword]> )
- step / process parameters (i.e. <{myparam}> ); note step's parameters overwrite process's parameters
It is possible also to use a mix like <[section,<class>]> (first get object class then translate it) or <[<{myparam}>]> (first get a parameter value then translate it)

In case of advanced, forms can include field and labels as usual in UI, while step/process parameters can be introduced with action fields with the same name of the parameter.