srinivasa mahendrakar

My feedback

  1. 363 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    srinivasa mahendrakar supported this idea  · 
  2. 168 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  API Management » Policies  ·  Flag idea as inappropriate…  ·  Admin →
    srinivasa mahendrakar supported this idea  · 
  3. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Logic Apps » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    srinivasa mahendrakar shared this idea  · 
  4. 81 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  Logic Apps » Designer  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    srinivasa mahendrakar commented  · 

    Hi Derek,

    Thanks for the response. Allowing multiple variable initialization in single action does help. Scopes will be used more and more as a mechanism to group various actions. We do need the ability to initialize variables inside. Its great if this restriction can be removed.

    And to the second point, when you have large Logic apps (specially in B2B processing) , its good if we have scoping for variables.

    srinivasa mahendrakar shared this idea  · 
  5. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Logic Apps » Workflow runtime  ·  Flag idea as inappropriate…  ·  Admin →
    srinivasa mahendrakar shared this idea  · 

Feedback and Knowledge Base