Listed below are the available configuration settings for the inventory application.

ADS Config

This ADS configuration allows the enabling of external authentication (active directory service) in Inventory.   This option will support up to three ADS domains.  If multiple ADS domains are configured, each one is attempted in order. 

The 'enabled' box on the ADS Configuration domain must be checked and the user's account in SYSTEM>User must have the 'external authentication' box checked as well in order to use ADS.  Users that don't have the 'External Authentication'  box checked will authenticate locally. 

For example, consider the user "miller" in a domain "mcoecn.org".   If the "ADS Domain" field is left blank, then the user must specify the fully qualified name of "miller@mcoecn.org" when logging in and the username field in user's account must contain "miller@mcoecn.org".  However, if the "ADS Domain" field contains "mcoecn.org", then the user can login without specifying the domain, and the profile username is simply "miller".

For this reason, when configuring multiple domains, it is strongly recommended that only one domain specify an "ADS Domain".  The others should be blank to force the user to specify the fully qualified name to prevent collisions.  If a default is provided for more than one domain, and a user "miller" exists in both domains, they will share the same profile in the application.

More Information on ADS Configuration 

Please refer to the 'Configure' section of the /wiki/spaces/rtd/pages/2752939 for more information.

Password Config

Allows ADMIN user to make changes to user password configuration. NOTE: this will affect all users in the application.

• alter the minimum length of a password and optionally require mixed case and/or numeric values as part of the password
• alter password expiration.  Sets the number of days between required password changes.  Default value is 90 days.  If set to zero, passwords will not automatically expire. 
• Pre-Expired Password:  If a user's password is changed by an administrator, should the password be immediately expired?  This will require the user to change the password on the next login.  Does not affect users who hold the 'ADMINISTRATORS' role.

Email Config

• Default Administrator Address is not being used at this time so this can be left as "root."
• Default From Address will be used when sending emails from the application (via the Job Scheduler).
• Enable Start TLS is an email security protocol. For example, the box should be checked if the district has MS Exchange Office 365 with SMTP authentication enabled. 
• The SMTP Host and Port information must also be entered for emails to be sent. Generally, the Port and SMTP Host information would be known by the ITC.

Jobs

When the Inventory FYE Report Bundle is triggered, the ability to view the job can be found here.  Other jobs (i.e. scheduler cleanup job) can also be viewed.  Once all reports for the FYE Inventory report bundle are generated, zipped and the emailed, the status will show 'completed'.  Click 'refresh' on the job scheduler grid to view the most up-to-date status.

Migration Import

This is a mass load option for non-migrating districts allowing ITC staff to import data for districts starting on Inventory without the fiscal year restrictions that apply to the System>Import options, allowing prior year data to be imported into the application.    

• This option will allow you to upload CSV files for acquisitions, items or dispositions. The data formats and headers for this option are the same as documented in the System>Import chapter.
• The 'Item' import type, by default, will also create any Core codes that does not exist.  For example, fund, function, location, etc.
• 'Create Acquisition Records' will be checked by default when selecting the 'item' import type thus creating the associated acquisition transaction.  Districts can choose not to create an associated acquisition record by 'unchecking' the box.  Used caes
• to optionally create the acquisition when the item is created, however this will happen for all items in the CSV file being imported.  Separate imports (files) should be used if necessary, one for items they want acquisitions created for automatically and one for items they do not want acquisitions created for automatically.