You use an Assign Variable action to assign a local, page, flow, or application variable a value. This action can also be used to create a local variable.

For example, if your action chain sends a request to a GET endpoint, you can use the Assign Variable action to map the response to a page variable that's bound to a page component. Or, suppose you want to capture the ID of an item selected in a list. You could use a Selection event to start an action chain that assigns the selected item’s ID to a variable.

To use an Assign Variable action to create a local variable:

1. For Variable, enter its name and hit Enter on your keyboard.
2. For Type, select its data type.
3. If necessary, use the Value field to assign it a value.
   
   
   Description of the illustration jsac-assign-new-local-var.png
   
   

To use an Assign Variable action for a value assignment:

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. If you need to create a variable for the assignment, click the Variable property's Create link, otherwise, start to type the variable's name in the field and select it when it appears. You could also select the variable from the list.
3. To set the variable's value, hover over the far-right side of the Value property and click to choose the variable that holds the value, or click fx to create an expression for the value.

   In this example, the page variable fullName is assigned the result from a module function:
   
   Description of the illustration jsac-assign-variables-action.jpg
   

If you need to do another assignment, click the + Assign Variable button in the Properties pane:

Description of the illustration jsac-assign-another-var.png

Then make the assignment using the Variable and Value fields that appear for the new variable assignment:

Description of the illustration jsac-assign-another-var2.png

If you'd like to move a variable assignment to a different position, in the Properties pane, click and hold an assignment, then move it to its new position.

You add a Call Action Chain action to start an action chain. This action can call action chains defined in the same page, flow, or App UI.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. Select an existing action chain from the Action Chain ID list, or click Create to create a new action chain. You'll only be able to select or create an action chain within your current scope or any higher scope. For example, if you're at the page level, you can select or create an action chain at the page, flow, or App UI level. However, if you're at the App UI level, you can only do so at the App UI level.
3. If the called action chain requires input parameters, the input parameters will be listed under the Parameters section of the Properties pane. For each input parameter, hover over the far-right side of the parameter and click to choose its source. If you need to create a variable, use the appropriate Create link in the Variables dialogue to create it at the appropriate scope level.
   
   
   Description of the illustration jsac-create-variable-assigner.jpg
   
   

   If a value is returned by the action, it is assigned to the auto-generated variable shown by the Store Result In property.

   Here's an example of a completed Call Action Chain action with specified input parameters:
   
   Description of the illustration jsac-call-action-chain-action-example.jpg
   

You add a Call Component action to call a method on a component.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. In the Properties pane, select the component name from the Selector list, which is only populated with components that have their ID properties specified.

   For example, if your page contains three buttons whose IDs are Create, Update, and Save, you'll see those options available for selection in the list.

3. With the component selected, select or enter the Method Name to call:
   
   
   Description of the illustration jsac-call-component-action-example.jpg
   
   
4. If the method requires input parameters, hover over the far-right side of the parameters under the Parameters section and click to choose their source.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. In the Properties pane, select an existing function from the Function Name list, or click Create to create a new function. You can select or create a function that is defined for the current page, flow, or App UI.
3. If you want to view or modify the function's code, click Go to Module Function to go to the JavaScript editor to do so.
4. If the function requires input parameters, they'll be listed under the Parameters section of the Properties pane. For each input parameter, hover over the far-right side of the parameter and click to choose the variable that holds the value, or click fx to create an expression for the value. If you need to create a variable, use the appropriate Create link in the Variables dialogue to create it at the appropriate scope level.
   
   
   Description of the illustration jsac-create-variable-assigner.jpg
   
   

   Here's an example of a Call Function action, with its input parameter, arg1, needing specification:
   
   Description of the illustration jsac-call-function-action-example.jpg
   

A Call REST action is used to call a REST API endpoint to create, update, delete or display records.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
   
   
   Description of the illustration jsac-call-rest-action-example-blank.jpg
   
   
