-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
External Meeting Response URL #3394
Open
tfreier
wants to merge
2
commits into
salesagility:hotfix-7.10.x
Choose a base branch
from
tfreier:meeting-response-url-hotfix
base: hotfix-7.10.x
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
External Meeting Response URL #3394
tfreier
wants to merge
2
commits into
salesagility:hotfix-7.10.x
from
tfreier:meeting-response-url-hotfix
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Dillon-Brown
added
the
PR:Type:Enhancement
Pull requests that provide more functionality. Associated Issues are called suggestions
label
Feb 14, 2018
cameronblaikie
added
the
PR:Community Contribution
These are contribution made by the community
label
Dec 3, 2018
Please rebase this pull request onto hotfix-7.10.x as the hotfix branch is now specifically for 7.11.x issues. Please take a look at our contribution guidelines for more information. |
Mac-Rae
added
the
PR:Wrong Branch
Pull requests that point towards a restricted branch such as master
label
Aug 5, 2019
Dillon-Brown
removed
the
PR:Wrong Branch
Pull requests that point towards a restricted branch such as master
label
Nov 22, 2019
mattlorimer
force-pushed
the
hotfix-7.10.x
branch
2 times, most recently
from
October 28, 2020 17:49
3149dea
to
ab954a4
Compare
Self note on language changes |
mattlorimer
force-pushed
the
hotfix-7.10.x
branch
from
November 5, 2020 22:05
1609e8b
to
b06335d
Compare
jack7anderson7
added
the
Outdated: Needs Review
PR needs reviewed as it might be outdaded
label
Mar 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Outdated: Needs Review
PR needs reviewed as it might be outdaded
PR:Community Contribution
These are contribution made by the community
PR:Type:Enhancement
Pull requests that provide more functionality. Associated Issues are called suggestions
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a new feature that allows users to define a custom URL that users who click on a response link within a meeting invitation get redirected to instead of seeing the standard meeting response page.
This PR is a copy of #1801 which I had created for the wrong branch)
Description
If the user defines a meeting response URL under Admin > AOP Settings. The meeting response page will forward to the set URL instead of displaying the standard meeting response page. If there is no URL set nothing change. Therefore this will only affect users that actively provide a value. In addition, it will append some variables to the URL to allow the response page to display some details about the meeting.
Motivation and Context
When SuiteCRM sends out meeting invitations the user is supposed to use the links to accept or decline the invitation. So far the response page has been very simple and there was no way to customize it either. In addition, it displayed a link to the meeting record in sugar which customers usually can't access. In my case, this kept me from using the meetings module altogether.
How To Test This
Types of changes
Final checklist