Create a ChangeSet File

ChangeSets do not include OEM layers. If your application is based on an OEM layer, you must create a ChangeSet for that as well.

Do no store ChangeSet files in the application directory. (With the exception of OEM Template ChangeSets.)

An application distributed as a Snapshot without source files will run as a read-only application. The Idea Studio button will not, and can not, be enabled.

If you intend to use a ChangeSet to distribute updates, you must select a type that matches how the application is running on the destination workstation. Do not send a Snapshot ChangeSet without source code if the application is running in development mode on the destination. Likewise, do not send a Complete ChangeSet if the application is in run-only mode on that target workstation.

To create a standard or snapshot ChangeSet:

  1. Ensure that changes are deployed if auto-deploy is switched off for your workstation. (Local versus Deployed Changes)
  2. Open the Application Configuration dialog to the Create ChangeSet File page.
  3. Select the type of ChangeSet to create.
    If creating a snapshot ChangeSet, choose whether to include source files.
  4. Click, Create.

A dialog box will open, prompting you for a file name. You can also select the directory where the ChangeSet will be stored. The extension ".changeset", ".snapshot" or ".template" will be added to whatever file name you provide.

  1. Type a file name for the ChangeSet.
  2. Click OK.

Revision Files

This applies only to standard ChangeSets, being used to update remote workstations.

When sending an update to a remote computer for a larger application, it may be helpful to limit the size of the ChangeSet by including only revisions that are not already on the remote computer. To do so, generate a revision file on the remote computer, and send that file for use when generating ChangeSet.

If you intend to send further updates to a remote workstation, you may wish to create a revision file on the current machine immediately after creating the ChangeSet. This can be used when generating the next ChangeSet to ensure that it includes only changes made since the previous one.

Optional step:

"Open containing folder after creating file" This option can save time if you intend to copy or otherwise work with the file immediately. This option is available for all types of ChangeSet.