2. Click Select beside Endpoint in the Properties pane.

   The Select Endpoint window displays a list of endpoints that are available in your application. Each business object and service usually exposes multiple endpoints, each one for a different purpose. For instance, you can have an endpoint for getting multiple records, one for getting a single record, one for updating a record, and one for deleting a record. Each endpoint has different properties that you need to specify. For instance, for an endpoint that retrieves a single record, the record's ID must be provided.
   
   Description of the illustration action-chain-editor-selectendpoint-dialog-appui.png
   

3. Select an endpoint from the list and click Select.
   The properties for the REST call are displayed in the Properties pane, with required properties marked with an asterisk (*):
   

   
   Description of the illustration jsac-call-rest-action-parameters-app-ui.jpg

   
   
4. If the REST call requires header or input parameters, click the associated Assign or Not Mapped link and use the assignment window to specify the value for the property. Click Save.

   You map variables to parameters in the assignment window by dragging the variable in the Sources pane onto the parameter in the Target pane. In some cases, you might need to make multiple mappings. To delete a line mapping a variable to a parameter, right-click the line and select Delete. You can also select a parameter in the Target pane to view and edit the expression for its assignment in the lower pane.
   
   Description of the illustration action-chain-map-inputparameters.png
   

   If a suitable variable does not exist, use the + icon beside the relevant node (Action Chain, Page, and so on) to create a new variable.

5. Specify any other properties that may be required for the REST call.
6. To handle a REST call error, drag the first action to take if an error occurred onto the Create Error Handle area that appears at the bottom of the Call REST card on the canvas:
   
   
   Description of the illustration jsac-call-rest-create-error-handler.png
   
   The dropped action is added in an If condition that checks if an error occurred during the REST call. Configure the action in the Properties pane and add any other required actions to the condition.
   
   
   Description of the illustration jsac-call-rest-create-error-handler-done.png
   
   

You add a Call Variable action to an action chain to call a method on an InstanceFactory variable defined for the current scope (flow, page, or App UI). Using this action with any other type results in an error.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. From the Variable list, select an InstanceFactory type variable defined for the App UI.
3. For the Method list, select the method you want to call. The available methods are based on the definition file imported for the type.
   
   

   
   Description of the illustration jsac-call-variable-action-example.jpg

   
   
4. If the method requires input parameters, hover over the far-right side of a parameter and click to choose the value, or click fx to create an expression for the value.

   If the method returns a value, it is assigned to the auto-generated variable shown by the Store Result In property in the Properties pane.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. Using the Properties pane, write or edit your custom code:
   
   
   Description of the illustration jsac-code-action.jpg
   
   

You add a Fire Data Provider Event action to dispatch an event on a data provider in order to reflect changes to your data. For example, a component using a particular Service Data Provider (SDP) may need to display new data because new data has been added to the endpoint used by the SDP.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. Update the ID field in the Properties pane to make the action more identifiable.
3. From the Event Target list, select an existing variable based on a data provider (like ServiceDataProvider) as the target of the event. If necessary, click Create to create a new data provider variable as the event's target.
   
   
   Description of the illustration jsac-fire-data-provider-event-example.jpg
   
   
4. Select the type of event you want to dispatch:
   • Refresh: Used to show all changes.
   • Mutate: Used to specify which changes to show. For example, after a record is deleted, you can use the Mutate option to indicate the deleted record, prompting the UI component bound to the SDP to remove it from the display.

     A mutation event can include multiple mutation operations (add, update, remove) as long as the ID values between operations do not intersect. This behavior is enforced by JET components. For example, you cannot add a record and remove it in the same event, because the order of operations cannot be guaranteed.

