change value dropdown to name #21525
Open
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.
Checklist before requesting a review
Please delete options that are not relevant.
Description
A client reported an issue when exporting and re-importing business rules for tickets in an environment where ITIL categories were translated.
During export, the XML file contained the translated value of the ITIL category (depending on the user interface language), but during import, the rule engine only recognized the original (non-translated) category name.
As a result, importing rules failed when the export and import were performed in different languages.
The export process has been adjusted to always include the category name (fields["name"]), regardless of the interface language used at the time of export.
Change:
The XML export now returns the label (fields['name']) for dropdown references instead of the ID.
This improves readability and consistency with other export formats.
Modifications:
Updated the expected test in phpunit/functional/RuleRightCollectionTest.php to use fields['name'] when building the expected XML output.
Screenshots (if appropriate):