What is the logic behind testName in the epmautomate command simulateconccurentusage? — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

What is the logic behind testName in the epmautomate command simulateconccurentusage?

in EPM Platform and Freeform 28 comments

Summary:

In the July 2025 patch updates for EPM, a new parameter testName was introduced. Per July 2025 notes:

The simulateConcurrentUsage EPM Automate command and REST API have been updated to accept the testName parameter which allows you to specify a name to identify the current command or API invocation. Additionally, the value you specify for this parameter is used to name the users created for the simulation. This parameter value is mandatory for test modes 0, 1, 2, and 3 and is optional for test mode 4.

Oracle Fusion Cloud Enterprise Performance Management July 2025 What's New


Content (please ensure you mask any confidential information):

Also, testName

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!