5. If you chose the Mutate event, ensure that the keyAttributes property is set for the SDP variable. The parameters for showing the added, removed, and updated records are under the Add, Remove and Update sections. For the mutate event to perform optimally, here's what's required for each section:
   • Add: Use the data parameter to pass the added record or records from the add operation’s returned result. If you are using an SDP variable, the structure of the data must match the structure specified by the itemsPath parameter of the SDP variable’s definition:
     
     
     Description of the illustration jsac-sdp-items-path.jpg
     
     Use the keys parameter to pass the key values of the added records with the Set<*> format. Lastly, use the metadata parameter to pass the key values of the added records with the format Array.<ItemMetadata.<KeyValue>>.
     For example:

     data: {items: [callRestCreateEmployeeResult.body],},
     keys: [callRestCreateEmployeeResult.body.id],
     metadata: [{key: callRestCreateEmployeeResult.body.id,}],

   • Remove: Use the keys parameter to pass the key values of the deleted records with the Set<*> format.
   • Update: Same as add.

You add a Fire Event action to invoke a predefined event or a custom event that you have defined in your application.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. In the Properties pane, select an existing event from the Event Name list of available events, or click Create to create a new custom event at the appropriate scope level (page, flow, or App UI). The list contains events that are available within the current scope.
3. If the event has input parameters, the Parameters property is shown. To pass in a parameter, hover over the far-right side of the parameter and click to choose the variable. If you need to create a variable, use a Create link in the Variables dialogue to create it at the appropriate scope level.
   
   
   Description of the illustration jsac-fire-event-action-example.jpg
   
   
4. If the event returns a value, it is assigned to the auto-generated variable shown by the Store Result In property.

You add a Fire Notification action to display a notification to the user in the web browser.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
   
   
   Description of the illustration jsac-fire-notification-action-example.jpg
   
   
2. Update the ID field in the Properties pane to make the action more identifiable.
3. Enter a summary of the notification in the Summary field.
4. Enter the message you want to display in the Message field.

   The message can be a static string (The name was updated.) or it can contain variables ({{ 'Could not create new Contacts: status ' + $chain.results.createContacts.payload.status }}).

5. For Display Mode, choose how the notification is dismissed: Transient — goes away after a few seconds, or Persist — stays until the user closes it.
6. Select a Notification Type to specify the look of the notification window.

You add a For Each action to execute actions for each item in an array.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. Configure the action's properties in the Properties pane:
   1. For Parameters, hover over the property's far-right side and click to choose the array to loop through, such as this array, $page.variables.expenseRecordsToUpdate.data:
      
      
      Description of the illustration jsac-variables-dialogue-items-array.jpg
      
      
   2. For Mode, select whether your called actions run serially (default) or in parallel. Regardless of the mode, the For Each action will not complete until the actions for each item in the array are complete.
   3. For Item Alias, optionally, enter an alias for the current item in the array; the default is item.
   4. For Index Alias, optionally, enter an alias for the loop index, which starts at 0 and increases by 1 for each iteration. The default alias is index.
3. Add the actions you want to take for each item of the array to the Add Action area of the For Each action. Here's an example that loops to call a REST endpoint (PATCH /ExpenseReport/{ExpenseReport_Id}) that updates the expense record at the current iteration:
   
   
   Description of the illustration jsac-each-call-rest.jpg
   
   

Use a Get Dirty Data Status action to check if any of the values have changed for the tracked variables within a particular scope (application, flow, page, fragment, layout), including any contained flows, pages, fragments, layouts, and their extensions. Tracked variables outside the scope being checked aren't considered. For example, in this image, both variables defined at the page level have their Dirty Data Behavior property set to Track.:

Description of the illustration jsac-variable-dirty-data.png

Whenever the value for any of these tracked variables changes, the dirty data status for their scope (referred to as context in code) is automatically changed from 'notDirty' to 'dirty'. If any tracked variables are defined for a layout, fragment, or extension of this page, and one of those variables changes, the page's dirty data status is also automatically set to 'dirty'. To reset the scope's dirty data status back to 'notDirty', use the Reset Dirty Status action.

