OBEROn - Bug Trace - Oberon Platform
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
21 Domain Objects feature N/A 2011-01-13 11:49 2022-08-23 03:57
Reporter: guest Platform:  
Assigned To: administrator OS:  
Priority: normal OS Version:  
Status: feedback Product Version: 2.0 - DB build 0052  
Product Build: Resolution: reopened  
Projection: none      
ETA: none Fixed in Version: 4.0 - DB build 0070  
Summary: 0000021: Need functinality to do check out-check in and undo checkout
Description: Business Objects are modified by many people and they need to track the changes on the Business Objects. So some business Objects needs to have the capability to do a check out check in and Undo Check out functionality and track these in terms of iteration history
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:
Issue History
Date Modified Username Field Change
2011-01-13 11:49 guest New Issue
2011-01-19 16:21 administrator Status new => assigned
2011-01-19 16:21 administrator Assigned To => administrator
2011-01-19 16:22 administrator Status assigned => feedback
2011-05-17 17:23 administrator Note Added: 0000071
2011-05-17 17:23 administrator Status feedback => acknowledged
2011-08-10 19:19 guest Note Added: 0000090
2011-08-10 20:32 guest Note Deleted: 0000090
2011-09-15 04:29 guest Note Added: 0000097
2011-09-16 16:59 guest Note Added: 0000098
2011-09-17 10:19 guest Note Deleted: 0000098
2011-09-17 10:19 guest Note Deleted: 0000097
2011-09-19 04:58 guest Note Added: 0000101
2011-09-20 23:58 guest Note Added: 0000102
2011-09-21 02:18 guest Note Added: 0000103
2011-09-21 06:10 guest Note Added: 0000104
2011-09-21 09:05 guest Note Added: 0000105
2011-09-22 08:15 guest Note Added: 0000106
2011-09-22 19:29 guest Note Added: 0000109
2011-09-22 20:19 guest Note Added: 0000110
2011-09-23 00:28 guest Note Added: 0000111
2011-09-23 08:19 guest Note Added: 0000112
2011-09-23 09:32 administrator Note Deleted: 0000101
2011-09-23 09:32 administrator Note Deleted: 0000102
2011-09-23 09:32 administrator Note Deleted: 0000103
2011-09-23 09:32 administrator Note Deleted: 0000104
2011-09-23 09:32 administrator Note Deleted: 0000105
2011-09-23 09:32 administrator Note Deleted: 0000106
2011-09-23 09:32 administrator Note Deleted: 0000109
2011-09-23 09:32 administrator Note Deleted: 0000111
2011-09-23 09:32 administrator Note Deleted: 0000112
2011-09-23 09:32 administrator Note Deleted: 0000110
2011-09-23 18:19 guest Note Added: 0000114
2011-09-25 23:21 guest Note Added: 0000117
2011-09-26 12:43 guest Note Added: 0000118
2011-09-26 16:50 guest Note Added: 0000119
2011-09-29 03:00 guest Note Added: 0000120
2011-09-29 23:43 guest Note Added: 0000121
2011-09-30 08:25 guest Note Added: 0000122
2011-10-03 17:22 guest Note Added: 0000123
2011-10-04 22:10 guest Note Added: 0000124
2011-10-04 23:09 guest Note Added: 0000125
2011-10-05 08:44 guest Note Added: 0000126
2011-10-05 19:01 guest Note Deleted: 0000114
2011-10-05 19:02 guest Note Deleted: 0000124
2011-10-05 19:02 guest Note Deleted: 0000125
2011-10-05 19:02 guest Note Deleted: 0000126
2011-10-05 19:02 guest Note Deleted: 0000122
2011-10-05 19:02 guest Note Deleted: 0000118
2011-10-05 19:02 guest Note Deleted: 0000123
2011-10-05 19:02 guest Note Deleted: 0000121
2011-10-05 19:02 guest Note Deleted: 0000120
2011-10-05 19:02 guest Note Deleted: 0000117
2011-10-05 19:02 guest Note Deleted: 0000119
2011-10-05 19:03 administrator Status acknowledged => feedback
2011-10-05 23:31 guest Note Added: 0000127
2011-10-06 12:06 guest Note Added: 0000128
2011-10-06 14:07 guest Note Added: 0000129
2011-10-06 16:01 guest Note Added: 0000130
2011-10-07 01:39 guest Note Added: 0000131
2011-10-07 11:35 guest Note Added: 0000132
2011-10-09 15:44 guest Note Added: 0000133
2011-10-10 23:14 guest Note Added: 0000134
2011-10-11 02:36 guest Note Added: 0000135
2011-10-11 06:05 guest Note Added: 0000136
2011-10-11 14:16 administrator Note Deleted: 0000127
2011-10-11 14:16 administrator Note Deleted: 0000128
2011-10-11 14:16 administrator Note Deleted: 0000129
2011-10-11 14:17 administrator Note Deleted: 0000132
2011-10-11 14:17 administrator Note Deleted: 0000135
2011-10-11 14:17 administrator Note Deleted: 0000134
2011-10-11 14:17 administrator Note Deleted: 0000136
2011-10-11 14:17 administrator Note Deleted: 0000131
2011-10-11 14:17 administrator Note Deleted: 0000130
2011-10-11 14:17 administrator Note Deleted: 0000133
2012-08-08 15:21 administrator Status feedback => assigned
2012-08-08 15:23 administrator Target Version => 2.7 build 0066
2012-08-08 16:57 administrator Note Added: 0000147
2012-08-08 17:06 administrator Note Edited: 0000147
2012-08-08 17:13 administrator Note Added: 0000148
2012-08-08 17:14 administrator Note Edited: 0000148
2012-08-08 17:14 administrator Note Edited: 0000148
2012-08-08 17:15 administrator Status assigned => resolved
2012-08-08 17:15 administrator Fixed in Version => 2.7 build 0066
2012-08-08 17:15 administrator Resolution open => fixed
2012-09-24 03:02 guest Status resolved => feedback
2012-09-24 03:02 guest Resolution fixed => reopened
2012-09-24 20:41 administrator Status feedback => resolved
2012-09-24 20:41 administrator Resolution reopened => fixed
2013-04-12 08:26 guest Status resolved => feedback
2013-04-12 08:26 guest Resolution fixed => reopened
2013-04-12 13:12 administrator Status feedback => resolved
2013-04-12 13:12 administrator Fixed in Version 3.0 - DB build 0067 => 4.0 - DB build 0070
2013-04-12 13:12 administrator Resolution reopened => fixed
2022-08-23 03:57 guest Status resolved => feedback
2022-08-23 03:57 guest Resolution fixed => reopened

