Job Type Input Parameters

Job Type	Parameter Name
Purge	Purge Execution Mode: Select the purge execution mode from the drop-down list. The following modes are available: Event History History With Force Record Versions Record Versions With Force Record Versions (Golden Copy) Deleted Records Metadata Versions Record Synclog Purge Bounded Type: For details, see Types of Bounded Purge. Purge Policy: Select the purge policy (Light, Medium, Aggressive, or Custom). The default value is Medium. For more information, see Purge Policies. Parameters: Bounded Purge Time Interval: Enter time in seconds. Bounded Purge Record Count: Enter the number of records to be purged. Retention Days: By default, the period of retention is 365 days. The default is 90 days in the case of Event History and 0 in the case of Record Versions mode. This field is displayed if you have selected the History with Force, and Record Versions modes. Incremental: Click the check box if you want the purge to be worked incrementally to make sure that the purge is done only for the delta since the last purge. Repository Name: Enter the repository name. This field is displayed if you have selected the Repository, Record Versions, Metadata, and Metadata Versions modes. Hints: Enter the hint characters. The allowed hint characters are A D, F, L, M, S, G, P, and R. For information about hint characters, see Hint Characters. This field is displayed if you have selected the Repository mode. Data Source Name: Enter the data source name. This field is displayed if you have selected the Metadata and Metadata Versions modes. Version To Retain: Enter the version number that you want to retain in purge. For information about version to retain, see Delete Record Versions. This field is displayed if you have selected the Record Versions mode. Interval: Enter an interval in days and must be a positive integer. For information about interval, see Interval in Record Versions. This field is displayed if you have selected the Record Versions mode.
Duplicate Detection	Search Entity: Select the Table or View option. For a single repository, select Table and for multiple repositories select View. View Name: Enter the view name which is indexed with the same repository and attributes. View name is an index entity name. Specify the View name if you have selected the search entity type View. Search Mode: Select the Incremental or Complete mode. This is a mode of execution for search. Complete: For the first time search, all confirmed records are added. Later, when next job runs, search is performed only on the added records between the interval of the last and current jobs. Incremental: Specifies that only new or changed data is searched except in one case, that is, if a scheduler duplicate detection job was not executed earlier, the server starts with the Complete mode and the search is performed on the entire data. Data Provider Class: Enter the data extractor helper class name. It retrieves records from the golden copy table for the specified repository ID. For example: `DupDetectJobDataExtractor`. Match Threshold: Select the threshold score for matching. Specify a value between 0 to 1. For example, `0.2`, `0.5`, and so on. By default, the score is `0.6`. Repository Name: Enter the existing repository name. Root Repository: Select the check box if the repository is a root repository. Match Attributes: Enter the name of matching attributes. You can enter multiple matching attributes. You can perform search based on these attributes. Weight: Enter a decimal number between 0.00 to 1. This is the weightage of an attribute for matching records. Display Attributes: Enter the name of attributes that should be displayed in the scheduler duplicate detection report. Relationship: Name: Enter the name of a relationship. Related Repository: Enter the name of the related repository. Note: To complete the Duplicate Detection process, you must perform some prerequisites. For information see the chapter, "Scheduler Duplicate Detection Process" in ibi MDM Customization Guide.
Index Entity Checkpoint	Checkpoint all Index Entities: Select the check box if you want perform search on all index entities. Index Entity Name: Enter the name of an index entity on which you can perform the search. Specify a comma separated list of index entity names to checkpoint multiple index entities. To checkpoint all index entities, specify an asterisk (*). Note: Ensure that the index entity names that you specify in this job should match with the index entities defined in the `IndexerConfig.xml` file and the ibi Patterns - Search server is up.
Trigger A Workflow	Directory Name: Enter the directory name to create a trigger file in a specified location. For example, $MQ_COMMON_DIR/directoryname/Prefix.extension. Prefix: Enter the file name of a trigger file, which is required to fire the workflow. Extension: Enter the extension of a file. For example, .xml.
Hierarchy Lock Expiry Scheduler	Expiry Interval in Hrs: Specify the expiry interval time in hours to unlock the invalid locks set on the hierarchy.
Linkage Cleanup Scheduler	Hierarchy Names: Specify a comma separated list of hierarchy names to delete linkage data in multiple hierarchies. Enterprise Name: Specify an enterprise name in which the hierarchy is created.
Right to be Forgotten Scheduler	Repository Name: Enter the repository name from which you want to delete records. To delete records from all repositories, specify an asterisk (). An asterisk () value indicates that records from all repositories (excluding repositories that you specified explicitly for custom attributes) are considered for deletion. Attributes: Enter any record attribute and its value. The supported data types for the attributes are boolean and string. You can set different values based on your requirement. For example, ConsiderForExpiry Deprecated Neglect Discard Note: To delete records from multiple repositories, click Add Repository. Currently, supports only one attribute per repository. In the Attributes section, you must enter a name and value. Empty values are not considered for deletion of records.

Purge

