Timed Updating of System Common "Choice XML"

When you design Business Data input field, you configure [Data types] of Data Items such as 'Numeric' or 'Date'. For example, you would set 'String type (Single line)' for "Customer phone number", 'Numeric type' for "Your Billing total".

Then, what if Data Input field for "Product Name" or "Name of the State"?

Most of the cases, 'Select type' will be set to the Input field. That is, it will save the labor of typing for the operator and will reduce data fluctuation, by using the selectable interfaces such as "Select Box" and "Check Box". (Assisting Data Input)

  <item value="h1" display="Espresso" />
  <item value="h2" display="Americano" />
  <item value="h3" display="Latte" />
  <item value="h4" display="Black Tea" />
  <item value="c1" display="Iced House Blend" />
  <item value="c2" display="Iced Tea" />
  <item value="c3" display="Organge Juice" />
  <item value="c4" display="Lemonade" />
  <item value="c5" display="Soda" />
  <item value="e1" display="Bagel" />
  <item value="e2" display="Oatmeal" />
  <item value="e3" display="Serial" />
  <item value="e4" display="Cheese Burger" />
  <item value="e5" display="Pan Cake" />
  <item value="m1" display="Prix fixe A" />
  <item value="m2" display="Prix fixe B" />
  <item value="m3" display="Prix fixe C" />

However, these Choices must be always maintained in the newest condition.

For instance, it is a same old story that "Renovating the cafe menu of all chain stores" at seasonal change, but it's tricky doing that. Only 'Select type' among the [Data types], needs maintenance.

I have been introducing samples of "How to manage 'Cafe Menu (Choices XML)' centrally" throughout the latest 3 articles.

• Two article before the last (choices that closed in business):
  "Cafe menu" (Choices XML) is referenced from multiple input field, within a certain business.
• The article before the last (choices that closed in business):
  "Cafe menu" (Choices XML) is referenced from multiple input field, within a certain business. (+ Filtered Category)
• The last (Choices used from the entire company):
  "Cafe Menu" (Choices XML) is referenced from the input field of various internal operations.

In this article, we make further consideration of "Maintenance of the Choice data". Now, we study about a Workflow for updating 'Choices XML' which is commonly used by the entire company, using [Service Task], a special automatic processing step for maintenance of Choices.

Incidentally, this "flow of updating the system-common setting" is an act of controlling the < business platform >. It can be said as strengthening of "internal control". That is, it can be said that a workflow system controls the < business > (Business Processing governance associated with IT), but on the other hand, this Business Process definition can be said that it controls further to the fundamental part. (General governance associated with IT)

[Cafe Menu Upgrading: "2. Display Test" screen]

Centrally Managing "Option List" Used in a Variety of Internal Business

There are great needs for centrally management in the system on the list of Options to be indicated. Subsequent to previous articles of the last and one before the last, we are going to study for the use of 'Optional Choices' in common, over the case of "Cafe menu" in 'restaurant chain business'.

• one before the last: The same 'Cafe menu' (Choice .XML) is referred by multiple input field (Select type).
• the last: The same 'Cafe menu' (Choice .XML) is referred by multiple input field (Select type). (+ Narrowing down the options by selecting a category)

In these examples above, 'Optional Choices to be used commonly' are managed in one file (Choices .XML). However, it is just a closed world of "Weekly report business" operation, that managing centrally the list to be indicated on "multiple input forms". In other words, it is just a "Operation oriented" central management.

• A1. Weekly Report: Select an item that sold well.
• A2. Weekly Report: Select an item that not sold well.

But this time, we consider Choices XML so to speak 'Cross- operational', that to be referred by input forms for other operations. The following is a business flow that each store reporting the "broken cookware" to the headquarter. The reports must include which item is affected by the lack of the cookware.

• B. Broken Report: Select items affected.

[Broken Cookware Report flow: "1. Enter Cookware Broken" screen]

Select from Main Class, Narrowed Down Choices

Following the previous article we are going to consider "weekly report in the coffee shop chain business".

In this coffee shop chain, you don't feel inconvenience in inputting operation to select "Menu", because the number of the menu is only 17 in total. However, if the number becomes 30 or 50, there will be some difficulties in making selection. I would like to think up some trick for the sake of data inputting without mistakes.

＜cafe-menu.xml＞

<items>
  <item value="h1" display="Espresso" />
  <item value="h2" display="Americano" />
  <item value="h3" display="Latte" />
  <item value="h4" display="Black Tea" />
  <item value="c1" display="Iced House Blend" />
  <item value="c2" display="Iced Tea" />
  <item value="c3" display="Organge Juice" />
  <item value="c4" display="Lemonade" />
  <item value="c5" display="Soda" />
  <item value="e1" display="Bagel" />
  <item value="e2" display="Oatmeal" />
  <item value="e3" display="Serial" />
  <item value="e4" display="Cheese Burger" />
  <item value="e5" display="Pan Cake" />
  <item value="m1" display="Prix fixe A" />
  <item value="m2" display="Prix fixe B" />
  <item value="m3" display="Prix fixe C" />
</items>

 
"Value attribute" is set in a Select form in HTML, other than Display name (display attribute). And "Main class code" is set in the "Value attribute" in this case. (H: Hot Drinks, C: Cold Drinks, E: Food, M: Prix Fixe)

So, I'm going to think a simple filter using this "Main class code". (Show hidden control using JavaScript)

[Data Items list screen]

Choices for both of Column A and B (Weekly report by store manager)

"Weekly Report" job in a coffee shop chain.

The manager of each store inputs "Report of store summary" by every Monday morning. Report contents are the following 6 items.

1. The number of customers of a week (Numeric type data)
2. Item which sold quite (Select type data)
3. Cause of Good sales (String type data)
4. Item which did not sell many (Select type data)
5. Cause of Bad sales (String type data)
6. The outcome of this week, and the goal for the next week (String type data)

Area manager at Headquarters checks the manager's report in the morning of Monday, and makes "comments" and "questions" to each one the report. An email goes to the store manager whose report has been commented. Also an email goes to the store manager whose report has been asked questions, and the store manager is required to input "Answer to the question from Headquarter".

In addition, it should be reported surely every week with minimum labor of making the report, because it is a day-to-day operation to be performed repeatedly. Also, the report content should be opened to all store managers so that they can browse the reports at any time.

<Organization Info>

• Company
• Kanto; Tokyo store, Shinagawa store, Yokohama store
• Chubu-area; Nagoya store
• Kansai-area; Kyoto store, Osaka store

(This blog, "Workflow Sample" is falling into a rut recently. Suddenly, a thought of posting in a format of 'Business designing exercise' (Process Modeling exercise) came to me...)

[Data Items list screen]