[ARA] Executing ARA workflow in V12.1 now pre-populates package and profile based on the previous execution.

Document ID : KB000101734
Last Modified Date : 03/07/2018
Show Technical Document Details
Question:
Behavior on 12.0: Executing a workflow you always need to specify both profile and package. This helps when starting a workflow as to make a conscious effort in specifying the correct parameters
Behavior in 12.1 Executing a workflow now pre-populates package and profile based on the previous execution. This is dangerous as it leads to unintended deployments when in a hurry.
Is it a bug? We expect a fix for this to be able to revert to the old functionality (always ask for package and profile).
Answer:
This is not a bug. System works as designed. In an upcoming release of ARA there will be the possibility to configure the auto-fill behavior for that dialog
Since this also cause a lot of trouble to our customer which currently in V12.1 so we also provide a fix in Release.Manager 8.0.2
The section in customer.config should look like this
<add key="ExecutionDlg.DeploymentProfileAutoFill" value="true" />
<add key="ExecutionDlg.DepolymentPackageAutoFill" value="false" />
<add key="ExecutionDlg.InstallMode" value="overwrite" />