OfficeDev / OfficeDev/outlook-dev-docs
Action.InvokeAddInCommand - installation prompt does not trigger in the new Outlook Desktop client
Nobody has claimed this yet.
- 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)
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.
- ID: b948883f-055a-1e6a-791d-84338fc437a5
- Version Independent ID: 62b37158-dc1a-bfbe-d7ff-ba1963de950c
- Content: Invoke an Outlook add-in from an actionable message - Outlook Developer
- Content Source: docs/actionable-messages/invoke-add-in.md
- Service: outlook
- Sub-service: o365-connectors
- GitHub Login: @jasonjoh
- Microsoft Alias: jasonjoh
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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