Registreren

Pages
- Building your application
  - Introduction
  - Data model
  - Business logic
  - User interface - functional
  - User interface - graphical design
  - Configuration
  - Resources
- Advanced functions
- Hosting
- Miscellaneous

Diagnostics

When applying changes to your blueprint, it will be analyzed automatically by the engine for errors.

Please note: If you run into problems you cannot solve yourself, do not hesitate to contact CrossmarX for assistance. If any bugs are discovered, we aim to fix those as quick as possible.

Blueprint warnings

The results of the afore mentioned analysis are presented in the blueprint diagnosis. This is an important and powerful tool. If something goes wrong, your first step should always be to check the diagnostics for possible warnings. A link to the diagnosis is always shown when reloading your application.
To access the diagnostics use Health check/diagnostics at the Deployment Panel.

Here is a small check list of common mistakes:

Did you define a database for your application?
Did you select the database and have you defined a table name for your class? If not, data cannot be stored!
Have you marked a key field within your class? And, if necessary, did you use the data type auto number for this key field?

When debugging, you should be sure application is using the most recent blueprint. If you have modified your blueprint and you haven't reloaded it into your application, you will not see the effect of your change. When in doubt, reload your application first and check if it still has an error.

Explain pages

The blueprint diagnostics does not explain everything. It only gives insight into the correctness of your blueprint, it doesn't show anything about the running application. To gain more insight into what is happening when the application is running explanations can be shown concerning what it does with every call using the explain pages. Although not exactly the same, the explain pages are similar to a system log.

You have to activate this feature at the "Session" menu at the Application Panel by selecting the session property “explanations” with value "true". After this is done, the engine puts question marks on the screen next to every screen element. Clicking on the question mark give you an extensive explanation about the screen element. For example why it is visible or hidden. It is often very useful to see how the engine has interpreted the user relevances you may have defined.

Documentation in the Studio

If you're still stuck, you can try searching the Studio for documents that are related to your problem. You can manually browse the pages, the forum, the tutorials or even the issues (see "Reporting bugs" below).

Reporting bugs

Bugs and issues can be reported through the bug tracking tool. To open the tool, open the "Issues" menu at the top of the CrossmarX Studio and click "All issues". The issue database, which can be viewed here, contains information about all (unresolved) issues concerning the CrossmarX Application Engine.

Contact CrossmarX

As noted before, if you cannot solve the problem by yourself, please contact CrossmarX for assistance. Do not hesitate to call, mail or chat with us, even during evenings or on weekends. If you have encountered a bug in our software we are eager to fix it as quickly as possible.