Open designer and add trigger.
Add compose action.
Issue: Before showing the parameters it shows tab headers, blank and then Change connection for sometime before parameters are rendered.

AB#15929196

AB#15949666

When using a switch statement with multiple conditions and saving, only 1 condition and default is actually serialized. Renames of conditions is also ignored.

AB#15928528

After clicking, nothing happened.

AB#15952686

Rero steps -

1. Create manual trigger and add Service bus action.
2. Expand the queues parameter.
3. it shows Enter custom values and suddenly shows the items.

Expected: It should show some kind of loading indicator if it is fetching the items. IN case of errors it should show the error.

AB#15949756

Create an action and have it run after multiple other actions. delete the other actions that it runs after - we have a UI Bug

AB#15929158

AB#16010925

AB#15919811

AB#15919832

AB#15919848

AB#15929131

AB#16117203

Tracking issue for:

• https://github.com/Azure/logic_apps_designer/security/code-scanning/6

I created a workflow trying to invoke another workflow in the logic app. Validation failed saying the workflow could not be found although it did exist in the logic app. After deleting the "Invoke another workflow" action, validation now fails with this error.

AB#15953157

AB#15952496

Repro Steps:

1. Open a node with an accessible token somewhere
2. Click Add Dynamic Content to hide the token picker
3. Click on the token
4. Token picker stays hidden

AB#15952250

Create a new workflow and open designer
Add request trigger.
Add the below schema -

{
    "properties": {
        "arrayData": {
            "items": {
                "properties": {
                    "item": {
                        "type": "integer"
                    }
                },
                "required": [
                    "item"
                ],
                "type": "object"
            },
            "type": "array"
        },
        "objectData": {
            "properties": {
                "A": {
                    "type": "string"
                }
            },
            "type": "object"
        }
    },
    "type": "object"
}

Go to settings and check
Result: It only shows Secure data and inputs. Its missing all the other along with split On.

Old designer -

New designer -

Scenario 2 -
On reload of this definition, its still missing the split On and custom tracking Id.

AB#15929267

AB#15929299

AB#16116576

AB#15929300

AB#16140942

Seems to be a race condition. Only reproed once and couldn't while recording.

AB#15952064

AB#15949675

AB#15929264

AB#15995623

Scrolling anywhere on the canvas will scroll the canvas as expected, but scrolling on the react-flow controls (minimap or control/zoom buttons) causes the whole page itself to scroll.
When we render designer in Portal there is a 100vh css val that results in some hidden overdraw that we only experience in this one scroll instance.

AB#15952156

AB#15929309

AB#15949670

Repro Steps:

1. Open a node's settings
2. In the RunAfter settings, click the Select Actions dropdown
3. Click on the existing RunAfter, and it will be removed, leaving the node with no parents (how sad)

AB#15952336

1. Create a new action with a new connection
2. Click a different Action
3. Go to Original Action
4. No longer see Create a Connection

AB#15929207

AB#15949660

We shouldn't allow variables in the variable name - causes designer to crash when modifying the workflow

AB#15983293

1. Choose GET as the method for request trigger

2. Open dropdown for method parameter

3. Delete the value and press enter

4. Switch to a different parameter
   notice that there's no value shown for method parameter
   

5. Switch to code view, the old value is still there

AB#15952859

AB#15929216

AB#15952554

1. open workflow https://ms.portal.azure.com/?feature.canmodifystamps=true&Microsoft_Azure_EMA=newdesigner&microsoft_azure_ema_enableNewDesigner=true#view/Microsoft_Azure_EMA/WorkflowMenuBlade/~/designer/resourceId/%2Fsubscriptions%2F80d4fe69-c95b-4dd2-a938-9250f1c8ab03%2FresourceGroups%2Ftonyrg0%2Fproviders%2FMicrosoft.Web%2Fsites%2Fiatest0%2Fworkflows%2Fstate/location/East%20US%202%20EUAP/isReadOnly~/false

