Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Include All Keys in standardValue XML for add_standard_value_set_entr…
…ies Task from Entries Option with Backward Compatibility (#3820) ``` task: add_standard_value_set_entries options: api_names: CaseOrigin entries: - fullName: New Account label: New Account - fullName: Questionable Contact label: Questionable Contact ui_options: name: Add values to Case Origin picklist ``` For the add_standard_value_set_entries task, we noticed that only the fullname and label keys were being considered when generating the XML file for deployment, while other keys were being ignored. We've implemented a fix to ensure that all provided keys are now included in the standard value entry XML file. For example , If the entries were given like this , ``` entries: - fullName: testerunner label: testrunner groupingString: Scheduled ``` Now, it generates an XML like this ``` <standardValue> <fullName>testerunner</fullName> <label>testrunner</label> <default>false</default> <groupingString>Scheduled</groupingString> </standardValue> ``` But, there were case by case scenarios added for "OpportunityStage","CaseStatus","LeadStatus" which were left untouched to maintain backward compatibility and default will be always set as False, even though we pass in the entries as true. Related work item : [W-16541459](https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00001zQu1TYAS/view)
- Loading branch information