> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flexagon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# exportNewSnapshot

> This operation utilizes Oracle EPM's migration capability to enable files to be moved across environments. For file type (artifact) objects, it genera

This operation utilizes Oracle EPM's migration capability to enable files to be moved across environments.

* For file type (artifact) objects, it generates a snapshot (containing meta information of on the files only) based on the files selected in the package being built. That snapshot is uploaded to the EPM server and Repeat Export is called which looks at the meta information in the uploaded snapshot and generates an updated snapshot with the files from that EPM server. That new snapshot is downloaded to FlexDeploy as the artifact and the snapshot on the EPM server is deleted.

* For template type objects, this operation exports a JSON template from an Enterprise Data Management instance. The dimension or application which will be exported is the file name in FlexDeploy.

This would be used for the build operation for package based projects using snapshots/templates to deploy EPM files.

This operation is applicable for the following EPM services:

* Planning

* FreeForm

* Financial Consolidation and Close

* Account Reconciliation

* Tax Reporting

* Enterprise Profitability and Cost Management

* Oracle Strategic Workforce Planning Cloud

* Oracle Sales Planning Cloud

* Enterprise Data Management

## Exporting Templates

Application-level template exports automatically include all dimensions in the application. For accurate deployment history and change detection in FlexDeploy, it is recommended to also include all application dimensions in your FlexDeploy package when exporting an application. This can be done by manually adding dimensions to the package or by using a dynamic package (see below), which would automatically add any new application dimensions to the package.

![image-20250516-151751.png](https://mintcdn.com/flexagon-llc-ce77a95c/NkeZh5D-Nf8j_WaD/images/fd111/12596415438.png?fit=max\&auto=format\&n=NkeZh5D-Nf8j_WaD\&q=85\&s=5bee34c728ed0e02ca8b78c589f450d5)

## Discovery

Prior to initiating a build, the user must discover the files to be included in future builds for that project. For file type (artifact) objects, the discovery will use the project property **Oracle EPM Discover Snapshot** to determine the files to add to the catalog. 

Since FlexDeploy @9.0.0.6, each dimension and application in your EDMCS instance will be discovered as a JSON template file. Template files will have the following path structure:

* `/templates/<Application name>/<Dimension name>.json` for dimension files

* `/templates/<Application name>.json` for application files

With the release of FlexDeploy @9.0.0.3, certain EPM types will now be discovered, built, and deployed individually, eliminating the need to deploy all files of a given type as a group. The affected EPM types include:

* Consolidation Rules

* Translation Overrides

* A subset of Data Management types

  * Import Formats

  * Locations

  * Data Load Rules

  * Data Load Mappings

  * Logic Groups

  * Check Rule Groups

  * Check Entity Groups

See [Discovering Project Files](https://docs.flexagon.com/flexdeploy-9-0-documentation/flexdeploy-users-guide/projects/file-catalog.md) for more information. 

# Target Properties

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Property Name**</th><th>**Property Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>Oracle EPM Account</td><td>`FDEPM_CLOUD_ACCOUNT_CODE`</td><td>Yes\
</td><td>Oracle EPM Account integration instance to export from.See [Configuring Oracle EPM Cloud Account](https://docs.flexagon.com/flexdeploy-9-0-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-epm-plugin-guide/appendix-oracle-epm/configuring-oracle-epm-cloud-account.md) for instructions on how to create Oracle EPM cloud account in FlexDeploy.</td></tr></tbody></table>

# Project Properties

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Property Name**</th><th>**Property Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>Discover Snapshot</td><td>`FDEPM_DISCOVER_SNAPSHOT`</td><td>\*No</td><td>The Oracle EPM Snapshot that will be used to discover which files are available.\*Required except when deploying EDMCS template files</td></tr><tr><td>Snapshot Base Name</td><td>`FDEPM_SNAPSHOT_BASE_NAME`</td><td>\*No</td><td>The Snapshot prefix used when exporting a Snapshot. The prefix will be followed by the workflow execution id to form the snapshot name.\*Required except when deploying EDMCS template files</td></tr></tbody></table>

# Inputs

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Input Name**</th><th>**Input Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>Oracle EPM Snapshot Timeout</td><td>`FDEPM_INP_SNAPSHOT_TIMEOUT`</td><td>No</td><td>Time to wait in seconds for the snapshot to be imported, uploaded or downloaded.  Defaults to 300.</td></tr></tbody></table>

# Artifacts

This operation produces artifacts that will be stored in the artifacts repository.

# Endpoint Selection

This operation will select all available endpoints associated to the target.

# Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.