Auto Deletion - Revision history

LDO at 10:55, 13 May 2025

2025-05-13T10:55:17Z

LDO at 10:52, 13 May 2025

2025-05-13T10:52:32Z

LDO at 10:49, 13 May 2025

2025-05-13T10:49:49Z

LDO at 10:49, 13 May 2025

2025-05-13T10:49:31Z

LDO at 10:48, 13 May 2025

2025-05-13T10:48:44Z

LDO at 10:48, 13 May 2025

2025-05-13T10:48:14Z

LDO at 10:45, 13 May 2025

2025-05-13T10:45:12Z

LDO at 10:44, 13 May 2025

2025-05-13T10:44:42Z

LDO at 10:41, 13 May 2025

2025-05-13T10:41:53Z

LDO: Created page with "UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses. This can be done via the MetaClass DELETE_CONFIGU..."

2025-05-13T10:39:41Z

Created page with "UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses. This can be done via the MetaClass DELETE_CONFIGU..."

New page

UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses.
This can be done via the MetaClass DELETE_CONFIGURATION which is provided from a UBIK database and can be found under System.Main.Base.

The deletion configuration is divided into two main categories:
===Soft Deletion===
A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.

===Hard Deletion===
''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation.

Example: Delete Configuration for the Progress Task MetaClass where limit is set to 30 days
[[File:Example_DeleteConfig.png|350x100px]]
Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.

===Deletion Workflow===
The DeleteManager component needs to be initialized (via WhoBert for example) to handle the deletion process.
Within the DeleteManager, this method must be executed:

ExecuteSoftDelete: This method updates the record's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.
Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.

<source lang = "csharp">
DeleteManager delmanager = new DeleteManager();
delManager.ExecuteSoftDelete();
</source>

← Older revision		Revision as of 10:52, 13 May 2025
Line 26:		Line 26:
	delManager.ExecuteSoftDelete();		delManager.ExecuteSoftDelete();
	</source>		</source>
−
−	~~[[Category:Pages with broken file links\|Auto Deletion]]~~

@@ Line 11: / Line 11: @@
 ====Example====
 Delete Configuration for the Progress Task MetaClass where limit is set to 30 days
-[[File:DeleteConfigExample.PNG]]
+[[File:Example_DeleteConfig.png]]
 Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.

@@ Line 11: / Line 11: @@
 ====Example====
 Delete Configuration for the Progress Task MetaClass where limit is set to 30 days
-[[File:Example DeleteConfig.PNG]]
+[[File:DeleteConfigExample.PNG]]
 Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.

@@ Line 11: / Line 11: @@
 ====Example====
 Delete Configuration for the Progress Task MetaClass where limit is set to 30 days
-[[File:Example_DeleteConfig.PNG]]
+[[File:Example DeleteConfig.PNG]]
 Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.

@@ Line 9: / Line 9: @@
 ''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are marked as hard-deleted and can be permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation.
-Example: Delete Configuration for the Progress Task MetaClass where limit is set to 30 days
+====Example====
 [[File:Example_DeleteConfig.PNG]]
 Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.

@@ Line 19: / Line 19: @@
 Within the DeleteManager, this method must be executed:
-ExecuteSoftDelete: This method updates the record's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.
+ExecuteSoftDelete: This method itertaes through all instances which are marked for soft-deletion, updates the instance's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.
 Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.

@@ Line 4: / Line 4: @@
 The deletion configuration is divided into two main categories:
 ===Soft Deletion===
-A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.
+A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be marked as soft-deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.
 ===Hard Deletion===
-''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation.
+''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are marked as hard-deleted and can be permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation.
 Example: Delete Configuration for the Progress Task MetaClass where limit is set to 30 days
@@ Line 24: / Line 24: @@
 delManager.ExecuteSoftDelete();
 </source>