View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000114 | Oberon Platform | Platform functionalities | public | 2014-08-01 18:59 | 2014-08-06 18:32 |
| Reporter | g_prajeesh | Assigned To | administrator | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.1 - DB build 0071 | ||||
| Target Version | 4.2 - DB build 0072 | Fixed in Version | 4.2 - DB build 0072 | ||
| Summary | 0000114: Add more states for workflow steps and trigger for state change events | ||||
| Description | Each of the workflow steps should have the following behaviour / states: Start, Resume, Skip, abort, complete, restart, terminate each of these can associated with a program so that it can be run when the step changes to the state. Same for Workflow process | ||||
| Tags | No tags attached. | ||||
|
|
At the moment we have the following step status: Queued: added to the running list Wait: waiting for user action Execution: system actions are running Suspended: step execution is suspended Expired: expiration date is reached Error: execution returned an error Completed: finished its execution Terminated: execution aborted and the following step actions: Complete change status to Completed Suspend change status to Suspended Resume change status to Queued and then automatically to Wait or Execution Terminate change status to Terminated it is also possible to force the status to Error or Expired So the proposed status list is equivalent to: Start = Queued (first time execution) Resume = Queued (continue from the situation before the suspension) Restart (not supported) Skip (not supported) Complete = Completed Terminate = Terminated Abort = Terminated or Suspended? |
|
|
Added the Skipped status and the possibility to set this status by the "process update-step" command. For example: process update '59E9965D' step 'action_1' status skipped; Added the "Change State" trigger : when a change is made in the step status the declared program will be executed automatically. workflow edit '<WF Name>' step change '<Step Name>' changestate trigger '<Program Name>' ; |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-08-01 18:59 | g_prajeesh | New Issue | |
| 2014-08-03 11:23 | administrator | Status | new => assigned |
| 2014-08-03 11:23 | administrator | Assigned To | => administrator |
| 2014-08-03 11:23 | administrator | Status | assigned => acknowledged |
| 2014-08-06 11:41 | administrator | Note Added: 0000187 | |
| 2014-08-06 11:42 | administrator | Note Edited: 0000187 | |
| 2014-08-06 18:19 | administrator | Fixed in Version | => 4.2 - DB build 0072 |
| 2014-08-06 18:19 | administrator | Target Version | => 4.2 - DB build 0072 |
| 2014-08-06 18:19 | administrator | Summary | each of the workflow steps should have the following behaviour / states => Add more states for workflow steps and trigger for state change events |
| 2014-08-06 18:19 | administrator | Description Updated | |
| 2014-08-06 18:32 | administrator | Note Added: 0000188 | |
| 2014-08-06 18:32 | administrator | Status | acknowledged => resolved |
| 2014-08-06 18:32 | administrator | Resolution | open => fixed |
