You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/pages/on-click-event.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ The **Show a page** event opens the specified page. Select the page which opens
98
98
99
99
#### Page Arguments
100
100
101
-
**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.
101
+
**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 or the page itself.
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/pages/page-resources/snippet.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,10 +46,10 @@ The values for the platform property are:
46
46
47
47
#### Parameters {#parameters}
48
48
49
-
**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.
49
+
**Snippet parameters**allow snippets to be re-used with different data. They work the same way as [Page Parameters](/refguide/page-properties/#parameters).
50
50
51
51
{{% alert color="info" %}}
52
-
Snippets do not support **optional**and **primitive** types as [parameters](/refguide/page-parameter/).
52
+
Snippet parameters do not support primitive types and cannot be made optional, like [page parameters](/refguide/page-parameter/) do.
Argument determines whether it is **required** or **optional** to [pass an argument](/refguide/page-parameter/#passing-arguments) to the parameter when opening the page. If it is required it is mandatory to supply an argument for that parameter when opening a page.
30
+
Argument determines whether it is **required** or **optional** to [pass an argument](#passing-arguments) to the parameter when opening the page. If it is required it is mandatory to supply an argument for that parameter when opening a page.
31
31
32
32
### Default Value
33
33
34
-
When an argument is set to **optional**, a default value can be set. When a default value is set if the parameter is omitted, the default value will be used. In the example below, if the parameter is omitted by the user an empty string `''`will be used for the parameter.
34
+
When argument is set to **optional**, a default value can be set. The default value is used if no [argument is passed](#passing-arguments) to the parameter. Given the example below, if no argument is passed for **CustomerName**, the page will open with the parameter set to `''`.
The default value is used when the argument is omitted during **modeling**. Not when the argument value is `empty` during **runtime**.
39
+
The default value is used when the argument is omitted during modeling. Not when the argument value is `empty` during runtime.
40
40
{{% /alert %}}
41
41
42
42
## Passing Arguments {#passing-arguments}
@@ -53,6 +53,6 @@ Variable arguments are used to pass parameters from the context to the page. Thi
53
53
54
54
### Expression-Based Arguments
55
55
56
-
Objects and primitive values, such as `Boolean`, `Date and time`, `Decimal`, `Enumeration`, `Integer/Long`, and `String`, can be passed and used in expressions. This method allows users to use functions and follow associations within the expression to set the argument values. Using expressions for arguments provides flexibility in setting values and improves the functionality of pages. In the example below, the page has a parameter **AnimalName** which is populated by an expression extracting the **Name** member of the provided **Animal** object:
56
+
This method allows users to use functions and follow associations within the expression to set the argument values. Using expressions for arguments provides flexibility in setting values and improves the functionality of pages. In the example below, the page has a parameter **AnimalName** which is populated by an expression extracting the **Name** member of the provided **Animal** object:
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/pages/page/page-properties.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ In simple e-commerce applications, the URLs can be configured as follows:
105
105
106
106
#### Parameters {#parameters}
107
107
108
-
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.
108
+
The list of [parameters](/refguide/page-parameter/) that this page expects. These parameters can be used by widgets on the page.
109
109
110
110
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.
0 commit comments