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

Explicitely check transition conditions for follow up transitions and allow processes to have empty starting dialogs. #1506

Closed
svenoe opened this issue Dec 14, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@svenoe
Copy link
Contributor

svenoe commented Dec 14, 2021

We are enhancing how processes can be used with this comparatively small change significantly. Basically after a transition is completed, it will be explicitly checked, whether the conditions for the next transition are also fulfilled already and if so, it will be executed. This requires conscious setup of the processes, but it enables the admin to set up transition chains with various entry points, or optional acitvity dialogs, which will be skipped, if the information they provide is already present.

With this and also because it is needed to start processes via generic agent following CustomerTicketMessage, having activities without activity dialogs, and also having processes without starting activity dialog is not considered to be an error anymore.

@svenoe svenoe added the enhancement New feature or request label Dec 14, 2021
@svenoe svenoe added this to the OTOBO 10.1.1 milestone Dec 14, 2021
@svenoe svenoe self-assigned this Dec 14, 2021
svenoe pushed a commit that referenced this issue Dec 14, 2021
@svenoe
Copy link
Contributor Author

svenoe commented Dec 14, 2021

Basic functionality is implemented. Maybe some visual improvements or so will still come, closing the issue for now, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant