-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hotfix - Flujos de trabajo - Evaluar valores vacíos en campos numéricos #8
Conversation
Actions executed at: 2024-01-18 08:26:57. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(A)Probado:
- Código revisado.
- Ejecución de Flujo de Trabajo con condición "is null" en campo Currency (al modificar y en planificador)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(A)probado
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(A)Probado
# This is the 1st commit message: Fix salesagility#10364 - Adding now option in Datetime fields # This is the commit message #2: Fix salesagility#10364 - Adding now option in Datetime fields # This is the commit message #3: Fix salesagility#10364 - Adding now option in Datetime fields # This is the commit message #4: Fix salesagility#10364 - Adding now option in Datetime fields # This is the commit message #5: Fix salesagility#10364 - Adding now option in Datetime fields # This is the commit message #6: Fix salesagility#10364 - Adding now option in Datetime fields # This is the commit message #7: Fix salesagility#10364 - Adding now option in Datetime fields # This is the commit message #8: Fix salesagility#10364 - Adding now option in Datetime fields # This is the commit message #9: Fix salesagility#10364 - Adding now option in Datetime fields
Descripción
A la hora de evaluar el valor nulo en lasd condiciones de los flujos de trabajo, se ha visto que los campos de tipo texto o fecha se recuperan como "", sin embargo los campos numéricos se estaban seteando a NULL. A la hora de comprobar si un campo era NULL, la condición miraba si el campo estaba como "". Se ha cambiado esta condición para que si el tipo es numérico y tiene valor NULL se altere el valor previo a la condición a "", sin afectar el valor en el resto del código (sólo para la evaluación de la condición), de manera que no haya efectos colaterales.
Pruebas