Content Management and Capture

Hi All,

I am having an issue with all of the pages being set to Problem in Verify. This started with our updating Datacap to 9.1.9 ifix005. I have two applications which are almost identical. One is having this issue, and the other is not. Along with the Datacap upgrade I also changed to PDFFREDocumentToImage to reduce the size of the tiffs converted from PDFs. 

In the Verify task, all pages are marked as problem. You have to hit submit on all pages. We have very large documents of 300 to 400 pages. I cannot figure out where the trailing_pages are being set to problem. 

Thanks,

Bob

Hi Bob,

There are a couple of things which might cause this to happen:

1. If you're using Datacap Navigator and your previous version of Datacap was prior to 9.1.5, check this out article: https://www.ibm.com/support/pages/ibm-datacap-navigator-visiting-page-verify-task-page-status-changes-problem
2. It's more likely that your Page Statuses needs to be checked / set: https://www.ibm.com/docs/en/datacap/9.1.9?topic=navigator-specifying-page-types-main-pages-trailing-pages. To set these in TMWeb, go to the Administrator tab, select the Verify task and click the Setup link:
   
   
   
   
   
   
   
   You could compare the settings of the app that is working with the one that is not.

Hope this helps!

Shaun

Hi All,

I am having an issue with all of the pages being set to Problem in Verify. This started with our updating Datacap to 9.1.9 ifix005. I have two applications which are almost identical. One is having this issue, and the other is not. Along with the Datacap upgrade I also changed to PDFFREDocumentToImage to reduce the size of the tiffs converted from PDFs. 

In the Verify task, all pages are marked as problem. You have to hit submit on all pages. We have very large documents of 300 to 400 pages. I cannot figure out where the trailing_pages are being set to problem. 

Thanks,

Bob

Not sure what happened to my reply earlier.

Thanks Shaun for the suggestions,

We are using Navigator for Verify. The issue is not that the pages are turning to problem on viewing the pages, they are all set to problem when opening the batch in Verify. I did try your suggestion on the configuration but no change.

Bob

Hi Bob,

There are a couple of things which might cause this to happen:

1. If you're using Datacap Navigator and your previous version of Datacap was prior to 9.1.5, check this out article: https://www.ibm.com/support/pages/ibm-datacap-navigator-visiting-page-verify-task-page-status-changes-problem
2. It's more likely that your Page Statuses needs to be checked / set: https://www.ibm.com/docs/en/datacap/9.1.9?topic=navigator-specifying-page-types-main-pages-trailing-pages. To set these in TMWeb, go to the Administrator tab, select the Verify task and click the Setup link:
   
   
   
   
   
   
   
   You could compare the settings of the app that is working with the one that is not.

Hope this helps!

Shaun

Hi All,

I am having an issue with all of the pages being set to Problem in Verify. This started with our updating Datacap to 9.1.9 ifix005. I have two applications which are almost identical. One is having this issue, and the other is not. Along with the Datacap upgrade I also changed to PDFFREDocumentToImage to reduce the size of the tiffs converted from PDFs. 

In the Verify task, all pages are marked as problem. You have to hit submit on all pages. We have very large documents of 300 to 400 pages. I cannot figure out where the trailing_pages are being set to problem. 

Thanks,

Bob

Hi Bob,

Without seeing the application, it's difficult to suggest other reasons why the trailing pages have a status of 1 when they arrive in the Verify panel.

Assuming that there is a Validate task which runs prior to Verify, it could be that which is setting the page statuses to 1. It may also be getting set before that, however.

You could compare both applications side by side in Datacap Studio to see whether there are differences in the configuration of their Validate tasks. Specifically, I would be looking for the use of the  StatusPreserveOn and StatusPreserveOff actions in the first instance:

https://www.ibm.com/docs/en/datacap/9.1.9?topic=rulerunnerlogic-statuspreserveoff

https://www.ibm.com/docs/en/datacap/9.1.9?topic=rulerunnerlogic-statuspreserveon

I've seen a couple of situations where ootb actions used to return True in older versions when in fact they should have returned False under certain circumstances or vice versa. This went unnoticed until the app was upgraded and the fact that the behaviour was fixed by IBM brought it to light. 

If the Validate task / StatusPreserveOn / StatusPreserveOff doesn't shed any light on it, I would process a batch in Datacap Studio and see at which point the trailing page status is set to 1, then do the same with the good application and compare the behaviour between the two.

