Manual Jobs on Defined Sets

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

To run a manual job, you must have roles that enable you to:
1) Access the Run a Job – Select a Job to Run page, and
2) Run the job.

To access the page, you must have one of the roles that is listed in Roles column of the Manual Jobs by Content Type table.

Only jobs that you can run (that are available to your user roles) appear on the Run a Job – Select Job to Run page.

This section presents how to run a job manually on a defined set of objects, such as a list of PO lines or physical items.

To run a job on a set:

If there are no sets defined or if you require a specific set for the job you are running, you must first define the set. For information on defining sets, see Managing Search Queries and Sets.

On the "Run a Job – Select Job to Run" page (Admin > Manage Jobs and Sets > Run a Job), find the job you want to run. Note that each job requires you to have a certain role to view the job in the table; see Manual Jobs and Their Relevant Parameters.

Run a Job - Select Job to Run Page

For each job, the following information appears:

Run a Job – Select Job to Run Page Columns
Name	Description
Name	The name of the job.
Description	A description of the job.
Content Type	The type of set that the job processes. For example, physical titles, digital titles, bibliographic records, and so forth.
Type	The type of request or job that runs (for example, export, move items, or requests).

Select a job and select Next.
The Run a Job - Select Set page appears.

Run a Job - Select Set Page
Select a set and select Next.
If there are parameters to set, the Run a Job - Enter Task Parameters page appears. If there are no parameters to set, the workflow skips this page.

Run a Job - Enter Task Parameters (Example) Page

The number of members in the set that you selected in the last step appears on this page. Verify that this number is similar to what you expected based on the selected set.

Enter the required parameters. To see the parameters required to configure for each job, see Manual Jobs and Their Relevant Parameters.
Select Next. The Run a Job - Review and Confirm page appears.

Run a Job - Review and Confirm (Example) Page
Optionally, enter a more descriptive job name to replace the default one. The name identifies this job for editing and monitoring.
- The number of members in the set that you selected in the last step appears on this page. Verify that this number is similar to what you expected based on the selected set.
- For more information on the API Information section, see the Developer's Network documentation.
Review the job information and:
- Select Submit and select Confirm in the dialog box to run the job.
- Select Back to go back and correct any information that you entered.
  When you select Back, you are taken back one page at a time. You can select Back on any page to go back to the previous page.
- Select Cancel to delete what you entered and return to the home page.

Manual Jobs and Their Relevant Parameters

The following table lists the available manual jobs that can be run on defined sets. To run the job, you must have one or more of the roles in the Roles column.

Manual Jobs by Content Type
Name	Content Type (set type)	Type	Description and Parameters	Roles
Update/Notify Users	User	Users	Updates parameters for users and/or notifies users. This job lets you add roles to users. For roles that have the role parameter "Read Only", this job does not let you set that parameter to selected when adding the role. This job does not let you add roles with other types of role parameters. For more information on this job, watch: the Bulk Actions on a Set of Users video (4:33 mins). Parameters: For the field Added/changed field: By user account type: Handles specific fields according to the account type (internal or external). For example, if using the job to add a block, the block is added as external for external users and as internal for internal users. Internal field values are not overridden during an SIS update. External field values are overridden during an SIS update. Internal: Handles specific fields as if they are internal, even when belonging to an external account. For example, if using the job to add a block, the block is added as internal even if the block is being attached to an external user. Internal field values are not overridden during an SIS update. The fields affected by this setting are: User group Campus Resource sharing library Add block type Add statistics category Add note To change internal users to external, or vice versa, select Set Account To and the relevant target account type. If external users are changed to internal users, the users’ passwords are reset to 10 random characters. If you select Don't Generate Password, no password is set; this field appears only if you select one of the Set Account To options. To email/notify users, select Send Notification to User and select the notification type. To configure notification types, see Configuring User Notification Types and the User Notifications Letter in ConfiguringRapido Letters. The roles that cannot be updated by this job are: Circulation Desk Operator Circulation Desk Operator - Limited Circulation Desk Manager Requests Operator Work Order Operator Receiving Operator Receiving Operator Limited Fulfillment Services Operator	User Administrator, User Manager