Need more details about archiving the Work Objects to another DB
Provide more details on following queries:
1.Handling the Index related tables
User tries deleting Work Object from Work table system automatically deletes the indexes from index tables, but when retrieved it system did not create the index instances related to the work Object.
What is the reason?
2.What are the different tables, in which Work Object data is stored.
-User is aware of the pc_work, history, workparty and pc_link_attachment tables. Please provide rest of the table details.
3.How to handle the archiving, can this be done with below approach, or do we have any OOTB approach for archiving:
-Open the WorkObject from the work table, copy the WorkObject to the Archive table (this is a replica of the work table) and delete the Workobject from Work table (With Obj-* methods).
4.Do we have any document link for knowing more information about the archiving.
Handling the Index related tables? how it will be populated?
When we import the archive zip, index should be created on saving the WO and saving is done automatically in the process of importing.
How do we need to handle the archiving, can this be done with below approach, or do we have any OOTB approach for archiving.
What are the different tables, in which Work Object data will be stored.
You can enable the Global DB trace in SME and get all the insert statements when creating the work item to precisely get an idea which all table gets updated.
0% found this useful