When checking the dirty data status of a particular scope and its subscopes, it’s the scope from which the action chain is called that matters, not the scope in which the action chain is defined. For instance, if a page event initiates a flow's action chain with a Get Dirty Data Status action, the Get Dirty Data Status action returns that page's dirty data status, not the flow's, because the action chain is called from the page.

This functionality works with all data types except Service Data Providers (SDPs). You'll have to handle tracking value changes for SDPs manually, if needed.

For information about this action in the Oracle Visual Builder Page Model Reference, see Get Dirty Data Status.

This example shows an Add Employee page for adding a new employee's information. The page has two fields, one for a name and one for a birthdate, and their dirty data status needs to be tracked. The page also has a Save, Cancel, and Go to Home Page button. When the Save button is clicked, the employee's information is posted to storage.

Description of the illustration jsac-personal-info-form.png

The name and birthdate components are bound to page variables to hold their values:

Description of the illustration jsac-dirty-data-bind-component.png

To begin:

1. Go to the page's Variables tab and set the page variables' Dirty Data Behavior property to Track:
   
   
   Description of the illustration jsac-dirty-data-info-change-variables.png
   
   
2. To add the dirty data functionality to the Save button's action chain, to check if there's actually dirty data before posting:
   1. Go the Save button's action chain. Here's an example, which passes a new employee's information to an action chain that posts the data to storage:
      
      
      Description of the illustration jsac-dirtydata-action-chain.png
      
      
   2. Add a Get Dirty Data Status action to the top of the action chain.
   3. Wrap the code for posting the new employee's data in an If action to check if there's dirty data to post. If there's no dirty data, do nothing.
   4. At the end of the If action's code, add a Reset Dirty Data Status action to reset the dirty data status back to 'notDirty'.

   Here's the action chain with the added dirty data functionality:
   
   Description of the illustration jsac-dirtydata-action-check.png
   

3. Next, we need to create a vbBeforeExit event listener to listen for when a user tries to navigate away from the page, which includes using the browser's Back and Forward buttons. If there are unsaved changes, a notification will warn the user of the unsaved changes and prevent the navigation. The event listener's action chain will be automatically passed an event object with a dirtyDataStatus property to check if the navigation away from the page will result in the tracked page variables losing their data.

   To begin:

   1. Open the Event Listeners tab and click the + Event Listener button to create a new event listener.
   2. Select vbBeforeExit, which starts its associated action chain whenever a user tries to navigate away from the page. Click Next:
      
      
      Description of the illustration jsac-dirty-data-exit-event.png
      
      

      We now need to create the action chain that's started by this event listener.

   3. On the Select Action Chain step of the Create Event Listener wizard, select the Create Page Action Chain option, under Page Action Chains. Click Finish.
      
      
      Description of the illustration jsac-dirty-data-exit-listener-action.png
      
      
   4. Back on the Event Listeners tab, hover over the new event listener that you just created and click the Go to Action Chain link that appears:
      
      
      Description of the illustration jsac-dirty-data-exit-event-action-link.png
      
      

      You're taken to the Action Chain editor to create the action chain that warns the user of unsaved changes.

   5. Add an If action to check if the navigation away from the page results in the tracked variables losing their data.

      Use the event parameter that was passed to the action chain, which has a dirtyDataStatus property. The property is set to 'dirty' if there will be lost tracked data, otherwise it's set to 'notDirty'.

   6. To handle the case in which the navigation results in a lose of tracked data, within the If action, add a Fire Notification action to notify the user of unsaved changes. To prevent the navigation away from the page, add a Return action to return the return object with its cancelled property set to true.
   7. To handle the case in which there is no dirty data, return the return object with its cancelled property set to false.

      Here's the completed action chain:
      
      Description of the illustration jsac-dirty-data-exit-event-action-chain.png
      

4. Finally, go to the Cancel button's action chain, which navigates to the home page. Add a Reset Dirty Data Status action to reset the page's dirty data status back to 'notDirty'. This is needed in case there's dirty data, which would prevent the vbBeforeExit event listener's action chain from allowing the navigation to the home page.
   
   
   Description of the illustration jsac-dirtydata-cancel-button.png
   
   

