Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Hello, the IBM code example is clear and matches your code block except you do not need os.Save, bin.save, you don't need searchscope either. You are hitting your guid right and have console out it was matched?  Is that guid one document or part of a version series? SAVE will commit your pending action you are correct about that. As another troubleshooting step after you locate your test document, recover and save it run the same code again and see if the item is still in the recovery bin.  Last troubleshooting step check your CPE log after you make the call, or if the item never moves out of recovery bin loop it with a thread sleep like 1 second and then look at CPE logs see what is going on. 

Working with Recovery Bins - IBM Documentation

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Hi Jay,

Thanks for the reply! I was assuming that I wouldn't need the os.save() and bin.save(), I had just added them because I was running out of ideas of what else to try. The code does successfully find that GUID and does the .recover() logic. The GUID is just the document ID of a standard document that was placed in the recovery bin. The documents for some reason successfully leave the recovery bin but they do not appear in content navigator. I am not really sure where the documents are ending up. 

Hello, the IBM code example is clear and matches your code block except you do not need os.Save, bin.save, you don't need searchscope either. You are hitting your guid right and have console out it was matched?  Is that guid one document or part of a version series? SAVE will commit your pending action you are correct about that. As another troubleshooting step after you locate your test document, recover and save it run the same code again and see if the item is still in the recovery bin.  Last troubleshooting step check your CPE log after you make the call, or if the item never moves out of recovery bin loop it with a thread sleep like 1 second and then look at CPE logs see what is going on. 

Working with Recovery Bins - IBM Documentation

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Oh k gotcha. When you say the document is not visible in navigator is that because you are using a search template to locate the document? After you do the recover + save, do an ad hoc search against all versions on document class root, enable include subclasses, do not use folder path as part of search and have one search field ID = 'your recycle item ID' execute and share the results. Do you see a document? Next step do the same search in ACCE, provide the GUID and search. If neither place returns a result and the item is in docversion take a look at the security_id and compare to a document you can see with the same security_id. If you cannot view the document and security is the same there must be another internal flag or bit preventing the document from being visible in CPE most likely a column in docversion. 

Hi Jay,

Thanks for the reply! I was assuming that I wouldn't need the os.save() and bin.save(), I had just added them because I was running out of ideas of what else to try. The code does successfully find that GUID and does the .recover() logic. The GUID is just the document ID of a standard document that was placed in the recovery bin. The documents for some reason successfully leave the recovery bin but they do not appear in content navigator. I am not really sure where the documents are ending up. 

Hello, the IBM code example is clear and matches your code block except you do not need os.Save, bin.save, you don't need searchscope either. You are hitting your guid right and have console out it was matched?  Is that guid one document or part of a version series? SAVE will commit your pending action you are correct about that. As another troubleshooting step after you locate your test document, recover and save it run the same code again and see if the item is still in the recovery bin.  Last troubleshooting step check your CPE log after you make the call, or if the item never moves out of recovery bin loop it with a thread sleep like 1 second and then look at CPE logs see what is going on. 

Working with Recovery Bins - IBM Documentation

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Hi Jay,

Thanks for the reply! I was assuming that I wouldn't need the os.save() and bin.save(), I had just added them because I was running out of ideas of what else to try. The code does successfully find that GUID and does the .recover() logic. The GUID is just the document ID of a standard document that was placed in the recovery bin. The documents for some reason successfully leave the recovery bin but they do not appear in content navigator. I am not really sure where the documents are ending up. 

Hello, the IBM code example is clear and matches your code block except you do not need os.Save, bin.save, you don't need searchscope either. You are hitting your guid right and have console out it was matched?  Is that guid one document or part of a version series? SAVE will commit your pending action you are correct about that. As another troubleshooting step after you locate your test document, recover and save it run the same code again and see if the item is still in the recovery bin.  Last troubleshooting step check your CPE log after you make the call, or if the item never moves out of recovery bin loop it with a thread sleep like 1 second and then look at CPE logs see what is going on. 

