|
OBEROn - Bug Trace - Oberon Platform
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 117 | Platform functionalities | feature | always | 2014-08-03 12:54 | 2014-08-03 12:59 |
|
|
|||||
| Reporter: | administrator | Platform: | |||
| Assigned To: | administrator | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | resolved | Product Version: | 4.1 - DB build 0071 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.2 - DB build 0072 | ||
|
|
|||||
| Summary: | 0000117: Perform lifecycle actions on workflow execution | ||||
| Description: |
In OBEROn you can automatically start a workflow when an event occurs: the generated process includes the OBJECTID and some other object related information in the parameter list. The workflow generally represents the evolution of the object lifecycle and after completed some actions, you need to change the object status; in the current version, a process can modify the object status in a programmatic way by adding a System-type step with java code inside. It should be more simple if you define a new step-type for performing direct action on object lifecycle. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
|
|
|||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2014-08-03 12:54 | administrator | New Issue | |||
| 2014-08-03 12:54 | administrator | Fixed in Version | => 4.2 - DB build 0072 | ||
| 2014-08-03 12:54 | administrator | Target Version | => 4.2 - DB build 0072 | ||
| 2014-08-03 12:59 | administrator | Note Added: 0000182 | |||
| 2014-08-03 12:59 | administrator | Status | new => resolved | ||
| 2014-08-03 12:59 | administrator | Resolution | open => fixed | ||
| 2014-08-03 12:59 | administrator | Assigned To | => administrator | ||
| Notes | |||||
|
|
|||||
|
|
||||