Login
The Standard Cuberry Behaviors & Features
 
To make use of Cuberry's features and to keep the behavior and the look of all modules some guidelines should be met.
Here is a list of recommendations which helps you when creating new or extending existing modules.
  • All labels and messages are localizable
     
  • Messages are preferable shown in the status strip of the DetailView or in a the standard Cuberry dialog called P2YellowDialog.
     
  • When pressing the save button the status strip shows a green sign as a confirmation that the entity was successfully saved. If not, then a red sign must be shown in the status strip with the message that describes why the error has occurred.
     
  • After making a change and trying to close the DetailView without clicking on the save or save & close button a message must pop up saying that the entity was not saved and asking if it should be saved. A cancel option is given to go back to the DetailView without saving.
     
  • Changes are not saved automatically. The save or the save & close button must be clicked to save the changes.
     
  • Update management / locking is implemented by using the TStamp field. If someone else has updated the rows before the save button was pressed, then an error messages shows that an update is not possible.
     
  • Stored procedure and database related functionalities should be kept to a minimum (triggers, table-valued or scalar-valued functions …etc.) for the case that the database should be migrated to another database vendor than Microsoft. 

 
The Main Application View 

On the left side of the application main view you have the main and sub menus and the find control in between. Only menu items are shown where the user has access permission. 

Users see only those menu items to which they has access rights.

The sorting position of all menu items can be set up in the Module Manager module. Both the main and the sub menu labels are customizable.
 
The language can be switched through the language selector on the right bottom corner.

The current user and user group is shown on the top right corner. This helps the administrator to identify and edit the user access permissions.

 

The Application Main View in Right-To-Left Language

The application supports multi languages. In the following screen shot Arabic is the selected language to show that right-to-left languages are supported. 

 
The Standard Cuberry DetailView 

The DetailView comes with many standard components. The menu bar has five standard buttons: [Save], [Save & Close], [Print], [History] and [Information].

The information button shows who created this entity, when it was created and who updated it and when it was updated the last time.

The history button (not fully functioning yet) shows the tracked history of this entity. To activate this feature each field which should to be tracked must be defined first.
 

The Status Strip shows messages and warnings on the left side.

On the right the Status Strip shows the status of the entity, e.g. for a financial transaction the status can be “New”, “Open”, “Booked” or “Canceled”. This is part of Cuberry’s workflow feature. Hiding and showing buttons in the menu bar depend on the status. More information on the workflow feature can be found in Workflow Management section.

Labels, Status and messages in the status strip are shown in the current language and can be customized with the Module Manager.
 

Editing or adding an entity is always done in the DetailView. Mandatory fields are marked red if a field is empty. Mandatory fields and content validation can be customized in the Module Manager.

The status strip on the button of the detail view shows the current status of the entity (on the right corner) and shows messages as feedback on the user's actions (on the left corner). A red, yellow or green sign shows the criticality of the message.

Menu items are shown and hidden depending on the users permission and the current workflow status of the entity.
Some Additional Module User Interfaces 

The Reporting Module

The Reporting Module shows reports on the Microsoft Reporting Server.
The naming and description of each report can be set for each installed language.
The reports are grouped in categories and there is an access permission for each report. 

 

User Management

Users are managed in groups. Each user may be in only one user group. Access permissions are managed on user group basis. A user group may have read, write or no permission on a module/sub-menu-item.

Special rights may also be configured. As the workflow status of the entity influences the activation and deactivation of certain menu buttons and fields, special permissions can be configured to change this behavior.

E.g. Accounting Users may only add new accounts but they may not turn these accounts to active (as long as an account is in the "Initializing" status no transactions can be made on this account). So there is an "Activate Account" button which is not shown to Accounting Users but it must be shown to Accounting Administrators who have the right to turn these accounts to status "Active". This is where the special permissions is needed.