Skip to content
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

Cambio de status en no aprobar movimiento #171

Merged
merged 2 commits into from
Jan 5, 2022

Conversation

DanKazuky
Copy link
Contributor

Se ajusto en el interceptor en caso de que el movimiento no pueda ser realizado, devolver un status personalizado (452) para que el cliente detecte la alerta de no crear por evaluar movimiento, ademas se limpio codigo que sobraba en el mid.

udistrital/necesidades_cliente#303

Se ajusto en el interceptor en caso de que el movimiento no pueda ser realizado, devolver un status personalizado (452) para que el cliente detecte la alerta de no crear por evaluar movimiento, ademas se limpio codigo que sobraba en el mid.
@DanKazuky DanKazuky requested a review from AlexFBP January 4, 2022 17:10
@DanKazuky DanKazuky added this to Sprint Planning (To Do) in KRONOS via automation Jan 4, 2022
@AlexFBP AlexFBP merged commit 52d8bf3 into develop Jan 5, 2022
KRONOS automation moved this from Sprint Planning (To Do) to Sprint (Done) Jan 5, 2022
@AlexFBP AlexFBP deleted the feature/retornoMovimiento branch January 5, 2022 05:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
KRONOS
  
Sprint (Done)
Development

Successfully merging this pull request may close these issues.

None yet

2 participants