Working with Recovery Bins - IBM Documentation

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Christopher

If you are not sure where the documents are ending up, have you tried searching for them based on GUID...either using ICN or ACCE?

It is likely the documents are being "unfiled" and can't be browsed too, but a search in ICN can find them.

The other alternatives include the document has been marked as hidden in which case you will only be able to find it in ACCE, or you don't have permissions to view the document after it's been restored.

Hi Jay,

Thanks for the reply! I was assuming that I wouldn't need the os.save() and bin.save(), I had just added them because I was running out of ideas of what else to try. The code does successfully find that GUID and does the .recover() logic. The GUID is just the document ID of a standard document that was placed in the recovery bin. The documents for some reason successfully leave the recovery bin but they do not appear in content navigator. I am not really sure where the documents are ending up. 

Hello, the IBM code example is clear and matches your code block except you do not need os.Save, bin.save, you don't need searchscope either. You are hitting your guid right and have console out it was matched?  Is that guid one document or part of a version series? SAVE will commit your pending action you are correct about that. As another troubleshooting step after you locate your test document, recover and save it run the same code again and see if the item is still in the recovery bin.  Last troubleshooting step check your CPE log after you make the call, or if the item never moves out of recovery bin loop it with a thread sleep like 1 second and then look at CPE logs see what is going on. 

Working with Recovery Bins - IBM Documentation

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Hi Ruth, 

I have tried in ICN and ACCE but they do not appear in either of them. I checked with our head administrator and he should have full access to everything and he stated that the document appears to not exist at all. Is there something potentially wrong with my deletion process? After the recycle/delete script, the documents did appear in the recovery bin in ACCE but maybe there's something else I'm doing wrong? 

Thank you for taking the time to look at this,

Chris

Christopher

If you are not sure where the documents are ending up, have you tried searching for them based on GUID...either using ICN or ACCE?

It is likely the documents are being "unfiled" and can't be browsed too, but a search in ICN can find them.

The other alternatives include the document has been marked as hidden in which case you will only be able to find it in ACCE, or you don't have permissions to view the document after it's been restored.

Hi Jay,

Thanks for the reply! I was assuming that I wouldn't need the os.save() and bin.save(), I had just added them because I was running out of ideas of what else to try. The code does successfully find that GUID and does the .recover() logic. The GUID is just the document ID of a standard document that was placed in the recovery bin. The documents for some reason successfully leave the recovery bin but they do not appear in content navigator. I am not really sure where the documents are ending up. 

Hello, the IBM code example is clear and matches your code block except you do not need os.Save, bin.save, you don't need searchscope either. You are hitting your guid right and have console out it was matched?  Is that guid one document or part of a version series? SAVE will commit your pending action you are correct about that. As another troubleshooting step after you locate your test document, recover and save it run the same code again and see if the item is still in the recovery bin.  Last troubleshooting step check your CPE log after you make the call, or if the item never moves out of recovery bin loop it with a thread sleep like 1 second and then look at CPE logs see what is going on. 

Working with Recovery Bins - IBM Documentation

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Sorry -- I'm not able to clearly read the code in the graphic. Take a look at the samples here: https://www.ibm.com/docs/en/filenet-p8-platform/5.6.0?topic=bins-working-recovery and make sure you have the appropriate permission to get to the items.

Hi Ruth, 

I have tried in ICN and ACCE but they do not appear in either of them. I checked with our head administrator and he should have full access to everything and he stated that the document appears to not exist at all. Is there something potentially wrong with my deletion process? After the recycle/delete script, the documents did appear in the recovery bin in ACCE but maybe there's something else I'm doing wrong? 

Thank you for taking the time to look at this,

Chris

Christopher

If you are not sure where the documents are ending up, have you tried searching for them based on GUID...either using ICN or ACCE?

It is likely the documents are being "unfiled" and can't be browsed too, but a search in ICN can find them.

