====== Parameters at runtime ======
===== Usage =====
Parameters are typically used by Vigilens to filter a subset of data when creating the report: for a particular company code, for a date or a date range, etc...

===== Creation =====

Parameters can be created in the screens that can use them, for example in conditions on joints or extractions according to criteria.

{{:en:v8_0_0:designer:menus:accueil:nouvellerequete:pasted:20200710-144641.png?nolink&400}}

===== Reuse =====

In all the dialog boxes that accept parameters, any parameter already defined can be reused:\\ 
{{:en:v8_0_0:designer:menus:accueil:nouvellerequete:pasted:20200710-144756.png?nolink}}

===== Mapping =====

During the creation of [[:en:v8_0_0:designer:menus:accueil:start|a new query]], there is the parameter assignment screen :\\ 
{{:en:v8_0_0:designer:menus:accueil:nouvellerequete:pasted:20200710-145425.png?nolink&500}}

This is where it's done:

  * mapping the parameter passing between a calling query and a subquery
  * the choice of the order in which all parameters are entered

We can go to a subquery:

  * or a fixed value (single value, range or list of values)
  * or the value of a parameter of the calling request.

{{:en:v8_0_0:designer:menus:accueil:nouvellerequete:pasted:20200710-145642.png?nolink&400}} \\ {{:en:v8_0_0:designer:menus:accueil:nouvellerequete:pasted:20200710-145717.png?nolink&400}}

<WRAP round tip> 
You can of course reuse the same parameter several times. For example, if we have several subqueries that have a company code as a parameter and/or a criterion about the company in the calling query, it makes sense to reuse the same parameter each time. Thus, at runtime, we will have a single entry of this parameter. 
</WRAP>