You add a Get Location action to get a user’s live location.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
   
   
   Description of the illustration jsac-get-location-action-example.jpg
   
   
2. Update the ID property in the Properties pane to make the action more identifiable.
3. Set the Maximum Age (in milliseconds) of a possible cached position that is acceptable to return. If set to 0 (default), the device cannot use a cached position and must attempt to retrieve the real current position. If set to Infinity, the device must return a cached position regardless of its age.
4. Set the Timeout value, representing the maximum length of time (in milliseconds) that the device is allowed to take in order to return a position.
5. Set the Enable High Accuracy value that indicates whether the application would like to receive the best possible results. If true and if the device is able to provide a more accurate position, it will do so. This can result in slower response times or increased power consumption. If false (default), the device can save resources by responding more quickly or using less power. For mobile devices, you should set this to true in order to use GPS sensors.

You use this action to add If, Else and Else If conditions.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. With the If block selected on the canvas, use either the visual condition builder or the code condition builder to create the condition. To visually create the condition, click the first field in the blue box and select the variable to compare against a value or another variable. Select the comparison operator using the second filed, and enter the value or variable to compare against in the third field.
   
   
   Description of the illustration jsac-if-action-first-condition.jpg
   
   
3. To add another condition, click the + Condition button and create the condition as explained in the previous step.
4. To reorder, delete, or add a condition before or after an existing condition, right-click the condition to bring up its context menu.
5. To combine the conditions with an AND operator, select all from the True if list. To combine the conditions with an OR operator, select any from the list.
6. Add the action to take for the If block when the conditions are met. You can either select the block and double-click the action, or drag and drop the action onto the Add Action area. If another action is to follow, double-click the next action or drag and drop it onto the bottom edge of the preceding action.
   
   
   Description of the illustration jsac-if-action-first-action.jpg
   
   
7. To add an Else or Else If condition, you have two options:
   • Drop the action to take for the new condition onto the Create Branch area at the bottom of the If block, which appears when you hover over it with an action.
     
     
     Description of the illustration jsac-if-action-drop-branch.jpg
     
     
   • Right-click an If or Else If block and select Duplicate.
   By default, an Else condition is created. To turn it into an Else If, enter a condition for it in the Properties pane.

Add a Navigate Back action to return to the previous page in a browser's history.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
   
   
   Description of the illustration jsac-nav-back-blank.jpg
   
   
2. Optional: For Parameters, specify a key/value pair map of parameters to pass to the previous page. If a parameter is not specified, the original value of the input parameter on the destination page is used. If a parameter is specified, it has precedence over fromUrl parameters.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
   
   
   Description of the illustration jsac-nav-app-blank.jpg
   
   
2. For the App UI property, select the App UI to navigate to. To find it more quickly, start to type the name of the App UI in the text area and select it when it appears.
3. For the Flow in App UI property, which appears after selecting an App UI, select the flow within the selected App UI to navigate to. Only default flows and flows that have their "Let other App UIs navigate to this flow" setting enabled can be navigated to and are available in the dropdown list:
   
   
   Description of the illustration jsac-nav-app-let-nav-flow.jpg
   
   
4. For the Page in Flow property, select the page within the selected flow to navigate to. Only default pages and pages that have their "Let other App UIs navigate to this page" setting enabled on their Settings tab can be navigated to and are available in the dropdown list:
5. If the selected App UI has input parameters, enter them under Parameters, which appears after selecting the App UI.
   
   
   Description of the illustration jsac-nav-app-example.jpg
   
   
6. For the Browser History property, select either push (default), skip, or replace to define the effect on browser history. This value is used only if the resource is used in the same window. If you choose skip, the URL is not modified. If you choose replace, the current browser history entry is replaced instead of pushed, meaning that the back button will not go back to that page.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
   
   
   Description of the illustration jsac-nav-flow-blank.jpg
   
   
