Best Practices for Designing Models

From QPR ProcessAnalyzer Wiki
Revision as of 23:50, 22 March 2022 by Ollvihe (talk | contribs) (Created page with "Limit number of returned rows Prefer ready-made measures and dimensions over custom As Analyzed objects, prefer Cases over Events. Don't use dimensioning when it's not nee...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Limit number of returned rows

Prefer ready-made measures and dimensions over custom

As Analyzed objects, prefer Cases over Events.

Don't use dimensioning when it's not needed. When there is anyways a row for each root object, dimensioning is unnecessary. For example, Cases as Analyzed objects and dimension by case id will lead to a row for each case, but the same result can be achieved by disabling dimensioning.

Use preset as examples

Use on-screen settings for settings that often users want to change, as they are easier to use than opening the settings. They also guide users to change parameters that might be relevant from the analysis viewpoint.