I hope this helps!

Shaun

Not sure what happened to my reply earlier.

Thanks Shaun for the suggestions,

We are using Navigator for Verify. The issue is not that the pages are turning to problem on viewing the pages, they are all set to problem when opening the batch in Verify. I did try your suggestion on the configuration but no change.

Bob

Hi Bob,

There are a couple of things which might cause this to happen:

1. If you're using Datacap Navigator and your previous version of Datacap was prior to 9.1.5, check this out article: https://www.ibm.com/support/pages/ibm-datacap-navigator-visiting-page-verify-task-page-status-changes-problem
2. It's more likely that your Page Statuses needs to be checked / set: https://www.ibm.com/docs/en/datacap/9.1.9?topic=navigator-specifying-page-types-main-pages-trailing-pages. To set these in TMWeb, go to the Administrator tab, select the Verify task and click the Setup link:
   
   
   
   
   
   
   
   You could compare the settings of the app that is working with the one that is not.

Hope this helps!

Shaun

Hi All,

I am having an issue with all of the pages being set to Problem in Verify. This started with our updating Datacap to 9.1.9 ifix005. I have two applications which are almost identical. One is having this issue, and the other is not. Along with the Datacap upgrade I also changed to PDFFREDocumentToImage to reduce the size of the tiffs converted from PDFs. 

In the Verify task, all pages are marked as problem. You have to hit submit on all pages. We have very large documents of 300 to 400 pages. I cannot figure out where the trailing_pages are being set to problem. 

Thanks,

Bob

Hi Shaun,

I ended up creating a rule to force the status to ok on Trailing_Pages, rrSet("0","@F.Status"). Not sure what could have changed but this seems to be working. 

Thanks again for your suggestions,

Bob

Hi Bob,

Without seeing the application, it's difficult to suggest other reasons why the trailing pages have a status of 1 when they arrive in the Verify panel.

Assuming that there is a Validate task which runs prior to Verify, it could be that which is setting the page statuses to 1. It may also be getting set before that, however.

You could compare both applications side by side in Datacap Studio to see whether there are differences in the configuration of their Validate tasks. Specifically, I would be looking for the use of the  StatusPreserveOn and StatusPreserveOff actions in the first instance:

https://www.ibm.com/docs/en/datacap/9.1.9?topic=rulerunnerlogic-statuspreserveoff

https://www.ibm.com/docs/en/datacap/9.1.9?topic=rulerunnerlogic-statuspreserveon

I've seen a couple of situations where ootb actions used to return True in older versions when in fact they should have returned False under certain circumstances or vice versa. This went unnoticed until the app was upgraded and the fact that the behaviour was fixed by IBM brought it to light. 

If the Validate task / StatusPreserveOn / StatusPreserveOff doesn't shed any light on it, I would process a batch in Datacap Studio and see at which point the trailing page status is set to 1, then do the same with the good application and compare the behaviour between the two.

I hope this helps!

Shaun

Not sure what happened to my reply earlier.

Thanks Shaun for the suggestions,

We are using Navigator for Verify. The issue is not that the pages are turning to problem on viewing the pages, they are all set to problem when opening the batch in Verify. I did try your suggestion on the configuration but no change.

Bob

Hi Bob,

There are a couple of things which might cause this to happen:

1. If you're using Datacap Navigator and your previous version of Datacap was prior to 9.1.5, check this out article: https://www.ibm.com/support/pages/ibm-datacap-navigator-visiting-page-verify-task-page-status-changes-problem
2. It's more likely that your Page Statuses needs to be checked / set: https://www.ibm.com/docs/en/datacap/9.1.9?topic=navigator-specifying-page-types-main-pages-trailing-pages. To set these in TMWeb, go to the Administrator tab, select the Verify task and click the Setup link:
   
   
   
   
   
   
   
   You could compare the settings of the app that is working with the one that is not.

Hope this helps!

Shaun

Hi All,

I am having an issue with all of the pages being set to Problem in Verify. This started with our updating Datacap to 9.1.9 ifix005. I have two applications which are almost identical. One is having this issue, and the other is not. Along with the Datacap upgrade I also changed to PDFFREDocumentToImage to reduce the size of the tiffs converted from PDFs. 

In the Verify task, all pages are marked as problem. You have to hit submit on all pages. We have very large documents of 300 to 400 pages. I cannot figure out where the trailing_pages are being set to problem. 

Thanks,

Bob