1. SCM (Supply Chain Management)
  2. SCM Mobile
  3. SCM Mobile App Customization
  4. Setting Up Image Capture or File Upload

Setting Up Image Capture or File Upload

On mobile pages, you can add the following icon page elements that provide additional capabilities to a standard or custom mobile process:

When you add these icons, you automatically include the image or document files during submission as you complete the mobile process flow. You can add only one of each icon on the same mobile page.

Supported Standard Target Transactions

Based on the standard mobile processes available within the SCM Mobile apps, you can set up the following supported transaction types:

Transaction Type

ID

Purchase Order

Return Authorization

Item Receipt

purchaseorder

returnauthorization

itemreceipt

Sales Order

Transfer Order

Item Fulfillment

salesorder

transferorder

itemfulfillment

Work Order

Work Order Completion

Work Order Issue

Assembly Build

workorder

workordercompletion

workorderissue

assemblybuild

Inventory Count

Inventory Adjustment

inventorycount

inventoryadjustment

  • If you create a custom record, you can also set it up to attach images or files.

    You can attach files to these NetSuite transactions even if the mobile process does not directly update them. To update them separately, you can run the scheduled script provided by SCM Mobile. For more information, see Capturing and Attaching Files Through the App.

  • You cannot attach the files to the following transactions: bin transfer, inbound shipment, wave, and pick task.

On a target transaction, the app displays the Mobile App Attachments subtab that contains the list of attachments by default. Alternatively, you can choose the standard or custom field in which you want to display the image or document attachments.

To set up image capture or file upload:

  1. Depending on the mobile process, follow the instructions in one of the following topics to add the page element until you reach the Mobile – Page Element page:

  2. On the Mobile – Page Element page, do the following:

    1. In the Name field, enter a unique name for the page element.

    2. In the Label field, select the label that you want to appear on the mobile page for this element.

    3. In the Type field, select one of the following page element types: Capture Image Icon or Upload File Icon.

  3. Specify how you want to attach images or files captured from the mobile page by doing one of the following:

    • To map the target transaction or custom record to which you want to attach the image or document files, set the Record Name field. In this field, you can enter the ID of the target transaction. To view the list of supported transactions and their IDs, see Supported Standard Target Transactions.

      If you want to display attachments in a specific field within the record, set up the Field Name field too.

    • To display attachments in a sublist, set up the Sublist Name field instead.

      If you want to display attachments in a specific field within the sublist, set up the Field Name field too.

    • If you want to attach files to multiple transactions, set the same fields on the No Code Settings subtab instead. To map a new transaction, click New Mobile – No Code Settings.

    For more information about these fields and IDs, see Data Capturing and Storage for Page Elements.

  4. To map your icon page element with the transaction associated with the mobile process, do the following:

    1. In the Reference Transaction Type field, enter the internal ID of the transaction.

    2. In the Reference Transaction State Path field, enter the state path to the key that contains the reference transaction’s internal ID.

      For more information about state paths, see Accessing Data Stored in the State or the example in this procedure.

      Alternatively, to assign a static value, enter the internal ID of the specific reference transaction. You may also use the keyword, constant, following by the internal ID or another static value.

  5. (Optional) For the Capture Image Icon, to include additional details in the filename, you can set up the Image State Path field. In this field, you can enter the state path to a key that contains the additional detail.

    For example, if you want to include the warehouse name in the filename, you can enter the following path in this field: state:dataRecord:auxParams:warehouse.

  6. Optionally, to control the visibility of the icon on the mobile page, you can set the following additional fields: Visibility Condition or Disable Field Condition.

    For detailed instructions, see Page Element Visibility and Loading.

  7. Click Save.

    You can perform other customizations or configurations on other pages or page elements within the mobile process.

  8. If you add multiple target transactions on the No Code Settings subtab, as described in step 3, you must update the mobile actions used for data submission.

    For example, data submission for the standard PO Receiving process occurs when you click the Enter Bin button for warehouses with bins. After you add the icon, you can access the Enter Bin page to configure the After On Click Action RESTlet for this button. You can set up the same mobile action used for standard mobile processes. See Mobile Actions for Data Submission.

  9. To apply all your updates to the app, you can click Save and Update App for Mobile Configuration. For Mobile Customization, see Compiling Mobile Customizations.

Example

Within the standard PO Receiving process, you want to add the Capture Image icon to the Enter Item page. On the Mobile Configuration page for this process, you access this page named, page_poReceiving_selectItem. Then, you click the Additional Page Elements subtab to access the Mobile – Page page on which you can add a new page element. On the Mobile – Page Element page, you provide the basic element settings, and then enter the following values for the new icon element:

  • Type – Capture Image Icon

  • Record – itemreceipt

    This setting displays captured images on item receipts, the target transaction.

  • Reference Transaction Type – purchaseorder

    This setting assigns purchase orders, the transaction associated with the mobile process, as the reference transaction for item receipts to which images are attached.

  • Reference Transaction State Path – state:dataRecord:scriptParams:transactionInternalId

    This state path to the transactionInternalId key stores the internal ID of purchase orders processed through PO Receiving on the app. It maps the specific purchase order used to generate the item receipt to which the captured images are attached.

With this set up, you can view captured images on the Mobile App Attachments subtab of generated item receipts associated with specific purchase orders received through the app.

After you update the standard or custom mobile process, you can view the icon on the app.

For information about manually attaching captured or uploaded files, see Capturing and Attaching Files Through the App.

If you encounter issues, see Troubleshooting Customizations.

Related Topics

General Notices