The quick answer
Open Setup > Custom > Mobile - Applications, view the NSWMS application, and choose Clone on the standard process, here NSWMS_CycleCount. On Clone Process choose Clone; a scheduled script, Mobile - Process Cloning On Demand, creates the copy. When Scheduled Script Status reads Complete, the clone is listed in Mobile - Process List as NSWMS_CycleCount_1 with Creation Type Clone, and after a new mobile session it appears as its own tile beside the standard one.
The screenshots show sample data. Person, company and warehouse values are fictional examples, and the recording is a replay of a practice account. Process names are generated by NetSuite, so yours may carry a different suffix.
Before you start
You need NetSuite WMS with the SCM Mobile application and a role that can customize mobile applications, usually Administrator or a mobile administration role, with the WMS permissions it needs. Try cloning in a sandbox or a controlled role first. Cloning does not hide or replace the standard process: until the standard tile is hidden, both can be available where role access and menu settings allow. This guide stops at the clone. It does not edit the clone's pages, restrict its roles, hide the standard tile or run Update App, which are the usual next steps before you roll a clone out and which you should complete before relying on the handheld result. Menus, button names, the cloning job's name and the generated suffix can differ by release and account.
01. Check the handheld menu
On the mobile device open WMS, choose the warehouse Northport Depot, then Inventory. In this example the tiles are the standard ones available to this role, including Cycle Count, and there is no cycle count clone yet.
02. Open the process list
On the desktop open Setup > Custom > Mobile - Applications, then choose View for NSWMS. Mobile - Process List lists the application's processes. Standard processes normally have Creation Type System and the actions Clone and Configure. Find NSWMS_CycleCount; no cycle count clone is listed.
03. Clone the process
Choose Clone on the NSWMS_CycleCount row. Clone Process says that cloning also creates duplicate versions of the process's pages, information screen elements, page elements, actions and icons; read the page in your account for what it lists. A clone is an independent copy, not a live link: later changes to the standard process do not flow into it.
Choose Clone. In this example a PROCESSING banner asks you to wait and links to the cloning status.
04. Follow the cloning job
Choose the link in the banner to open Scheduled Script Status. The cloning runs as a scheduled script; in this example it is Mobile - Process Cloning On Demand, which reads Processing while it works. The exact name and status presentation can vary.
Choose Refresh until the Status reads Complete. How long it takes depends on the size of the process and the account's queue.
05. Confirm the clone
Open Mobile - Applications again. In this example the Custom Processes count for NSWMS is one higher, though other activity can change that count, so confirm the clone in the process list rather than by the number.
View NSWMS. The new row NSWMS_CycleCount_1 has Edit | View instead of Clone | Configure and Creation Type Clone; its Accessible Role reads Administrator here. NetSuite generates the name and you can edit it after cloning; do not build scripts or integrations that depend on the suffix. Review the accessible roles on any clone you intend to roll out: if none are selected the process can be available to all available roles, subject to their normal WMS permissions.
06. Find it on the handheld
Reopen the mobile app. A running session can keep the menu it downloaded, so if the app offers your last session, choose Begin New Session, then WMS, the warehouse and Inventory. In this example the clone showed up after a new session without any further step; in your account you may need to run Update App first, and you should always run it after you edit the clone.
In this example the Inventory menu now shows a tile named after the clone, NSWMS_CycleCount_1, beside the standard Cycle Count tile. The tile label can be changed by editing the clone.
Check the result
- Scheduled Script Status shows the cloning job as Complete.
- Mobile - Process List has a new row with Creation Type Clone and Edit | View.
- After a new session, and Update App where your account needs it, the handheld shows a tile for the clone beside the standard tile.
Common questions
Why clone a standard mobile process instead of editing it?
Clone when you need process-level customization, additional pages or elements, custom actions, role-specific access, or an independently testable process. Standard processes are SuiteApp-owned and can change in an update, and a clone stays available as an independent copy while the standard flow remains as a fallback. For a change that a supported configuration option covers, such as a default value or a label, configuring the standard process can be enough. Cloning is not always the better choice.
What does cloning copy?
The process and its pages and page elements, plus the other objects the Clone Process page lists in your account, such as information screen elements, actions and icons, as independent records with generated names. The clone is not linked to later changes made to the standard process.
Why is my clone not in Mobile - Process List yet?
Cloning is asynchronous. Open Scheduled Script Status, find the cloning task and choose Refresh until it reads Complete, then reload the process list. If it stays queued or processing for a long time, check the other scheduled script work in the account.
Does cloning replace or hide the standard process?
No. Cloning adds a custom process. The standard process stays available unless its menu icon is separately hidden or restricted, which is a different configuration step you normally do only after testing the clone.
Who can use the clone?
Review the accessible roles on the clone. If none are selected it can be available to all available roles. Users still need the normal WMS permissions, role access, warehouse access and any permissions the process actions need.
Why do I need a new mobile session to see it?
A running session can keep the menu and access information it downloaded. After the clone, and after Update App if your account needs it, begin a new session or fully reopen the app so the device loads the current configuration. A new session does not replace Update App after you edit the clone.
What does the _1 suffix mean?
It is a generated sequence suffix: the first clone of that process. It is not a stable identifier to use in instructions or integrations, and you can edit the process name or label after cloning.