Location Specific Customization Keys 

Follow

The Ares Customization Manager supports customization keys that are specific to a given Processing Location.

Not all Customization Manager keys can be specified for a particular Processing Location. If a key does not have an option to indicate a specific Processing Location, the setting will affect all Processing Locations.

Processing Location Dropdown

You can change the Processing Location for one or more items using the Change Processing Site command. This button is located on the ribbon of open status queues as well as basic and custom search results grids. Click to choose the result(s) you want to change, click the Change Processing Site icon and choose the new site. The items will be moved to the processing site you selected.

The (DEFAULT) option indicates that you are not working with a specific Processing Location.

  1. In the Ares Customization Manager, select the Default button.
  2. Select the Processing site you want to switch to.

See Configuring Processing Sites and Pickup Locations for information on adding and configuring Processing sites.

Processing Location Entries

In the Tracking grid shown in every customization key, the Processing Location column is displayed.

Additionally, you can view the Processing Location of all Ares customization keys in the Customization table, found under System | General | Customization.

Creating Site-Specific Keys

Staff are able to create customization keys that are specific to a particular Processing Location. In the Ares database, the ProcessingLocation field will contain that Processing Location's site code.

  1. In the Ares Customization Manager, navigate to the Customization table under System | General.
  2. Click on the entry for the key you want to duplicate under another Processing Location.
  3. Click Copy Record. An Edit Row section will appear.
  4. Make any necessary changes, and select the new Processing Location from the dropdown menu.
  5. Click Save.

When Ares looks for the value of a customization key, it will consider the Processing Location in the context of the current operation. This is determined with the following priority:

  1. Is this an Item operation? If so, use the Item's Processing Location.
  2. Is this a Course operation? If so, use the Course's default pickup site's default Processing Location.
  3. Is there a Processing Location context for the current application? If so, use that. This is currently only relevant for the Ares client, which works against a selected Processing Location for purposes of processing items.
  4. There is no Processing Location for the current context.

Ares will then look for a site-specific version of the customization key it's retrieving.

 

Questions?

If this article didn’t resolve your issue, please take a moment and answer a few questions to help improve our documentation:

Feedback