-
Notifications
You must be signed in to change notification settings - Fork 3
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
Use StatusFlowTransition instead of StatusValidChange #34
Comments
ravilodhi
added a commit
that referenced
this issue
Dec 24, 2024
ravilodhi
added a commit
that referenced
this issue
Dec 24, 2024
ravilodhi
added a commit
that referenced
this issue
Dec 24, 2024
…it is already handled at framework level (#34).
dixitdeepak
added a commit
that referenced
this issue
Dec 24, 2024
Fixed: Used StatusFlowTransition entity instead of StatusValidChange (#34)
ravilodhi
added a commit
that referenced
this issue
Dec 26, 2024
…ting services for create/update cycle count and to update cycle count item. (#34)
ravilodhi
added a commit
that referenced
this issue
Dec 26, 2024
dixitdeepak
added a commit
that referenced
this issue
Dec 30, 2024
Improved: Used entity auto services and secas directly instead of writing services for create/update cycle count and to update cycle count item. (#34)
ravilodhi
added a commit
that referenced
this issue
Jan 2, 2025
dixitdeepak
added a commit
that referenced
this issue
Jan 2, 2025
Fixed: Corrected service to update inventory count import item (#34).
dixitdeepak
added a commit
that referenced
this issue
Jan 10, 2025
Fixed: Set statusDate correctly when recording inventory count import status change (#34).
dixitdeepak
added a commit
that referenced
this issue
Jan 10, 2025
Updated: Changed version to 2.0.1 for patch release.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: