Skip to content

Commit 6d32f32

Browse files
committed
Review: Remove excess sentences, adjust text
1 parent ed2e0cd commit 6d32f32

4 files changed

Lines changed: 9 additions & 9 deletions

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ The **Show a page** event opens the specified page. Select the page which opens
9898

9999
#### Page Arguments
100100

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.
102102

103103
### Call a Microflow {#call-microflow}
104104

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,10 +46,10 @@ The values for the platform property are:
4646

4747
#### Parameters {#parameters}
4848

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).
5050

5151
{{% 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.
5353
{{% /alert %}}
5454

5555
#### Variables {#variables}

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ To use an object or primitive value in your page, define a parameter. In the ima
1313

1414
{{< figure src="/attachments/refguide/modeling/pages/page/page-parameter.png" class="no-border" >}}
1515

16-
## Mappings
16+
## Properties
1717

1818
### Name
1919

@@ -27,16 +27,16 @@ Default: *Object*
2727

2828
### Argument {#argument}
2929

30-
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.
3131

3232
### Default Value
3333

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 `''`.
3535

3636
{{< figure src="/attachments/refguide/modeling/pages/page/page-parameter-default-value.png" max-width=70% >}}
3737

3838
{{% alert color="info" %}}
39-
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.
4040
{{% /alert %}}
4141

4242
## Passing Arguments {#passing-arguments}
@@ -53,6 +53,6 @@ Variable arguments are used to pass parameters from the context to the page. Thi
5353

5454
### Expression-Based Arguments
5555

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:
5757

5858
{{< figure src="/attachments/refguide/modeling/pages/page/page-parameter-expression.png" width="500px" >}}

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ In simple e-commerce applications, the URLs can be configured as follows:
105105

106106
#### Parameters {#parameters}
107107

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.
109109

110110
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.
111111

0 commit comments

Comments
 (0)