OfficeDev / OfficeDev/outlook-dev-docs

Action.InvokeAddInCommand - installation prompt does not trigger in the new Outlook Desktop client

Open
#1,005 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area: actionable messages
Dominant language
No language data
Stars
99
Forks
113
PR merge metrics
No merged PRs in 30d

Description

This acticle describes, that the installation prompt pop-up is supposed to be shown to user, if such Add-In is not installed.
(see screenshot below)
Screenshot 2023-07-04 141432

This code works as expected with the old Outlook Desktop, but the prompt does not get triggerred in the new Outlook Desktop.

                {
                  "type": "Action.InvokeAddInCommand",
                  "title": "${replyWithOutlookAddInButton.label}",
                  "addInId": "${replyWithOutlookAddInButton.addInId}",
                  "desktopCommandId": "msgReadOpenPaneButton",
                  "isEnabled": true,
                  "isPrimary": false,
                  "tooltip": "${replyWithOutlookAddInButton.tooltip}"
                }

Is there something different about the new and the old Outlook Desktop clients?
Feel free to ask for more details


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docs/actionable-messages/invoke-add-in.md and the documented Action.InvokeAddInCommand behavior. Reproduce the supplied payload in both old and new Outlook Desktop, then determine whether the page needs a client-specific clarification or whether the behavior requires product investigation; done means the discrepancy and supported behavior are documented or clearly handed off.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.