Add references to page parameters doc page

Author: stdagkalakis

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/client-activities/show-page.md

@@ -72,7 +72,7 @@ Often you need to have control of page history, for example to show the correct
 
 ### Parameters Section {#parameters}
 
-Depending on the selected page, you will see a list of its parameters. For each parameter, you can configure a variable or expression to specify which object should be passed to it. These objects are used by [data views](/refguide/data-view/) with a page parameter data source. If only one variable of the expected type for a certain parameter is available, that variable is automatically filled in.
+Depending on the selected page, you will see a list of its [parameters](/refguide/page-parameter/). For each parameter, you can configure a variable or expression to specify which object should be passed to it. These objects are used by [data views](/refguide/data-view/) with a page parameter data source. If only one variable of the expected type for a certain parameter is available, that variable is automatically filled in.
 
 ## Common Section{#common}
 

content/en/docs/refguide/modeling/pages/on-click-event.md

@@ -98,7 +98,7 @@ The **Show a page** event opens the specified page. Select the page which opens
 
 #### Page Arguments
 
-**Page arguments** are automatically configured based on the parameters of the selected page and the available arguments. In general, arguments are taken from any enclosing data widget. If the data widget enclosing the widget calling a page is inside another (nested) data widget, then objects from that data widget and any others in which it is nested can also be passed.
+**Page arguments** are automatically configured based on the [parameters](/refguide/page-parameter/) of the selected page and the available arguments. In general, arguments are taken from any enclosing data widget. If the data widget enclosing the widget calling a page is inside another (nested) data widget, then objects from that data widget and any others in which it is nested can also be passed.
 
 ### Call a Microflow {#call-microflow}
 

content/en/docs/refguide/modeling/pages/page-resources/snippet.md

@@ -48,6 +48,10 @@ The values for the platform property are:
 
 **Snippet Parameters** works the same way as [Page Parameter](/refguide/page-properties/#parameters) with the difference that a snippet's parameter can be accessed at the top level, for example when creating expressions or selecting attributes.
 
+{{% alert color="info" %}}
+Snippets do not support **optional** and **primitive** types as [parameters](/refguide/page-parameter/).
+{{% /alert %}}
+
 #### Variables {#variables}
 
 The list of **Variables** defined on the snippet. Variables are non-persistent, primitive values that can be used as attributes by widgets in the snippet. They behave the same as [variables on pages](/refguide/page-properties/#variables), with the exception that default values cannot reference snippet parameters.

content/en/docs/refguide/modeling/pages/page/page-properties.md

@@ -105,7 +105,7 @@ In simple e-commerce applications, the URLs can be configured as follows:
 
 #### Parameters {#parameters}
 
-The list of parameters that this page expects. These parameters can be used by [data views](/refguide/data-view/) with a page parameter data source.
+The list of [parameters](/refguide/page-parameter/) that this page expects. These parameters can be used by [data views](/refguide/data-view/) with a page parameter data source.
 
 A page parameter is an input that needs to be passed from the calling page, microflow, or nanoflow to the current page. Page parameters determine information that can be reused on the page. For example, if you want to build an **Employee_Details_Edit** page, the page will have a parameter **Employee**. Thus when this page is called an Employee object needs to be passed to it to show the corresponding Employee data.