Debugging training

Enric

Hi all,

In many occasions new BOARD developers/consultants don't start a project from scratch, they start from an already built solution and they need to solve issues or to evolve it. From my point of view, the "debugging" is as important as the construction, so I ask for an specific training in the academy with the following topics:

LEVEL XXX - Debugging

• Overview of the different BOARD Logs (Datareader, Diagnostics, Data Entry, Procedures…), how to analyze them and next steps once analyzed.

• Breakpoints
  • Overview and when to use them
  • Best practices (For example, if in the step 4 there is a dataflow that doesn't work, to copy the layout in the debugger and save it as "4")

• Impact analysis
  • How to use it and most used cases (for example cubes with procedures)

• General best practices to help in the development and debugging
  • Cubes naming convention (for example "ADMIN - LOAD - XXX", "PLAN - DE - XXX")
  • Procedures
    • When to use Capsule procedures (for example navigation or user interaction) and when to use Database procedures
    • Naming convention
    • Best practices
    • When to use Comments and what to include

I hope with this training we can get a recommended way of working, so we all can become more efficient solving issues without having to invest a lot of time.

Feel free to add in the comments new topics that could be included.

Regards