Run Batch scrips once when a correspondence is mixed with a CF change #257
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
On the Web UI, a response or comment on a ticket with a CF change at
the same times, makes TransactionBatch scrips run for the message/basic
fields transactions and another run for custom fields changes.
In Update.html, TicketObj was given to ProcessObjectCustomFieldUpdates
as $args{TicketObj} when this method works on $args{Object}. Without
Object, the method loads the ticket using the id present in customfields
ARGSRef, leading to a different object than the current batch one.
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.
On the Web UI, a response or comment on a ticket with a CF change at
the same times, makes TransactionBatch scrips run for the message/basic
fields transactions and another run for custom fields changes.
In Update.html, TicketObj was given to ProcessObjectCustomFieldUpdates
as $args{TicketObj} when this method works on $args{Object}. Without
Object, the method loads the ticket using the id present in customfields
ARGSRef, leading to a different object than the current batch one.