About Apps

The purpose of defining an app is to deliver efficient user interfaces to dedicated users. The purpose of Know-how Apps Components is to rely on the interface for an expert user to quickly program such apps using building blocks such as catalogs, document templates, user features, and commands. The expert user can organize and control the various building blocks by the means of operations pertaining to an object called a technological object. This object enables the end user to put in action the right building blocks combination at the right time.

The diagram below provides the expert user with an overview of an applicative app definition process.

If errors occur, the expert user can locally modify the access rights to the operations to edit them and to test the new solution before he makes the same corrections in the know-how apps component in Know-how Apps Components.

Before the expert user starts to create the end user app, he must have defined the process to be captured and created the features that he intends to reuse such as user features, power copies, VB scripts, CAA commands, engineering templates. He:

• Starts with the definition of types, that is to say a hierarchy of types, and sub-types associated with variables (attributes).
• Creates the dialogs boxes that will be used in the app.
• Defines for every technological object the operations that correspond to the tasks that the end user performs. To define a new operation, the expert user uses "building blocks" (see graphic above) that he links with each other.
• Creates the entire Design Process arranging the particular operations defined in the previous step. It guides the end user in his work.
• Generates the app that will be used by the end user. He creates and deploys the app configuration and can test the user app throughout the definition process.