Mobile states store data to make them available within the app. Data captured from a process page can be stored in the state and accessed on succeeding pages within the mobile process. At the end of a process flow, the stored data can be saved to a NetSuite record or transaction.
When you add or customize a page element, you can set it up to capture data to be stored in the state or display data from the state. For certain mobile actions associated with a page or page element, you can use state data to set up parameters.
You can access data through the state path to its key. For the path, use the state keyword followed by dataRecord, the object in the state that contains data from mobile pages. Within the dataRecord object, you can find groups of keys stored in the following objects:
- scriptParams – This object contains the standard keys for transaction and other data used within a standard mobile process.State path: state:dataRecord:scriptParams
- Example: state:dataRecord:scriptParams:vendorName
- This state path to the standard key, vendorName, enables you to retrieve the name of a vendor associated with a purchase order. Within the PO Receiving process, when you select a purchase order on a page, the associated vendorName key and its value are stored in the state for the succeeding mobile pages.
- auxParams – This object contains the keys for additional data that you set up during configuration or customization. It also contains data for the warehouse location that you select on the app.
- State path: state:dataRecord:auxParams
- Example: state:dataRecord:auxParams:customVendorName
- If you store data for a custom field called customVendorName, this state path enables you to retrieve its value.