Pug-2017 - General questions on app behavior

[steveboucher]

The following are questions or minor issues - this is a sample application - it doesn't have to be perfect! The issue is: How polished should it be?

1. The initial screen, aka the landing page or splash screen is titled: "Welcome to PUG 2017 Demo Application" and contains 4 icons that the use can use to navigate to Main, Management, Reports and Sales modules. My question is, once you choose a module, there is no navigation back to the splash screen. The only way back is via the browser's back button. Is this expected? There is no loss of navigation as the module screen contains navigation to the other modules.

2. In Management -> SalesRep. The Year Quota field is a summation of each month's sales. Looking in KUIB-UI-Builder, I could not find where this calculation was defined. Could you point out how this was done? Also, I don't understand the use of the term "Quota" as used here. Quota to me indicates a goal to achieve, yet here it is used to indicate total sales. Is this OK?

3. Sales -> Customer Orders. Recommend additional validation on data input. For example, add drop-down selection for Order Status and Carrier. Currently these 2 fields are free form. A specific list might be preferable. Also shouldn't OrderNum be auto-assigned? You can enter any number.

4. Sales - Customers. The list of customers includes location information, specifically the "State". Some of the customers are foreign and part of their location defaults into the "State" field. Ok, but edit or create a new customer and you are limited to selecting only US states. Doesn't support international locations.

[maurar3]

My responses below:

1.) This is expected behavior, as you can still navigate to other parts of your app via the left-hand panel.

2.) The YearQuota field is a sum of the salesrep's monthly quotas. This field is part of the resource's schema, and hence, specified in the catalog. The calculation (the totaling of the Month Quota fields)
is done in the BusinessEntity..

3.) Good ideas, Steve. We can do in future app, or update this app at later time.

4.) Yes, true. Maybe something we can address in future.