2. For the flow options, the Flow in Current Page option is only available if the page includes a Flow Container component. Selecting it provides you with the options for navigating to a flow or page within the current page. Selecting Flow in Parent Page provides you with the options for navigating to a flow of the parent page.
3. For the Flow property, select a flow or click the Create link to create a new flow to navigate to.
4. If the selected flow has input parameters, enter them for the Input Parameters property that appears after selecting the flow.
   
   
   Description of the illustration jsac-nav-flow-example.jpg
   
   
5. For Browser History, select either push (default), skip, or replace to define the effect on browser history. This value is used only if the resource is used in the same window. If you choose skip, the URL is not modified. If you choose replace, the current browser history entry is replaced instead of pushed, meaning that the back button will not go back to that page.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
   
   
   Description of the illustration jsac-nav-page-blank.jpg
   
   
2. For the Page property, select a page or click the Create link to create a new page to navigate to.
3. If the selected page has input parameters, enter them for the Input Parameters property that appears after selecting the page.
   
   
   Description of the illustration jsac-nav-page-input-params.jpg
   
   
4. For Browser History, select either push (default), skip, or replace to define the effect on browser history. This value is used only if the resource is used in the same window. If you choose skip, the URL is not modified. If you choose replace, the current browser history entry is replaced instead of pushed, meaning that the back button will not go back to that page.

You add an Open URL action to navigate to an external URL. In a web app, this action opens the specified URL in the current window or in a new window.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. In the Properties pane, enter the URL to navigate to.
3. Optional: For URL Parameters, if required, provide a key/value pair map of query parameters to pass to the specified URL.
4. Optional: For Hash, specify the hash entry to append to the URL. 
5. For Browser History, select either replace or push (default) to define the effect on browser history. This value is used only if the resource is used in the same window. If you chose replace, the current browser history entry is replaced instead of pushed, meaning that the back button will not go back to that page.
6. For Window Name, specify a name identifying the window as defined in the window.open() API. If not defined, the URL opens in the current window. For apps on mobile devices, you have three possible values: _self (default), _blank, or _system. For local file types, this property is ignored.

   Here's an example to open a new browser window with the specified URL. If you specify a value for the Window Name property (as shown here), once on the URL, the browser back button will re-enter the last page and the page input parameters will be remembered.
   
   Description of the illustration jsac-open-url-example.jpg
   

You use a Reset Dirty Data Status action to reset the Dirty Data status of the tracked variables in the scope where the action is used (application, page, fragment, layout, flow), and in any subscopes (contained pages, fragments, layouts, flows, and any extensions of them). The Dirty Data status of the tracked variables gets set to 'notDirty'.

This action is used with the Get Dirty Data Status action, which returns 'dirty' if any tracked variable in the current scope or its subscopes has a Dirty Data status of 'dirty'.

If you'd like to reset the Dirty Data status of specific variables so they don't cause the Get Dirty Data Status action to return 'dirty', enter or select them using the Variables to Reset property.

Description of the illustration jsac-dirty-data-reset-variables.png

You add a Reset Variables action to reset variables to their default values, as specified in the variable definitions.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. Update the ID field in the Properties pane to make the action more identifiable.
3. Click the Variables to Reset box to select the variables that you want to reset. You can also start to type the variable's name in the box and select it when it appears.
   
   

   
   Description of the illustration jsac-reset-variables-action-example.jpg

   
   

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. For the Payload property, hover over the far-right side of the property and click to choose the variable to return.
   
   
   Description of the illustration jsac-return-action-example.jpg
   
   

The Run In Parallel action is used to run multiple code blocks in parallel, and you can also use this action to wait for their results in order to produce a combined result.

For API information about this action, see Run in Parallel in the Oracle Visual Builder Page Model Reference.