Purge Execution Mode: Select the purge execution mode from the drop-down list. The following modes are available:
- Event History
- History With Force
- Record Versions
- Record Versions With Force
- Record Versions (Golden Copy)
- Deleted Records
- Metadata Versions
- Record Synclog
Purge Bounded Type: For details, see Types of Bounded Purge.
Purge Policy: Select the purge policy (Light, Medium, Aggressive, or Custom). The default value is Medium. For more information, see Purge Policies.
Parameters:
- Bounded Purge Time Interval: Enter time in seconds.
- Bounded Purge Record Count: Enter the number of records to be purged.
- Retention Days: By default, the period of retention is 365 days. The default is 90 days in the case of Event History and 0 in the case of Record Versions mode. This field is displayed if you have selected the History with Force, and Record Versions modes.
- Incremental: Click the check box if you want the purge to be worked incrementally to make sure that the purge is done only for the delta since the last purge.
- Repository Name: Enter the repository name. This field is displayed if you have selected the Repository, Record Versions, Metadata, and Metadata Versions modes.
- Hints: Enter the hint characters. The allowed hint characters are A D, F, L, M, S, G, P, and R. For information about hint characters, see Hint Characters. This field is displayed if you have selected the Repository mode.
- Data Source Name: Enter the data source name. This field is displayed if you have selected the Metadata and Metadata Versions modes.
  - Version To Retain: Enter the version number that you want to retain in purge. For information about version to retain, see Delete Record Versions. This field is displayed if you have selected the Record Versions mode.
  - Interval: Enter an interval in days and must be a positive integer. For information about interval, see Interval in Record Versions. This field is displayed if you have selected the Record Versions mode.

Duplicate Detection

Search Entity: Select the Table or View option. For a single repository, select Table and for multiple repositories select View.
- View Name: Enter the view name which is indexed with the same repository and attributes. View name is an index entity name. Specify the View name if you have selected the search entity type View.
- Search Mode: Select the Incremental or Complete mode. This is a mode of execution for search.
  - Complete: For the first time search, all confirmed records are added. Later, when next job runs, search is performed only on the added records between the interval of the last and current jobs.
  - Incremental: Specifies that only new or changed data is searched except in one case, that is, if a scheduler duplicate detection job was not executed earlier, the server starts with the Complete mode and the search is performed on the entire data.
- Data Provider Class: Enter the data extractor helper class name. It retrieves records from the golden copy table for the specified repository ID. For example: DupDetectJobDataExtractor.
- Match Threshold: Select the threshold score for matching. Specify a value between 0 to 1. For example, 0.2, 0.5, and so on. By default, the score is 0.6.
Repository Name: Enter the existing repository name.
- Root Repository: Select the check box if the repository is a root repository.
- Match Attributes: Enter the name of matching attributes. You can enter multiple matching attributes. You can perform search based on these attributes.
- Weight: Enter a decimal number between 0.00 to 1. This is the weightage of an attribute for matching records.
- Display Attributes: Enter the name of attributes that should be displayed in the scheduler duplicate detection report.
- Relationship:
  - Name: Enter the name of a relationship.
  - Related Repository: Enter the name of the related repository.

Note: To complete the Duplicate Detection process, you must perform some prerequisites. For information see the chapter, "Scheduler Duplicate Detection Process" in ibi MDM Customization Guide.

Index Entity Checkpoint

Checkpoint all Index Entities: Select the check box if you want perform search on all index entities.
Index Entity Name: Enter the name of an index entity on which you can perform the search. Specify a comma separated list of index entity names to checkpoint multiple index entities. To checkpoint all index entities, specify an asterisk (*).
Note: Ensure that the index entity names that you specify in this job should match with the index entities defined in the IndexerConfig.xml file and the ibi Patterns - Search server is up.

Trigger A Workflow

Directory Name: Enter the directory name to create a trigger file in a specified location. For example, $MQ_COMMON_DIR/directoryname/Prefix.extension.
Prefix: Enter the file name of a trigger file, which is required to fire the workflow.
Extension: Enter the extension of a file. For example, .xml.

Hierarchy Lock Expiry Scheduler

Expiry Interval in Hrs: Specify the expiry interval time in hours to unlock the invalid locks set on the hierarchy.

Linkage Cleanup Scheduler

Hierarchy Names: Specify a comma separated list of hierarchy names to delete linkage data in multiple hierarchies.
Enterprise Name: Specify an enterprise name in which the hierarchy is created.

Right to be Forgotten Scheduler

Repository Name: Enter the repository name from which you want to delete records.
- To delete records from all repositories, specify an asterisk (*). An asterisk (*) value indicates that records from all repositories (excluding repositories that you specified explicitly for custom attributes) are considered for deletion.
Attributes: Enter any record attribute and its value. The supported data types for the attributes are boolean and string. You can set different values based on your requirement. For example,
- ConsiderForExpiry
- Deprecated
- Neglect
- Discard

Note:

To delete records from multiple repositories, click Add Repository.
Currently, supports only one attribute per repository.
In the Attributes section, you must enter a name and value. Empty values are not considered for deletion of records.