About this task
Your decision plan rules need to set fields that are mapped
to user-defined metadata properties in
Content Collector. These user-defined metadata
properties can then be used in decision points or tasks in the
Content Collector task route to determine
how to process documents, such as to file a document into a specific
folder or assign an expiration date.
Tip: If you plan to
use Classification Center to review
how documents were classified, use the IBM Content
Manager or IBM FileNet® Content Manager decision plan actions
that are provided in Classification Workbench.
For example, use the Set the item type in IBM Content
Manager action that
populates the ContentManager:SetItemType field with the suggested
item type of the document. In Content Collector,
map the ContentManager:SetItemType field to a user-defined metadata
property. Then configure the Content Collector task
route to use this metadata value when setting the item type of the
document when it is added to the repository. By using these actions
that are designed for use by Classification Center in IBM Content
Manager or IBM FileNet Content Manager repositories, you can
use Classification Center to reclassify
the documents. However, you might need to create a different version
of the decision plan to be used by Classification Center. The triggers in the
decision plan for Classification Center might
need to differ from the triggers that were used in the decision plan
to classify the content during ingestion by Content Collector. For example, the content
might have different fields when it is sent from the email server
or the content repository.
When you create decision plan
rules to populate fields that are needed by Content Collector to process documents, such
as to set the item type, ensure that you define rules to assign a
default value to the field or flag documents that require manual review.
If
you create decision plan rules to set dates in
Content Collector, such as for setting the
expiration date in
IBM Content
Manager repositories,
use the
Set a content field to a date for IBM Content
Collector action that
is provided in
Classification Workbench to
convert the dates to the
Content Collector internal
date format.
Content Collector converts
dates from this internal format to the appropriate format according
to the target repository.
Tip: The
Set a content
field to a date for IBM Content
Collector action
converts dates to the internal date format for
Content Collector version 2.2 or later. If
you use
Content Collector version
2.1.1, complete the following steps to convert the dates to the correct
format:
- After you configure the Set a content field to a date
for IBM Content
Collector action,
click Convert to advanced actions. The action
is converted to two Set content field advanced actions.
- Edit the two advanced actions. Select each advanced action and
click Edit. In the Edit Action window,
click Edit value and modify the value.
- For the value of the first advanced action:
export_date(date('now')
, '+yyyy-MM-dd\'T\'hh:mm:ss:SSSZ-')
Add a zero before
the milliseconds value (that is, change :SSSZ to :0SSSZ).
For example:
export_date(date('now') , '+yyyy-MM-dd\'T\'hh:mm:ss:0SSSZ-')
- For the second advanced action:
substring($original_date_field,1,27)
concat ':' concat substring($original_date_field,28,3)
- In the first substring value, change $original_date_field,1,27 to $original_date_field,1,28.
- In the second substring value, change $original_date_field,28,3 to $original_date_field,29,3.
For example:substring($ICC:ExpirationDate,1,28) concat
':' concat substring($ICC:ExpirationDate,29,3)
