Remarks in O-Quis

This can be found in the procella manual. 

V13_FAQ_procella_Configuration-Recording-Data (hexagon.com)

Chapter 5.7.3.5; Page 72. 

Best practice: first create an event in the event catalogues called "free input" (or similar)

in the CMM - Reporting go in File | Configuration | additional settings  | recording data - standard

here choose the event

the event is written in K0005 like all events, the remark in K0009 (This is the reason, why K0009 is existing)

Explanation of the reason for this doubled writing: 

As much as possible Catalogue-based entries should be used. It makes the reading faster; the data amount is less in the database. and later analyses can be made faster (Pareto of Events, and similar). 

When adding text, later this "Free text" event can be searched, a Key-User can analyze the text which had been collected, and maybe make for the future standard events out of this. 

This can be found in the procella manual. 

V13_FAQ_procella_Configuration-Recording-Data (hexagon.com)

Chapter 5.7.3.5; Page 72. 

Best practice: first create an event in the event catalogues called "free input" (or similar)

in the CMM - Reporting go in File | Configuration | additional settings  | recording data - standard

here choose the event

the event is written in K0005 like all events, the remark in K0009 (This is the reason, why K0009 is existing)

Explanation of the reason for this doubled writing: 

As much as possible Catalogue-based entries should be used. It makes the reading faster; the data amount is less in the database. and later analyses can be made faster (Pareto of Events, and similar). 

When adding text, later this "Free text" event can be searched, a Key-User can analyze the text which had been collected, and maybe make for the future standard events out of this. 

Thanks Thomas! I sometimes forget that CMM reporting and Procella are a part of the same solution. When dealing with CMM reporting I'm only focused on looking at CMM reporting help files. Could be a future improvement to have more referencing between docs. CMM reporting goes over events, but would have been helpful for it to reference to look at procella for the answer. 

I already took this on my plate, as I did not find it in the CMM - documentation also (I have written it). Thank you for this. 

I've made the new catalogue entry and now trying to make this a standard event. However, under the standard event drop down I'm not seeing anything selectable. 

It can depend on the Version. Sometime you have to open a dataset (from file or from database), that the catalogue is initialized and shown in the dialogs. If this does not work, please contact your support with the exact Version number and customer number, that they can check this.