|
Anonymous | Login | Signup for a new account | 2024-11-22 09:43 CET |
Main | My View | View Issues | Change Log | Roadmap | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
0000117 | [Oberon Platform] Platform functionalities | feature | always | 2014-08-03 12:54 | 2014-08-03 12:59 | ||
Reporter | administrator | View Status | public | ||||
Assigned To | administrator | ||||||
Priority | normal | Resolution | fixed | Platform | |||
Status | resolved | OS | |||||
Projection | none | OS Version | |||||
ETA | none | Fixed in Version | 4.2 - DB build 0072 | Product Version | 4.1 - DB build 0071 | ||
Target Version | 4.2 - DB build 0072 | Product Build | |||||
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 | |||||||
Tags | No tags attached. | ||||||
Attached Files | |||||||
|
© 2008-2013 Mirko Solazzi | Website
Templates by IceTemplates.com
Please Read: Privacy Policy and Terms of Use |