go-to
This action redirects you to another jig. The go-to action can be used with elements like swipeable and rightElement or combined with another action. When paired with another action, it is triggered after the main action to navigate to a specified screen, for example, saving a date in a form and then opening a list of customers. go-to helps configure navigation, ensuring a seamless app flow. See Navigation for more information.
Configuration option
A go-to action can be set up in various ways:
As a separate action or in the action list.
As an associated action in the action list.
As a
swipeableaction in the left or right direction.As
rightElementin the list.Use the
go-toto open a jig as a modal using theisModalproperty set totrue. Set tofalseopens navigates to the specified jig.Use the
behaviourproperty to determine if you want to push the jig into the history of navigation, by using thenewvalue, or reuse the one you already have in history by using theexistingvalue.When you navigate to a jig using the
action.go-toor open it as a bottom modal (by settingisModal: true), you can access the outputs from that jig by referencing itsinstanceIdin your context expressions. In the originating jig, use the syntax[email protected].[isntance-id-of-the-jig].outputs.[key-of-output]to retrieve specific output values. See the Accessing jig outputs from a modal example.
Considerations
Current known limitations when using the
isModalproperty include:Unable to send a value from the jig modal to the parent jig.
Depending on the device used different behavior can be expected, such as the jig will slide from the bottom to top, but the entire screen will be covered. This applies to:
On any Android device (phones and tablets).
On an iPad in landscape mode:
When the drawer is open, it will only open in the jig panel.
When the drawer is closed, it will cover the entire screen, but it will not display as a modal.
Examples and code snippets
go-to as an action

go-to swipeable left/right

This example uses the go-to action as a swipeable property. We can choose the swipe direction left or right. After pressing the button, it will redirect to the details of the person.
Examples left: See the full example using static data in GitHub. See the full example using dynamic data in GitHub.
Examples right: See the full example using static data in GitHub. See the full example using dynamic data in GitHub.
go-to right button element

go-to onSuccess

In this example, the go-back action is associated with the submit-form action. After we enter the signature and press the "Sign" button, the submit-form action is performed and then the go-to action redirects us to the next page.
Examples: See the full example using dynamic data in GitHub.
go-to open a jig as a modal
In this example, we use the go-to action as the rightElement in the list-item component. There is a button for each item. When tapped the go-to will open the jig as a modal when the isModal property is set to true.
Examples: See the full example using dynamic data in GitHub.

go-to using new & existing behaviour
In this example, three jigs are configured to create a stack of data for each guest, including their Name, Age, and Address. Each jig's go-to action is set with the behaviour property as new, enabling new guest details to be pushed into the app history. In the final jig, a secondary go-to action is added. This action introduces a button to review each guest's data by setting the behaviour property to existing and linking to the first jig in the stack via the linkTo property. The review process will cycle through each guest's details in the stack before completing.


Accessing jig outputs from a modal
When you navigate to a jig using the action.go-to or open it as a bottom modal (by setting isModal: true), you can access the outputs from that jig by referencing its instanceId in your context expressions. In the originating jig, use the syntax [email protected].[isntance-id-of-the-jig].outputs.[key-of-output] to retrieve specific output values. The instanceId must match the one specified in the instanceId field of your navigation action, and the key corresponds to the specific output field you want to access from the target jig. This allows for seamless data flow between jigs, whether they're opened as full-screen navigations or modal overlays, enabling you to capture user interactions and form submissions from the modal jig and use them in the parent jig's logic or display.

Last updated
Was this helpful?