The other alternatives include the document has been marked as hidden in which case you will only be able to find it in ACCE, or you don't have permissions to view the document after it's been restored.

Hi Jay,

Thanks for the reply! I was assuming that I wouldn't need the os.save() and bin.save(), I had just added them because I was running out of ideas of what else to try. The code does successfully find that GUID and does the .recover() logic. The GUID is just the document ID of a standard document that was placed in the recovery bin. The documents for some reason successfully leave the recovery bin but they do not appear in content navigator. I am not really sure where the documents are ending up. 

Hello, the IBM code example is clear and matches your code block except you do not need os.Save, bin.save, you don't need searchscope either. You are hitting your guid right and have console out it was matched?  Is that guid one document or part of a version series? SAVE will commit your pending action you are correct about that. As another troubleshooting step after you locate your test document, recover and save it run the same code again and see if the item is still in the recovery bin.  Last troubleshooting step check your CPE log after you make the call, or if the item never moves out of recovery bin loop it with a thread sleep like 1 second and then look at CPE logs see what is going on. 

Working with Recovery Bins - IBM Documentation

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Hi Chris, do you want to do a screen share and do this together?  If so what's your schedule look like and time zone.

Sorry -- I'm not able to clearly read the code in the graphic. Take a look at the samples here: https://www.ibm.com/docs/en/filenet-p8-platform/5.6.0?topic=bins-working-recovery and make sure you have the appropriate permission to get to the items.

Hi Ruth, 

I have tried in ICN and ACCE but they do not appear in either of them. I checked with our head administrator and he should have full access to everything and he stated that the document appears to not exist at all. Is there something potentially wrong with my deletion process? After the recycle/delete script, the documents did appear in the recovery bin in ACCE but maybe there's something else I'm doing wrong? 

Thank you for taking the time to look at this,

Chris

Christopher

If you are not sure where the documents are ending up, have you tried searching for them based on GUID...either using ICN or ACCE?

It is likely the documents are being "unfiled" and can't be browsed too, but a search in ICN can find them.

The other alternatives include the document has been marked as hidden in which case you will only be able to find it in ACCE, or you don't have permissions to view the document after it's been restored.

Hi Jay,

Thanks for the reply! I was assuming that I wouldn't need the os.save() and bin.save(), I had just added them because I was running out of ideas of what else to try. The code does successfully find that GUID and does the .recover() logic. The GUID is just the document ID of a standard document that was placed in the recovery bin. The documents for some reason successfully leave the recovery bin but they do not appear in content navigator. I am not really sure where the documents are ending up. 

Hello, the IBM code example is clear and matches your code block except you do not need os.Save, bin.save, you don't need searchscope either. You are hitting your guid right and have console out it was matched?  Is that guid one document or part of a version series? SAVE will commit your pending action you are correct about that. As another troubleshooting step after you locate your test document, recover and save it run the same code again and see if the item is still in the recovery bin.  Last troubleshooting step check your CPE log after you make the call, or if the item never moves out of recovery bin loop it with a thread sleep like 1 second and then look at CPE logs see what is going on. 

Working with Recovery Bins - IBM Documentation

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Sorry -- I'm not able to clearly read the code in the graphic. Take a look at the samples here: https://www.ibm.com/docs/en/filenet-p8-platform/5.6.0?topic=bins-working-recovery and make sure you have the appropriate permission to get to the items.

Hi Ruth, 

I have tried in ICN and ACCE but they do not appear in either of them. I checked with our head administrator and he should have full access to everything and he stated that the document appears to not exist at all. Is there something potentially wrong with my deletion process? After the recycle/delete script, the documents did appear in the recovery bin in ACCE but maybe there's something else I'm doing wrong? 

Thank you for taking the time to look at this,

Chris

Christopher

If you are not sure where the documents are ending up, have you tried searching for them based on GUID...either using ICN or ACCE?

It is likely the documents are being "unfiled" and can't be browsed too, but a search in ICN can find them.

