Blansh
Technologies
Targeted applications:
Broadband Network System Management
Retail Chain and Warehouse System Management
Manufacturing System Management
Completeness of design and life cycle
List of tasks we have done for your project
Partnership opportunity - marketing
Intranet-based Management System Framework documentation (these pages require log-in authorization from Blansh Technologies):
GUI Managed Elements Status Tree
GUI Customer Operations
Broadband Network Control Reference Implementation
Broadband Network Control: Modem Simulator
Blansh GUI customer operations screens
By clicking a <Customer Operations> button in the top Buttons Bar, user initiates a customer operations by bringing up a Customer Records table (see below, click to see in full).
This operation is allowed to the ROOT, TECHNICIAN and OPERATOR authorization levels.
Customer Table consists of the following parts:
Top Table Buttons to invoke customer records related operations.
Query field: shows a current query from which data for this table was retrieved. This query might be manually provided by the user (if not locked by the request of the system designer), or automatically generated as it is a case in the initial start up or as a result of the <select query> operation chosen from the Customer Dialog .
Table of customer records.
Status field : bottom Browser field used.
From this point user may continue by manually updating, inserting, deleting records or exporting table data.
Customer Table screen.
Viewing and analyzing the Customer Table is <customer friendly>. You can change width of any or all the columns, use scroll bars, replace order of the columns.
Updating records.
There are two ways to do this.
1. Update content of the table fields. Complete changes in one field by either clicking <enter> or clicking on another field of the same row. Complete changes in the row by clicking <Update DB Row>. This will send update command to the Manager Server. Status field will report about success of the operation. Then you can continue with another row. All intuitive operations allowed while changing text in the field including <copy and paste> operations. Only remember to complete any row change by clicking <Update DB Row> button.
2. Bring up a Customer Dialog screen by choosing a row first and then clicking an <Update Dialog> button.
Following screen will appear (click to see in full):
Following operations can be performed:
Select query: check boxes against the field which must be matched in the query. Then click <Select query> button. This will update the Customer Table with results from the new query. You can verify your selections looking at the Query Field of the Customer Table.
Update text fields or pull down fields and click <Update>. After making all the updates you can verify the content of the database by running a <Refresh> on the Customer Table screen.
Close Dialog.
It has to be noted that in any of the screens described above, changing content in any field will not change a content of the system's database. Final update will only be completed when clicking either <Update DB Row> of the Customer Table screen or <Update> button of the Customer Dialog screen.
Insert and Delete operations.
These buttons on the Top Buttons Bar allow respective operations. Delete operation can be invoked only after a row was chosen (highlighted). Result: success or failure, will be reported in the status field of the Browser.
You might notice that for the Customer Operations these buttons are disabled (dimmed) . This is a customization to the Customer screens based on the design of our Broadband Network Control Reference Implementation : in this design the Customer records are not created manually by the operator, but rather automatically by the status report from the Modem hardware reporting that a <default> Customer (a connection port for it) exists. The operator only changes this automatically created record to the real customer by changing content of the fields. For the same reason Delete button is dimmed as the connection point (Modem port connection) still exists.
Again, these are customization made to our Framework to implement a specific design pattern.
All changes done by user are confirmed by the messages in the browser status field.
