Administrative Services Maintenance Screen

Purpose: The Administrative Maintenance screen includes all SUITS Administrative functions to be performed by designated SUITS Administrators. From the Administrative Services menu, SUITS users, Security Roles, and Resources are managed. Additionally, System Availability, Audit Logs, and Batch Job Instances are modified and monitored.

The Administrative Services menu is compiled of 5 panels: Security, System Management, Batch Process Maintenance (Job Schedule), Exception Processing, and User Preferences Maintenance. The SUITS administrative functions are housed within each of these panels. Each panel and the functions they house are listed below.

 

Security:

Security Administration is the maintenance of user profiles, roles, resources, and access. It starts with the concept of a “resource”. A resource is a form (screen), a user interface control (screen element the user can interact with, such as a field or tab) on a screen, an action the user can take on a screen (generally a button the user can click), or a workflow process. For a resource to be meaningful, the element (or elements) it defines must be developed in the System. For example, nothing prevents you from creating a resource for a screen called “Test Screen”, but assigning that resource won’t actually do anything if “Test Screen” isn’t really part of the System. Please refer to development training for creating user interface elements and linking them to resource levels.

 

System Management:

The SUITS System is dependent on a number of properties to function correctly, so the System also has functionality for creating, maintaining, and viewing those management properties.

Roughly in order from least granularity to most, the available System administration functions are:

      System management.

      System paths.

      Codes.

      Messages.

 

Batch Process Management:

      A job schedule, also called a batch, is a collection of steps the System executes in sequence to accomplish a business goal, such as processing a file or generating a report. The System code uses a batch handler to run all batch jobs. The batch handler contains instructions for each step of running the job. It refers to the steps by their names and IDs, which must be configured on the job schedule in the System. If the batch handler has a new batch, you must create a job schedule in the System so the batch handler has records to refer to.

 

      Besides the schedule and step IDs, job schedules define what triggers the System to execute the job (either an event such as the System detecting a received file or a user clicking a button; or a date and time based on a schedule type), whether the System will run the job when triggered, the job’s priority level when the System is running multiple jobs, whether an instance of the job running can or cannot be canceled before it finishes, email address(es) for notifications about the job, any dependency on other jobs, and any other notes describing how the job functions.

 

Related Links

      Create SUITS Portal User Record

      Create a New SUITS Internal User Record

      Collection Staff County Assignment

      Modify Existing SUITS Role

      Create New SUITS Role

      View SUITS Audit Log

      Maintain Messages and Banner Messages

      Change System Availability

      Create a System Path

      Manage Code Tables

      Update a System Message

      Setup and Maintain Resources

      Manually Run a Job Schedule

      Job Schedule Instance

      Job Service Instance

      Processing Exceptions

      User Preference Maintenance

      Manually Generate Correspondence

      Update Correspondence Template