Notes
(0000071)
administrator   
2011-05-17 17:23   
Possible with the following limitations:
-Iterations can be archived for comparison, for change trace and for change rollbacks.
-Object iterations cannot be retrieved with global searches (only the last iteration will be compared with query filters)
-Cannot recover overwritten object attached files
(0000147)
administrator   
2012-08-08 16:57   
(edited on: 2012-08-08 17:06)
Solution to this requirements is partially implemented as follows:

the new "undo" option has been added for objects (in the lifecycle definition) and links (in the linktype definition)

lifecycle edit <LCNAME> ... [!|not]undo... ;
lifecycle show <LCNAME> get { ... undo ... } token ... ;

linktype edit <LTNAME> ... [!|not]undo... ;
linktype show <LTNAME> get { ... undo... } token ... ;

If the "undo" flag is enabled, each modification performed on the object/link generates a new iteration where the previous values for changed properties are stored.

To get the last or current iteration number use:

object show <id/CNR> get { ... iteration ... } token ... ;
link show <id> get { ... iteration ... } token ... ;

or the SDK method for ObjectObj / Link classes:

int getCurrentIteration(Framework framework)

It is also possible to retrieve the values stored for each iteration:

object show <id/CNR> get { ... iteration[<number>] ... } token ... ;
link show <id> get { ... iteration[<number>] ... } token ... ;

where <number> is the number of iteration

The same result can be obtained with the SDK method:

String getIteration(int iterNumber,Framework framework)
(0000148)
administrator   
2012-08-08 17:13   
(edited on: 2012-08-08 17:14)
The "undo" action is similar to the other user actions:

- it can be enabled in the lifecycle/stage for user/team/assignments
- it can raise check / action triggers to extend the basic behaviour
- it can be traced in the history table for both objects and links

Users enabled to perform the "undo" operation can execute the OOQL commands:

object undo <id/CNR>;
link undo <id>;

to go back to the previous status; or the following:

object undo <id/CNR> iteration[<number>];
link undo <id> iteration[<number>];

to return to the situation before the iteration N. <number>