Capsules can address a wide range of purposes. For example, a Capsule could be
An unstructured environment for ad-hoc analysis, allowing users to create and save their reports, analysis and models.
A highly structured application guiding users rigidly throughout a business process such as a budgeting and forecasting application.
An EIS (Executive Information System) application providing dashboards and executive reports.
A presentation for analyzing marketing campaign results, results of a product launch or the performance of any other business activity and process.
A financial reporting booklet or any other type or recurrent collection of reports and analysis.
A procedure for executing a set of maintenance tasks on a database.
Depending on the Capsule’s purpose and the type of users the Capsule is meant for, take into consideration the following guidelines,
Organize you Capsules into folders: you can create folders which are visible to all users, folders visible to user groups or individual users.
The Capsule’s main screen should explain the Capsule’s purpose and contents. Put some introductory text and a diagram illustrating how the Capsule is organized.
Limit the number of Capsule screens to a reasonable number that allows users to well understand and know the content of each screen. This simplifies navigation and maintenance. A single Capsule should not have more than 35 to 40 screens. If more screens are needed, consider creating a new Capsule then to simplify navigation you may create links from a Capsule to another.
Avoid creating similar screens having very slight differences. For example, two identical screens in terms or reports only having a different selection. This approach would cause a proliferation of screens; all users must know how to use the Select, the pagers, filters and the drill-down features.
When creating screens consider the following guidelines,
A screen should load within a few seconds. Limit the number of pictures and logos used and limit the number of data presentation objects (charts, tables etc) in order to remain within a reasonable loading time..
Place more than one report (DataView object) per screen. A screen having a single report does is not fully benefiting from Board’s analytical features. Use more than one report object and use the Master function on to provide depth to the analysis.
Notice
Concurrent Capsule Editing: Two or more Power User can develop together on the same Capsule. The locking mechanism that prevents design overlaps and conflicts happens at Screen and Procedure Level.
Samples :
Two Users can't develop together the same Screen or the Same Procedure
If User_1 tries to edit a Screen/Procedure that is already in design mode for User_2, he gets a Lock Message : it is enough that the User_2 closes the Screen/Procedure to enable Screen Editing for User_1.
If User_1 creates the Screen_1 (without Saving it yet) and User_1 creates the Screen_1 (same naming) they will be both able to edit Screen_1 and Save it with the Last Saved Screen_1 to prevail.