3.7 Batch operations on Items
Many of the Items generated in the course of day-to-day operation do not require any further investigation or action by the operator. To reduce operator workload, the batch operations on Items function allows you to deal with several of these Items at a time by changing the status of multiple Items in a batch.
Note that, when using an Item storage database, you cannot perform batch operations on the Items stored in the database.
The following table shows the batch operations you can perform on Items:
|
No. |
Operation |
Description |
|---|---|---|
|
1 |
Batch approval of Items |
Changes the status of Items to Acknowledged# (JIMSD_STAT_APPROVED). |
|
2 |
Batch closure of Items |
Changes the status of Items to Close# (JIMSD_STAT_CLOSE). |
- #
-
This is the default status name. In some environments, custom names might be used. For details, see 3.15 Status management.
You can perform batch operations on Items from the Batch Operation menu in the following windows:
-
Main window (Item list)
-
List of item search results window
You need to enable batch operations on Items in a property file before you can perform the tasks described in this section. The user who performs the batch operation must also have the appropriate access permissions for the Items he or she is working with. Each of the required settings is described below.
- Settings that allow batch operations on Items
-
The following settings must be entered before you can perform batch operations on Items:
-
Settings that enable batch operations on Items#
-
Settings that specify which users can perform batch operations on Items#
-
Setting that specifies how many Items can be edited at a time
- #
-
Separate settings are required for batch approval and batch closure of Items.
The settings associated with batch operations on Items are entered in the system property file. For details on the system property file, see System property file (hptl_jp1_imss_main_setting.properties) in Chapter 13. Definition Files.
-
- Access permissions required for batch operations on Items
-
The access permissions required to perform batch operations on Items depend on the batch operation being performed. If a person in charge who lacks the correct access permissions attempts to perform a batch operation on Items, the operation will fail.
- Access permissions required by users who perform batch operations on Items
-
The following table shows the access permissions a user must have to perform batch operations on Items:
Table 3‒39: Access permissions required for users who perform batch operations No.
Operation
Permissions required prior to performing batch operation
Permissions required when performing batch operation
1
Batch approval of Items
-
Permissions to view Items
-
Edit permissions for the Item or access permissions for the original status
Permissions to approve Items
2
Batch closure of Items
Permissions to close Items
-
- Access permissions required by person in charge of Items
-
When performing a batch operation on Items, either of the following access permissions must be assigned to the user who is in charge of the Item or to the role assigned to the user:
-
Permissions to view Items and permissions to edit Items
-
Access permission for Items in Close or Acknowledged status
-
For details on access permissions, see 3.11 Item access control.
If the option to set view permissions for individual Items is enabled for the process work board, you can only perform batch operations on Items for which you are a view permission owner. For details on setting view permissions for individual Items, see 3.11 Item access control.
The subsections below describe the general procedure for batch operations on Items, and how to view and interpret the results of a batch operation.
- Organization of this section