2. add an as2 action

3. select Transform JSON To JSON
   NOtice the wrong card is shown
   

4. select a another action and select 'Transform JSON To JSON' again
   now the correct card is shown
   

AB#15952646

1. Add Http action in the workflow.
2. In authentication parameter select Managed Identity and OAuth.

Result: The placeholders do not seem to be properly aligned and also the left alignment of its properties are different.
Expectation: Even though it has sub properties either all of the sub properties should have label in left and value in right or it should be label top and value bottom

Also even though managed identity is selected for the logic app it still shows the error above.

AB#15958393

AB#15929260

AB#15994617

AB#15929327

AB#15995639

AB#15808200

The command bar is using V8 so the background color wasn't set appropriately. The color should be the following (might need to use custom value for now)

1. Background color: colorNeutralBackground4 (#F0F0F0 for light, #0A0A0A for dark)
2. Text color: colorNeturalForeground1 or used whatever the current Azure theming provide for light and dark
3. Icon color: colorBrandForeground1 or used whatever the current Azure theming provide for light and dark

https://github.com/Azure/logic_apps_designer/blob/main/libs/data-mapper/src/lib/components/commandBar/EditorCommandBar.tsx

display name should be required

AB#15952520

Open below workflow and it's shown as dirty
https://ms.portal.azure.com/?feature.canmodifystamps=true&Microsoft_Azure_EMA=newdesigner&microsoft_azure_ema_enableNewDesigner=true#view/Microsoft_Azure_EMA/WorkflowMenuBlade/~/designer/resourceId/%2Fsubscriptions%2F80d4fe69-c95b-4dd2-a938-9250f1c8ab03%2FresourceGroups%2Ftonyrg0%2Fproviders%2FMicrosoft.Web%2Fsites%2Fiatest0%2Fworkflows%2Fstate/location/East%20US%202%20EUAP/isReadOnly~/false

Doing a diff shows that the inputs was removed

AB#15952749

AB#15949655

Repro steps:

1. Create a new Action
2. Actions running after the newly added action do not show the output tokens in the token picker

AB#15948346

AB#15949772

AB#15843430

AB#15929104

AB#16117207

AB#15929292

AB#16029245

Repro Steps:

1. Open a workflow
2. Before the nodes load their operation data, open the panel by clicking on a node
3. While the data is loading, the application thinks the node is missing a connection and sends the user to select/create a connection, instead of showing the loading state with the default tabs

AB#15952065

AB#15929148

Repro Steps:

1. In a workflow, create a Scope node, then another Scope within
2. Click and drag the parent Scope node header inside of the child Scope node
3. This operation should be counted as illegal, but the action is allowed and just deletes both of the nodes

The issue:

• Scope nodes cannot be drag-moved into themselves, but that is only checking the graph-id of the new position
• The nested position only checks the nested graph-id, so it looks valid

AB#15951748

AB#15929297

AB#15995588

1. Create new workflow and open designer
2. Add reuqest trigger and open search for adding action.
3. Now select InApp any service provider action like - Event Hub
4. Go to settings

Result: Network setting header shows up but there are no settings inside.

AB#15929180

AB#15958341

AB#15952316

AB#15929305

AB#15980323

Repro steps -

1. Create a new workflow in workflow app.
2. Open designer and add request trigger.
3. Add any action like Invoke a workflow / Compose.

Result: Create connection tab shows up instead of parameters even though this operation does not require any connection.

Note: Operation additions were done very quickly, maybe a race condition.

AB#15956558

If you click and drag what you think is the background next to an edge's add-node button, the drag is blocked by the drop target on the edge button.

This blocks any mouse interaction like primary/secondary clicks as well.

AB#15952523

Repro Steps:

1. Open a workflow
2. Before the nodes load their operation data, open the panel by clicking on a node
3. When the operations finish loading their data, the panel closes instead of just updating with the data

AB#15952039

AB#15929270

AB#15996185