On Tuesday, November 12, as part of a company wide initiative to bring all corporate websites under the OpenText brand, the Community will be down briefly around 11am Eastern / 8am Pacific as we transition to a new domain name.  The community will be offline while we make the change and when it comes back online it will be located at community.opentext.com and the old domain will redirect to this new location.  Thank you for your patience as we make this important change.

Wikis - Page

Exclude a file from scan

1 Likes

ISSUE:

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

HOW TO STEPS:

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.

PathCantHaveRegex0=.*thumb\.db
PathCantHaveRegex1=.*\.(pdf)

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:

How To-Best Practice
Comment List
Parents
  • I'm not aware of anything being audited however we have instead introduced the option for a review when setting up a policy. If you set a mandatory review for the policy that will ensure all docs the policy was applied to enter 'Awaiting Review' state.  The authorised reviewer(s) must then approve or reject the review before the policy will execute. Without this review being approved no docs would ever be destroyed by accident.

    The Execute Policies.log will show a count of docs awaiting review at any given time.

    e.g.

    25/11/2020 23:37:56 [7500] Info SqlDiscoverer 'delete with review' (7), phase 'Dispose' (7) : 1 documents awaiting review

    So if files are missing you know who to contact - the designated reviewers since they had the final say and must have approved the review. The relevant connector delete.log will also show when the delete(s) took place if they were approved.

    One further thought is we do offer a facility to notify policy approvers via email.
    You could get this email sent to an address that is always saved. That way you have a record of who was emailed to approve reviews etc.

Comment
  • I'm not aware of anything being audited however we have instead introduced the option for a review when setting up a policy. If you set a mandatory review for the policy that will ensure all docs the policy was applied to enter 'Awaiting Review' state.  The authorised reviewer(s) must then approve or reject the review before the policy will execute. Without this review being approved no docs would ever be destroyed by accident.

    The Execute Policies.log will show a count of docs awaiting review at any given time.

    e.g.

    25/11/2020 23:37:56 [7500] Info SqlDiscoverer 'delete with review' (7), phase 'Dispose' (7) : 1 documents awaiting review

    So if files are missing you know who to contact - the designated reviewers since they had the final say and must have approved the review. The relevant connector delete.log will also show when the delete(s) took place if they were approved.

    One further thought is we do offer a facility to notify policy approvers via email.
    You could get this email sent to an address that is always saved. That way you have a record of who was emailed to approve reviews etc.

Children
No Data
Related
Recommended