CASE CHG-63840-19-301663:
The functionality is implemented to allow the homologation of additional fields between different types of cases and models, as well as for the change of models in tasks. For correct value homologation, fields require certain conditions to be met based on the field type.
Admin Console
In order to carry out the homologation of additional fields between models, two essential conditions must be met: Field Type and identifier they must be equal.
Note: As of this release, the creation of additional fields with the same type and identifier within a model is not allowed. If fields with the same type and identifier already exist in a model, the homologation process will take the first field it finds and that meets the specified conditions.
Specialist console
During the creation or editing of cases or tasks, the homologation option will be available in the following scenarios:
- Change of service.
- Change of category.
- Convert from grid.
- Convert to Case Edit.
- Change of model in tasks.
A modal will be displayed requesting confirmation to proceed with the homologation of the additional fields.
For the values to be homologated correctly, the fields must meet the following conditions
| Fields | Conditions |
|---|---|
| Text | They should be the same length. |
| Catalogues | They must have the same catalog assigned. |
| List Tree Multiple Choice |
The value to be approved must exist in the values of the new model. |
Notes: 1. In the Tree and Tree Catalogue fields, it is validated that the value to be approved is selectable in the new field. 2. In the multiple choice field, the existing values are standardized. 3. When homologating to a field marked with dependency, the values are not homologated.