You can add the Scan Barcode action when you want your application to decode information such as URLs, Wi-Fi connections, and contact details from QR codes and barcodes.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
   
   
   Description of the illustration jsac-scan-barcode-action-example.jpg
   
   
2. Specify the action's properties in the Properties pane:
   1. Update the ID field to make the action more identifiable.
   2. In the Image field, enter an image object (either a CanvasImageSource, Blob, ImageData, or an <img> element) to decode.

      Note:

      If you're using the camera component to pass a Blob to the Scan Barcode action, you might run into the Failed to execute 'detect' on 'BarcodeDetector error. To get around this error, convert the Blob to an ImageBitmap before passing it to the Scan Barcode action. For example:

      1. Add a module function to do the image conversion, something like:

           // Convert Blob to ImageBitmap
           //
          PageModule.prototype.createImageBitmap = function(fileBlob) {
             return window.createImageBitmap(fileBlob);
           };

      2. Add a Call Function action to the action chain, similar to:
         
         
         Description of the illustration jsac-scan-barcode-example-chain.jpg
         
         
      3. Pass the converted ImageBitmap as the Image property for the Scan Barcode action.
   3. Optional: For the Formats property, select the barcode formats you want the browser to search for.

      Barcode formats unlock a variety of use cases. QR codes can be used for online payments, web navigation, or social media connections, aztec codes can be used to scan boarding passes, and shopping apps can use EAN or UPC barcodes to compare prices of physical items.

      If Formats is not specified, the browser will search all supported formats, so limiting the search to a particular subset of supported formats may provide better performance.

You add a Share action to share content with other applications, such as Facebook, Twitter, Slack, and SMS, by invoking the native sharing capabilities of the host platform. This action requires the user's consent, and as a best practice, consent should only be sought on a relevant user action.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. Update the ID field in the Properties pane to make the action more identifiable.
3. Configure the Title, Text, and URL. All properties are individually optional, but at least one property must be specified. Any URL can be shared, not just those under the website's current scope. Text can be shared with or without a URL.
   1. In the Title field, enter the title of the document to be shared.
   2. In the Text field, enter the text that will form the body of the message being shared.
   3. In the URL field, enter the URL that refers to the resource being shared.

   Here's an example that shares the current page's title and URL:
   
   Description of the illustration jsac-share-action-example.jpg
   

You add a Switch action when you want to match a value against a set of values, in order to execute appropriate actions for that case.

1. Add the action in one of three ways, as explained at the end of Built-In Actions.
2. For Value, hover over the far-right side of the property and click to select the variable that is to be compared against each case value. If the value doesn't match any case value, or if it's null or undefined, the default case is executed.

   For example, when a menu defines a set of options, you can use the Switch action to determine which option was selected and to perform actions for that option. In this case, the page variable menuItemId holds the selected menu option, and it's selected using the Switch action's Value property:
   
   Description of the illustration jsac-switch-action.jpg
   

3. To define a case:
   1. Set a value for the case by selecting it within the Switch action, then using the Value property to enter its value or to select the variable that holds it. To select a variable, hover over the properties far-right side and click .
      
      
      Description of the illustration jsac-switch-action-case1.png
      
      
   1. Drop the actions to execute for the case in the Add Action area of the case block and configure their properties in the Properties pane:
      
      
      Description of the illustration jsac-switch-action-case-action.png
      
      
   1. If the rest of the cases are to be ignored, select Break after. If not selected, the rest of the cases get executed, regardless of their values, until running into a break statement (if at all).
4. To add a new case block, right-click a case and select Duplicate.

You add a Try-Catch action to gracefully handle errors and avoid program crashes.

You can also surround an action with a Try-Catch action by right-clicking it and selecting Surround with Try-Catch:

Description of the illustration jsac-surround-try-catch.png

If you need a Finally block, drag the first action that you want to add to the block over the Try-Catch action and drop it into the Create Finally area that appears:

Description of the illustration jsac-create-finally-block.png