Deployment Drafts

What

When you create a deployment in FileWave Anywhere, an unfinished deployment may appear as a Deployment draft on the Deployments page. Keeping a draft preserves your unfinished work; it does not publish the deployment or confirm that its payloads have reached devices.

When/Why

Deployment drafts protect work that you have started but not finished. If you close the browser, move to another task, or leave the deployment before saving it, FileWave Anywhere can keep the draft so you can return to it later.

Drafts are stored for the user and browser that created them. For example, a draft created in Chrome will not appear if the same administrator signs in from Firefox.

How

Deployment drafts appear on the Deployments page. To continue a draft, click its name or use the ... menu and choose Edit. To discard it, use the same menu and choose Delete.

The older FileWave 14.6 web interface below shows drafts separately from Active Deployments, with Created At and Last modified timestamps.

If you click Cancel while editing a draft, the Keep your draft? prompt offers Keep draft to retain the changes for later, or Delete to discard them.

Resume and check your work

After reopening a draft, recheck its targets, exclusions, payloads, installation type, and timing before saving and publishing. Review the Deployment Summary to confirm the intended device scope and content before updating the Model.

If a draft seems to be missing, return to the same administrator account and browser that created it. Check the name and last-modified time in Deployment drafts. If you already finished saving the deployment, look under Active Deployments rather than creating another copy. A draft retained with Keep draft still needs to be completed before it becomes a published deployment.