Concept Idea behind Article's dynamic field and displaying

[hkais]

Hello to the Znuny developers,

I am currently struggeling in understanding and explaining, why the Articles Dynamic fields can be defined and modified by code, BUT there is NO option to display them nor to edit them.

I can select the article's dynamic field to be shown on AgentTicketZoom via the assignment UI, but the field is not showing.
My expectation would have been if I can assign it, that the field will be shown.

If this behaviour is intentionally implemented this way, can someone explain the benefit for it?
If the behaviour is a bug, in what version/commit is/was this bug fixed?

best wishes

[root]

Hi,

There is an option to display them and it's used by customer in real life:

SCR-20240716-nerj.png

Since the field always belongs to an article it is display within the article where it was entered. Showing it somewhere is makes nos sense without the article context.

The nature of an article is immutability and this is required to be revision proof. That's why there is only the option to add a field, but no way to edit a field. The same behavior like an article.

SCR-20240716-nenq.png

- Roy

[hkais]

Hi Roy,

thank you for your good explain.

Since the field always belongs to an article it is display within the article where it was entered. Showing it somewhere is makes nos sense without the article context.

The nature of an article is immutability and this is required to be revision proof. That's why there is only the option to add a field, but no way to edit a field. The same behavior like an article.
SCR-20240716-nenq.png

Getting the point of the idea of having immutable articles.
But how would you cover a business process where you require details from the articles attachment (e.g. document print date or signature date) and you will have multiple articles with the attachments in this ticket, so each article shall have this details at article level and not on ticket level.
If I understand you well, during processing the article, the content of the attachment has also to be parsed and cannot be modifed afterwards "officially", only with programmatically workarounds. But cannot imagine that this is the only option?

[hkais]

After thinking a few hours I would suggest a few feature

let Admin decide if the dynamic field is immuatable for the reasons of revision safety
if admin says, yes, this field shall only be editable during "importing/creating" the article
if admin says, no, this is a helper field to avoid additional clicks like in my previous named case, the users shall be able to edit them

[stephan14x]

Hi,

there is the option to create Ticket Dynamic Fields that you can edit at any time in Ticket Free Text Dialog.

Would that be a solution for you?

Stephan

[hkais]

Hi,

there is the option to create Ticket Dynamic Fields that you can edit at any time in Ticket Free Text Dialog.

Would that be a solution for you?

Stephan

Hi Stephan,

how can you display and edit article based dynamic fields there?

If you refer to ticket based dynamic fields, how would you implement my referred example with multiple documents but different dates. And the date shall be a helper field for the agents on article level?