|
|
|
@ -1,4 +1,4 @@
|
|
|
|
|
d\section{Record filters}
|
|
|
|
|
\section{Record filters}
|
|
|
|
|
\subsection{Introduction}
|
|
|
|
|
Filters are the key element of \OCS{} use cases by allowing rapid and easy access to the searched records presented in all tables.
|
|
|
|
|
Therefore: in order to use this application fully effective you should make sure that all concepts and instructions written in
|
|
|
|
@ -53,7 +53,7 @@ To make life easier filter IDs follow simple convention.
|
|
|
|
|
\begin{itemize}
|
|
|
|
|
\item Filter ID filtering a specific record type contains usually the name of a specific group. For instance \mono{project::weapons} filter
|
|
|
|
|
contains the word weapons (did you noticed?). Plural form is always used.
|
|
|
|
|
\item When filtering specific subgroup the ID starts just like in the case of general filter. For instance project::weaponssilver will
|
|
|
|
|
\item When filtering specific subgroup the ID starts just like in the case of general filter. For instance \mono{project::weaponssilver} will
|
|
|
|
|
filter only silver weapons (new mechanic introduced by the \BM{}, silver weapons deal double damage against werewolfs) and
|
|
|
|
|
\mono{project::weaponsmagical} will filter only magical weapons (able to hurt ghosts and other supernatural creatures).
|
|
|
|
|
\item There are few exceptions from the above rule. For instance there is a \mono{project::added}, \mono{project::removed},
|
|
|
|
|