Login to Kuika platform and select the project you will work on from the Apps screen.
Open the Properties panel by selecting the relevant element in theUI Design module.
Click on the+ ADD ACTION drop-down menu.
Select a suitable trigger action (event) such as Initial Actions, OnClick, OnBlur→ Navigation → Navigate.
Configuring the Navigate Action
In the drop-down menu, you can configure the following fields:
To Screen
Tip: String
Necessity Yes
Description: The name of the target screen to which the user will be directed.
Input: Enter the screen name text, for example, “OrderDetailsScreen”. This field can be primarily used to import data from data sources such as Action Result. Other sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker .
Open As
Type: Enum
Necessity Yes
Description: Specifies how to open the screen (only one option must be selected).
Input: For example,
“Current Page”
“New Tab”
“Drawer”
“Modal”
Data can be imported into this field primarily from data sources such as Action Result. Different sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker.
Current Page
Tip: Boolean
Necessity Yes
Description: Should the selected screen open on top of the current page?
Input: For example, true or false.This field can be primarily used to pass data from data sources such as Action Result. Other sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker.
New Tab
Tip: Boolean
Necessity Yes
Description: Should the redirect open in a new tab?
Input: For example, true or false. Data can be imported into this field primarily from data sources such as Action Result. Other sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker.
Drawer
Tip: Boolean
Necessity Yes
Description: Should the screen open as a side panel (drawer)?
Input: For example, true or false. This field can primarily receive data from data sources such as Action Result. Other sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker.
Modal
Tip: Boolean
Necessity Yes
Description: Should the screen open as a modal (popup)?
Input: For example, true or false. Data can be passed to this field primarily from data sources such as Action Result. Other sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker.
FloatPanel
Type: Boolean
Mandatory: Yes
Description: Should the screen be opened as a float panel (a panel that floats on the page)?
Input: For example, true or false. Data can be transferred to this field primarily from data sources such as Action Result. In addition, different sources such as Method Input, Current, Screen Input, Fixed or Component can be used. These categories can be defined by selecting them from the Symbol Picker.
Placement
Tip: String
Requirement: Optional
Description: Drawer's location.
Input: For example,
“Top”
“Right.”
“Bottom.”
“Left”
Data can be imported into this field primarily from data sources such as Action Result. Different sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker.
Width
Tip: String
Requirement: Optional
Description: Drawer or modal width.
Input: For example, values such as “400px”, “80%”, “60vw”, etc. This field is primarily used to import data from data sources such as Action Result. Other sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker.
Height
Tip: String
Requirement: Optional
Description: Drawer or modal height.
Input: For example, values such as “300px”, “90%”, “70vh” can be entered. This field is primarily used to import data from data sources such as Action Result. Other sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker.
Closable
Tip: Boolean
Requirement: Optional
Description: Indicates whether the modal window can be closed by the user.
Input: For example, true or false. This field can be primarily used to import data from data sources such as Action Result. Other sources such as Method Input, Current, Screen Input, Fixed or Component can also be used. These categories can be defined by selecting them via Symbol Picker.
Execute Page Init Actions After Closed (Boolean): Determines whether the initialisation actions of the redirected page are executed when the page opened with Navigate is closed.
true: Initialisation actions are executed after the page is closed.
false: No initialisation actions are executed after the page is closed.
If this parameter is false, the ‘Disable Smart Execute Page Init’ setting has no effect.
Disable Smart Execute Page Init (Boolean): Applies when Execute Page Init Actions After Closed = true. Only available in web applications.
false: The init action does not run when returning to the page unless a backend request was made on the redirected page.
true: The init action runs in all cases when returning to the page, regardless of whether a backend request was made on the redirected page.
This setting is only meaningful when Execute Page Init Actions After Closed = true.
All parameters can be taken from Action Result, Method Input, Current, Screen Input, Fixed or Component sources. These sources can be accessed and linked via Symbol Picker.
