-
Notifications
You must be signed in to change notification settings - Fork 75
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
DynamicFieldDB don't work in processes in the agent interface #1659
Milestone
Comments
reneeb
added a commit
to reneeb/otobo
that referenced
this issue
Mar 11, 2022
… only when it is present. Otherwise the field name becomes '' and that leads to error messages in the system log ('Need DynamicFieldName') and to JavaScript errors as it cannot find the field in the dialog.
svenoe
pushed a commit
that referenced
this issue
Mar 14, 2022
…n it is present. (#1660) Otherwise the field name becomes '' and that leads to error messages in the system log ('Need DynamicFieldName') and to JavaScript errors as it cannot find the field in the dialog.
stefanhaerter
added a commit
that referenced
this issue
Mar 14, 2022
…he expression IndexOfActivityDialogID > 0 to return false, so the name is not shortened
svenoe
pushed a commit
that referenced
this issue
Mar 15, 2022
…he expression IndexOfActivityDialogID > 0 to return false, so the name is not shortened
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you use a dynamic field of type DB in an activity dialog in the agent interface, it doesn't work. You can search for values, but you can't use them.
The JavaScript code assumes that the activity dialog id is appended to the field name (as it is in the customer interface) and hence it cannot find the field in the activity dialog.
The text was updated successfully, but these errors were encountered: