YaST/AppArmor/RoughDraft-UI-Redesign

From openSUSE

AppArmor Reporting Redesign

These are options for the new design of the AppArmor reporting forms. The current plan is to redo the main report scheduling form, and make minor changes to some of the others, but the feedback here could change those plans.

Design Considerations

The idea is to have information presented and editable without users having to do a lot of clicking, or to have to go back and forth between forms to make decisions, and then make changes. The new form mockups were made in QT Designer, so the look is a little different than in YaST. (And the bottom row of buttons will be changed to the YaST standard, "Back", "Abort", "Finished" as appropriate.)

The Current UI (Old Design)

AppArmor Current Report Design

Reporting is designed to act like a management console, with the main screen being the report scheduling and management form. This is intended as a launching point to manage all aspects of reporting:

1. Adding, editing, deleting reports
2. Altering report execution schedules
3. Running reports
4. Viewing previously created reports

Main Page - Report Schedule Management

This is the form that will need the most redesign. It may end up looking more like YaST/Printer but most of the redesign ideas are covered at the end of this document: YaST/AppArmor#Report_Scheduling_UI_Redesign.

Adding an SIR Report Page 1

This is the form for setting the schedule of the cron job that generates reports. The "Day" and "Month" values will be replaced with a radio button group for choosing between "Daily", "Weekly", "Monthly".

Adding an SIR Report Page 2

This is where we create search filters for the AppArmor events db.

Running an ESS Report

Generate simple stats about AppArmor events. There might not be any change on this form. The common "Forward", "Sort", etc. buttons. could be removed. For the "View All" function, you might get into a situation where you have thousands of hosts, and in that case you would need these buttons. Also, leaving them might help create a feeling of consistency across the reporting forms?

Running an SIR Report Page 1 (Setting Filters)

Running an SIR Report Page 2 (Output)

The "First Page" and "Last Page" buttons are going to be removed, because the same functionality exists in the "Go to Page" button.

Running an Applications Audit Report

Running an ESS Report

Running an SIR Report Page 1 (Setting Filters)

Running an SIR Report Page 2 (Output)

Viewing Archived Reports (Selection)

Viewing Archived Reports requires several steps.

1. Form 1 - The user selects the "View Archive" button from the main scheduling screen.
2. Form 2 - The user selects the type of report (AUD, ESS, SIR) and all reports or a single report.
3. Form 3 - (For archived SIR reports only) The user selects optional filters. (same as "Run Sir Report", page 1)
4. Form 4 - The resulting report is displayed. (same as "Run Sir Report", page 2)

The only planned change for this is to remove the "Choose a Report Type" field, and use input from the initial schedule form to determine what type of report the user wants to look at. This change would make this form act like the "Run Report" form

Viewing Archived Reports (Output)

Report Scheduling Redesign (New)

New Scheduling UI - Option 1

I prefer this form, though the buttons may make it a little confusing. The "Enable" drop-down could be replaced with a button that switches between "Enabled/Disabled" or "Off/On" depending on the selected report. Another possibility is moving the enable/disable toggle to the Edit form.

New Scheduling UI - Option 2

This is similar to the current form, but simplified, and is a better match for configuration in cron.

New Scheduling UI - Option 3

This form assumes that running and viewing reports would be executed through a different interface. Great for simplification, but it would add more icons to the growing list of top-level items in the "Novell AppArmor" listing.

New Scheduling UI - Option 4

I was just shown this: YaST/Printer. I'll add screens of a form using this template (with one tab for report scheduling, and one tab for running/viewing reports soon.