Enabling ControlPoint Insert Configuration

2 Likes

ISSUE:

ControlPoint allows mapping fields with the target repositories of information. With that, you can send metadata captured by ControlPoint to the target application. For example, you collect social security numbers from documents with entity extraction function; Insert Configuration will allow you to send this value to Content Manager when you do an action to create a record in CM. Insert Configurations are defined in ADMINISTRATION.

Insert Configuration is disabled by default on a new installation.

HOW TO STEPS:

Go to the scheduler install folder, by default: C:\Program Files\Micro Focus\ControlPoint\Engine\Scheduler.

Edit the configuration file ControlPointTimer.exe.config.

Look for…

<add key=”InsertConfigEnabled” value=”false” />

Change it to…

<add key=”InsertConfigEnabled” value=”true” />

A restart of the ControlPoint Engine service is needed to pick up the change.

Note: To map field with Content Manager you can have a look at this post.

Labels:

How To-Best Practice
Comment List
Parents
  • I'm finding success in mapping certain CP fields to fields in CM (CPLOCATION or Tags work great). But fields such as AU_DOCUMENT_KEYWORDS_STRING is a field that does not appear to be exported. We also do not see any errors in the process.  It is an IDOL field that is indexed during a Full Content index and pulled from the Tags field in the File property Details. The field does not appear to be ported over to any other field in the Advanced properties.

    Are there fields that cannot be exported from CP, or any specific configuration to get ready to be exported then mapped?  

Comment
  • I'm finding success in mapping certain CP fields to fields in CM (CPLOCATION or Tags work great). But fields such as AU_DOCUMENT_KEYWORDS_STRING is a field that does not appear to be exported. We also do not see any errors in the process.  It is an IDOL field that is indexed during a Full Content index and pulled from the Tags field in the File property Details. The field does not appear to be ported over to any other field in the Advanced properties.

    Are there fields that cannot be exported from CP, or any specific configuration to get ready to be exported then mapped?  

Children
No Data
Related
Recommended