Versioning with BOPF

[victor_ionescu]

Hi all,

does BOPF provide any built-in functionality for versioning of entries ( e.g. in order to display a log of the different states that a particular node has had throughout the time )?

Or is this something that would need to be handled on the application-level ? ( Or perhaps by implementing a custom data access layer )

Best regards

Victor

[victor_ionescu]

Hi all,

does BOPF provide any built-in functionality for versioning of entries ( e.g. in order to display a log of the different states that a particular node has had throughout the time )?

Or is this something that would need to be handled on the application-level ? ( Or perhaps by implementing a custom data access layer )

Best regards

Victor

[former_member190794]

Hello Victor,

there is no built-in functionality available, so you could implement this on application layer.

a) You introduce a version flag on each node to be versionized and create custom associations and queries that only take the current version into account. In case of alternative keys, the version flag needs to be part of it. The disadvantage of this solution: it expands your BO model.

If you need to version the whole BO instance, you could create a toplevel version node and have all application specific nodes as subnodes.

b) You implement an own DAC that filters out old versions. You can check /BOBF/CL_DAC_TABLE and adapt the SQL statements accordingly (that are only a few). The advantage of this solution is that your BO model keeps small.

Best regards

Tilmann

[victor_ionescu]

Hi Tilmann,

thanks for the quick reply. This was also what I was assuming

Best regards

Victor