The other alternatives include the document has been marked as hidden in which case you will only be able to find it in ACCE, or you don't have permissions to view the document after it's been restored.

Hi Jay,

Thanks for the reply! I was assuming that I wouldn't need the os.save() and bin.save(), I had just added them because I was running out of ideas of what else to try. The code does successfully find that GUID and does the .recover() logic. The GUID is just the document ID of a standard document that was placed in the recovery bin. The documents for some reason successfully leave the recovery bin but they do not appear in content navigator. I am not really sure where the documents are ending up. 

Hello, the IBM code example is clear and matches your code block except you do not need os.Save, bin.save, you don't need searchscope either. You are hitting your guid right and have console out it was matched?  Is that guid one document or part of a version series? SAVE will commit your pending action you are correct about that. As another troubleshooting step after you locate your test document, recover and save it run the same code again and see if the item is still in the recovery bin.  Last troubleshooting step check your CPE log after you make the call, or if the item never moves out of recovery bin loop it with a thread sleep like 1 second and then look at CPE logs see what is going on. 

Working with Recovery Bins - IBM Documentation

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Hi Ruth, 

It looks like the code mentioned there is the same that I am using. I will triple check on permissions but I believe that the user that I am using has full access to this environment.

Thanks,

Chris

Sorry -- I'm not able to clearly read the code in the graphic. Take a look at the samples here: https://www.ibm.com/docs/en/filenet-p8-platform/5.6.0?topic=bins-working-recovery and make sure you have the appropriate permission to get to the items.

Hi Ruth, 

I have tried in ICN and ACCE but they do not appear in either of them. I checked with our head administrator and he should have full access to everything and he stated that the document appears to not exist at all. Is there something potentially wrong with my deletion process? After the recycle/delete script, the documents did appear in the recovery bin in ACCE but maybe there's something else I'm doing wrong? 

Thank you for taking the time to look at this,

Chris

Christopher

If you are not sure where the documents are ending up, have you tried searching for them based on GUID...either using ICN or ACCE?

It is likely the documents are being "unfiled" and can't be browsed too, but a search in ICN can find them.

The other alternatives include the document has been marked as hidden in which case you will only be able to find it in ACCE, or you don't have permissions to view the document after it's been restored.

Hi Jay,

Thanks for the reply! I was assuming that I wouldn't need the os.save() and bin.save(), I had just added them because I was running out of ideas of what else to try. The code does successfully find that GUID and does the .recover() logic. The GUID is just the document ID of a standard document that was placed in the recovery bin. The documents for some reason successfully leave the recovery bin but they do not appear in content navigator. I am not really sure where the documents are ending up. 

Hello, the IBM code example is clear and matches your code block except you do not need os.Save, bin.save, you don't need searchscope either. You are hitting your guid right and have console out it was matched?  Is that guid one document or part of a version series? SAVE will commit your pending action you are correct about that. As another troubleshooting step after you locate your test document, recover and save it run the same code again and see if the item is still in the recovery bin.  Last troubleshooting step check your CPE log after you make the call, or if the item never moves out of recovery bin loop it with a thread sleep like 1 second and then look at CPE logs see what is going on. 

Working with Recovery Bins - IBM Documentation

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris

Good morning,

I'm currently working on a data script that iterates through a specific recovery bin to find a specified item and use .recover() to return it back to the DocVersion table. When doing my initial testing on this, it appears that the .recover() function out of the box just adds the recovery process as a pending action and I am unsure how to make that complete processing. For most pending actions, just using ".save(RefreshMode.REFRESH)" on the item is enough to get the server to process it but I've tried saving/refreshing the CmRecoveryItemImpl, the object store, and even the recovery bin but the item is still not searchable in Content Navigator or in the DocVersion table. Here is a code snippet of the logic I am using:

I would greatly appreciate any advice/input that you may be able to offer and thank you for reading my post.

Thanks,

Chris