19 Work With JSON Action Chains

Action chains determine what happens when users interact with pages or components in your user interface, for example, when they select a row in a table or click a button on a page. Each action chain defines a sequence of actions (for example, navigating to a page, calling a REST endpoint, assigning data to a variable, and so on) and is started by an event listener when an event occurs.

Say you want users who click an Edit button on a List of Employees page to be taken to a page that lets them change employee details: you'd define an ojAction event for the Edit button, create an event listener that listens for the ojAction event, and select an action chain with a Navigate action to open the Edit Employee page. Now whenever the ojAction event occurs, the event listener triggers the action chain to navigate to the edit page.

JavaScript and JSON Action Chains

You can call a JSON action chain from a JavaScript action chain using the Call Action Chain action; however, you can't call a JavaScript action chain from a JSON action chain.

When you go to create a new action chain on an Actions tab, you can choose between a new JavaScript or JSON action chain:

Description of the illustration jsac-create-new-chain-dialogue.png

When you go to create a new action chain for an event listener, component, or variable, by default it will be a JavaScript action chain.

If you only want to work with JSON action chains, refer to JavaScript and JSON Action Chains for instructions on how to disable JavaScript action chains.