TicketArticleCreate modified table #12
Open
Conversation
This file contains hidden or 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
Subject description fixed. From and To is only mandatory if CommunicationChannel is EMail (I guess?)
|
TLDR: To and From and not mandatory The From is needed for the CommunicationChannels Email, Phone, and Internal. If no From is provided, it is generated based on the parameter UserID (== the current user if this parameter is not used in the transition action). |
rkaldung
approved these changes
May 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Subject description fixed. From and To is only mandatory if CommunicationChannel is EMail (I guess?).
The fields
ToandFromseem to be not mandatory if Communication Channel isInternal. I guess you only need those fields if CommunicationChannel is set to EMail?