Exclude a file from scan

Exclude a file from scan


ControlPoint allows to exclude files when scanning sources. The graphical interface gives the possibility to exclude file extensions. What if I want to exclude a specific file.

Annotation 2020-04-30 141928.png


The connector configuration file gives you more granularity in what you can exclude.

Open the connector configuration file (.cfg).

Go to the task section of the repository: e.g. [TaskMyRepository]

Add the PathCantHaveRegex parameter. In the following example, we exclude "thumb.db" files AND all pdf files.


Note that you can have multiple parameters with the number at the end.

Also note that when you use these manual adds in the configuration file, you should not use anymore the field in the graphical interface as this will conflict.

See also the file system connector documentation: https://www.microfocus.com/documentation/idol/IDOL_12_3/FileSystemConnector_12.3_Documentation/Help/index.html#Configuration/TaskName/PathCantHaveRegex.htm

Labels (1)


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.


I am getting the message as "The selected set contains file type that have been configured for exclusion from Policy assignment. "[XXX as Policy name] will be assigned to non-exclused file types only " when I am trying to map the redundant documents to the policy with approver. I never updated any where to exclude any file type and May I know the triggering point and what it means? So the documents excluded will remain in the redundant list after dispose once approved? thx


What do you mean by 'when I am trying to map the redundant documents to the policy with approver.'

Are you just manually applying policy to your redundant data and seeing this error?
Please confirm the exact steps you are taking to reproduce the error and send a screenshot of the message also.


Yes, Keith. I manually select all items from my redundant list [ I did grouping some 10 individual repositories] mapping my Policy with approver. During the policy assignment getting this message as below. Actual duplicate count in my list is "558917". But document assigned to the policy is "558430". So trying to figure what documents excluded and why as I never setup any exclusion in the repository level or policy level. is that any way to check? 

Redundant_PolicyMapping_Delete With Review.PNG

Does the category associated with the 'Delete with Review' policy have any file type exclusions in the Field Text Training? e. g File Type NOT pdf

If not, please open a support ticket for this so we can spend more time to investigate.




Thanks Keith. Will do repository by repository rather than group to figure it out the files belongs to which repository is excluding and why. It is easier for me to narrow down and I will reject all the items from Policy as I set the approver.

BTW - For the redundant , to dispose any other way you can suggest other than What I mentioned above? thx


Still we can able to assign the Documents to the policy once the Policy Execution rejected by the Approver? I rejected the policy to be dispose and all showing as rejected. 

Again, When I back to the repository and select the documents and trying to assign to policy, it is not assigning. However, still it is showing the old policy name. Why is that behavior and how to dispose or reassign to policy for the rejected policy items?. 

Note: Since it is rejected , I am unable to "Remove Policy from an item" as well. I can see the query matches the items reject as well.

select * from [ControlPointMetadata].[DocumentPolicy] where ExecutionStatusCode='RV-R';


We are moving off topic from the original 'Exclude a file from scan' topic posted above.

Please raise a support ticket for your Policy issues and we will investigate this for you.

Note: removing policy from items in Review Rejected state is currently not possible via the UI. Please request the RemovePolicyFromRejectedDocs.sql script from support.



As Keith explained, we are covering a lot of ground on this thread.

For extensive analysis and support, please raise a support ticket and let us know the number.




Thanks Keith, I have raised the support ticket

Top Contributors
Version history
Revision #:
2 of 2
Last update:
‎2020-04-30 13:22
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.