Below are some of the Enhancement Requests (ERs) which we have introduced in BWCE 2.10.0 Hotfix-02 and BW 6.11.0 Hotfix-02

1. BWCE-8874
++++++++++++++++++++++++++++++++++++++++++++++++++++
Description:
============
A new BWDesign utitlity command "system:createProcess" is added to create empty process and subprocess in the imported project.

Details:
============
New BW design utility command added to create empty process or subprocess. Below is details:
DESCRIPTION
    system:createProcess
    Create an Empty Process or Sub process in your imported Project
SYNTAX
    system:createProcess [option] [moduleName] [processName] [packageName] [modifier].
ARGUMENTS
    modifier (optional)
        Default Value: public
        The type of process you want to create, values can be ""public"" or ""private""
    process
        The name of the newly created process
    package
        The name of the package under which the empty process is to be created, can also be a new package name
    module
        The name of the module you want to create a new empty process in
    option
        -p will create a Main Process, -s will create a Subprocess
++++++++++++++++++++++++++++++++++++++++++++++++++++

2. BWCE-8338 (This is only applicable with BWCE product)
++++++++++++++++++++++++++++++++++++++++++++++++++++
Description:
===========
Encrypt the clear-text versions of the environment variables values in envVar.properites file

Details:
=========
By default BW_ENCRYPT_ENV_FILE is set to false. It won't encrypt envVar.properties values. We can set BW_ENCRYPT_ENV_FILE to true to encrypt the environment variables values in envVar.properites file
++++++++++++++++++++++++++++++++++++++++++++++++++++

3. BWCE-8209
++++++++++++++++++++++++++++++++++++++++++++++++++++
Description:
============
Added support for Automatic update of process diagram - .bwd File Generation in BWCE Designer

Details:
===========
We need to check the 'Auto Generate Process Diagram on Save' checkbox, which is located under Windows -> Preferences -> Process Diagram -> Generate Process Diagram. 
Note:  The process diagram will be generated if only if we modify the process/subprocess

Reference: AMBW-51989"
+++++++++++++++++++++++++++++++++++++++++++++++++++++

4. BWCE-8031 (This is only applicable with BWCE product)
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Description:
=============
Added support to encrypt the environment variable which we use to connect to Secret Manager

Details:
=========
We can now provide the engine variable AZURE_CLIENT_SECRET  obfuscated values to connect to secret manager.
+++++++++++++++++++++++++++++++++++++++++++++++++++++

5. BWCE-7649
++++++++++++++++++++++++++++++++++++++++++++++++++++++
Description:
============
Added option to add Assertion to the Input Mapping along with Output Mapping

Details:
=========
For activites like Log which only contains input, support has been added for Add Input Assertion option. Right click on activity and select the Add Test option. Add Input Assertion would be visible.

Know Issue: Input Assertion for activities in a Sub-process is not possible
++++++++++++++++++++++++++++++++++++++++++++++++++++++

6. BWCE-7926
++++++++++++++++++++++++++++++++++++++++++++++++++++++
Description:
============
Support to turn off output validation for Parse JSON activity when the Schema Type selected is XSD.

Details:
=========
A new checkbox ""Validate Output"", is now added on the General tab of Parse JSON activity when the Schema Type selected is XSD. If a user wants to turn off the validation for Parse JSON activity, they can uncheck this checkbox. It is checked by default. This checkbox is hidden when the Schema Type is Generic. When users uncheck the Validate Output checkbox, the ""Ignore Additional JSON Fields"" checkbox is hidden, since it will have no meaning in this scenario.
In the runtime, we have introduced a new system property ""com.tibco.plugin.restjson.parse.validateop"" which takes precedence to what's chosen in the Validate Output checkbox UI. It is declared to be true by default, and we can set it to false to turn off validation.
++++++++++++++++++++++++++++++++++++++++++++++++++++++

7. BWCE-8937
++++++++++++++++++++++++++++++++++++++++++++++++++++++
Description:
============
Support for superclass fields in JavaToXML and XMLToJava activities

Details:
=========
The Java palette activities Java To XML and XML To Java now support classes with parent-child relationship.
To include fields from superclass in activity input/output select the ""Include SuperClass"" checkbox before browsing the child class using the Browse button.

Notes:
1. The fields from superclass which follow the conversion rules will be included.
2. If there are multiple Java To XML or XML To Java in a process that refer to the same class, then the ""Include Superclass"" checkbox configuration should be same for them.
EG: If activity1 and activity2 refer to the same Java class and you wish to include superclass information then  ""Include Superclass"" checkbox should be checked for both the activities before browsing the required Java class.
++++++++++++++++++++++++++++++++++++++++++++++++++++++

8. BWCE-8888
++++++++++++++++++++++++++++++++++++++++++++++++++++++
Description:
============
Add support for previous otel lmetrics meters to support backward compatibility

Details:
=========
The enhancement is done to support the Previous format of the OpenTelemetry Metrics Meters.
With this ticket, we have made certain changes where the OTel metrics will be available in both the Format. i.e the old format(The capital meters) and the new aggregated meters for the lmetric data.
With bw.tibco.remove.individual.otel.lmetrics, the old format metrics meters can be removed and only the newly added aggregated one will be present.
++++++++++++++++++++++++++++++++++++++++++++++++++++++

Enhancement Requests (ERs) introduced as a part of BWCE 2.10.0 Hotfix-02 and BW 6.11.0 Hotfix-02