Showing posts with label cloning. Show all posts
Showing posts with label cloning. Show all posts

Thursday, 28 May 2026

New enhancement way to clone the EPM Application: Starting from EPM Monthly Patch 26.05

Prior to EPM monthly patch 26.05cloning of any EPM application was limited to using backup snapshots or the Artifact snapshot as the source. There was not much flexibility provided by Oracle. From EPM Monthly patch 26.05, administration has got flexibility to specify an Environment Backup as the source when cloning an environment, providing a more efficient and reliable way to replicate the environments for disaster recovery or production-to-test migration.

EPM Automate command :  cloneEnvironment 

Clones the current environment and, optionally, identity domain artifacts (users and application role assignments), Data Management records, audit records, Job Console records, application properties, contents of the inbox and outbox, and stored snapshots. 

This command is an alternative to using the Clone Environment feature.

Syntax -

epmAutomate cloneEnvironment TARGET_USERNAME TARGET_PASSWORD TARGET_URL [SnapshotName=NAME] [environmentBackup=NAME] [UsersAndPredefinedRoles=true|false] [DataManagement=true|false] [appAudit=true|false] [jobConsole=true|false] [storedSnapshotsAndFiles=true|false] [DailyMaintenanceStartTime=true|false] [ApplicationProperties=true|false]

Examples:

  • Clone the environment, users and application role assignments, audit data, job console records, and Data Management records using an environment backup. Also change the maintenance start time of the target environment to that of the source environment:

    epmAutomate cloneEnvironment serviceAdmin Password.epw https://test-cloudpln.pbcs.us1.oraclecloud.com environmentBackup=2026-03-11T16:30:37/Environment_Backup UsersAndPredefinedRoles=true

  • Clone the environment, users and application role assignments, audit data, job console records, and Data Management records using a specific backup snapshot. Also change the maintenance start time of the target environment to that of the source environment:

    epmAutomate cloneEnvironment serviceAdmin Password.epw https://test-cloudpln.pbcs.us1.oraclecloud.com SnapshotName=2026-03-11T16:34:52/Artifact_Snapshot UsersAndPreDefinedRoles=true

  • Clone the environment including the contents of inbox and outbox, stored snapshots, but not the users and application role assignments, Data Management records, audit data, and Job Console records using the last artifact snapshot, without changing the maintenance start time of the target environment:

    epmAutomate cloneEnvironment serviceAdmin Password.epw https://test-cloudpln.pbcs.us1.oraclecloud.com DataManagement=false appAudit=false jobConsole=false storedSnapshotsAndFiles=true DailyMaintenanceStartTime=false

Applies to:   

ARCS, EDM, FCCS, Freeform, NRCS ,TRCS, Planning applications and Enterprise Profitability and Cost Management,

Business Benefit: 

This new option provides a more efficient and reliable way to replicate the environments for disaster recovery or production-to-test migration.

Thank you!

Friday, 23 May 2025

Clone Environment Able to Retain Application Settings in ARCS

The Clone feature in Migration and the cloneEnvironment EPM Automate command have been enhanced to optionally retain the application properties (Redwood Experience, theme, business process name, logo image, and background image) of the target environment.

These changes are made to support this enhancement:

  • EPM Automate: The cloneEnvironment command has been enhanced to accept the ApplicationProperties optional parameter, which defaults to true. With this default behavior, application properties are cloned from the source environment to the target. You can set this value to false to retain the application properties of the target environment.
  • Clone UI in Migration: The Clone Environment screen now shows the Application Properties checkbox. Deselect this checkbox to retain the application properties of the target environment.


Below types of records can be cloned - 

  • User and Predefined Roles (Identity domain artifacts)
  • Data Management (Optional) - For ARCS, EPCMCS, FCCS, FreeForm, Planning, PCMCS, and Tax Reporting
  • Application Audit (Optional) - For EPCMCS, FreeForm, and Planning
  • Job Console (Optional) -For EPMCS, FCCSFreeFormPlanning, and Tax Reporting
  • Stored Snapshot and Files (Content of the inbox, outbox, and stored snapshots)
  • Daily Maintenance Start Time
  • Application Properties (Optional) - For Account Reconciliation only

Business Benefit: This enhancement allows you to retain the application settings of the target environment.

Monday, 19 May 2025

Introducing a New Role for Managing Migration, Cloning, and Daily Maintenance in ARCS

Prior to update of 25.05, a user with Service Administrator role only can perform the tasks related to migration of application, cloning of environment and set the daily maintenance.

In release 25.05, A new application role named Migrations - Administer has been introduced. Users who are granted this role can access the following cards under the Tools card:

  • Migration
  • Clone Environment
  • Daily Maintenance

These users also have access to the REST APIs and EPM Automate commands that are associated with the above cards. For example, these users can issue the importsnapshot, cloneEnvironment, and setDailyMaintenanceStartTime EPM Automate commands.

Applies to:

  • Account Reconciliation 

Business Benefit: This feature helps delegate migration activities to users who are not Service Administrators.


Created by Mohit Jain and Megha Gupta.

Ability to Create and Manage External Users

Service Administrators can now use the Manage Users tab under Access Control to create, edit, and delete external users (users who are not p...