[ALM Accelerator - BUG]: Connection Request To Another User Does Not Show In Configuration

[jfung85]

Describe the issue

We tried to setup a solution for deployment from Dev to Test environments with a Migration Function Account and requested the connections be created by a different Solution Function Account. However, after the connections are created by the Solution Function Account, we are unable to see them under the Migration Function Account.

Expected Behavior

We expect that the connections created by a different user would show up for the requesting account with an Unknown Connection label.

What component are you experiencing the issue with?

ALM Accelerator Canvas App

What solution version are you using?

Accelerator Version: 1.0.20230606.1(Managed)

Steps To Reproduce

We tried to setup a solution for deployment from Dev to Test environments with these steps:
Logged in as migration function account

1. We used the AA4PP Admin app to create a new project with the Project Wizard
2. We used the AA4PP app to configure a new deployment profile
3. For the solution, clicked on Configure Deployment Settings -> Under Connection References -> Click on icon for Request Connection from Another User

Logged in as solution function account

1. Open link to AA4PP sent from the migration function account
2. Create connections and the connections show as selected in AA4PP app
3. Check the Share checkbox for all connections
4. Click Save

Logged in as migration function account

1. For the solution, clicked on Configure Deployment Settings -> Under Connection References -> Connections are blank

Anything else?

We also tried to the following:

1. As the solution function account, click on icon to enter connection manually or view the selection connection id
2. Copy the ID to the AA4PP app under the migration function account to enter the connection manually
3. Click on Save and Close
4. After going back, the values are not saved under the migration function account AA4PP app Connection References view.

[mikefactorial]

Hey @jfung85 might need to get on a call to work through your open issues. Feel free to setup a call with Vasavi and ask her to forward it to me. My microsoft account was accidentally disabled recently so will have her forward it to me.

[mikefactorial]

@jfung85 @tomjosbin (re: #5981)

Updates based on our call. We did find two minor issues with the Deployment Settings screen loading when using the request a connection feature. There are 2 places where we were defaulting to values specified when the home screen loads and as a result the deployment settings were not saving correctly.

1. OnVisible of the Deployment Settings screen we need to add the following at the top of the OnVisible function

            Set(DeploymentSettingName, "Deployment - ");

2. OnSelect of the Save button on the deployment settings screen we need to replace the reference to

glrSolution.Selected.uniquename

with

SelectedSolutionToConfigure.uniquename

on this line

UpdateContext({locSolutionEnvironmentDeploySettingName: DeploymentSettingName & " - " & SelectedSolutionToConfigure.uniquename & " - " & SelectedDeploymentEnvironment.EnvironmentUrl});

These updates will be included in the August release.

[tomjosbin]

Thanks a lot Mike :)

[CoEStarterKitBot]

@jfung85 This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.