What is the use case? What do you mean by "an update", any field? That can add a significant load on the system. You could build a condition to check if a list of fields has changed and the trigger the comment.

Hi Ulto,

Normally you'd need to provide some expression for how best to make the field Mandatory, in your case the Comments. For example I've used the following expression:

If ${entity.LastUpdateTime <= now()}

Define Comments as mandatory

As you dont really know what field could be updated its about trying to use something which gives you the best way to capture the update to the record. Which is where the LastUpdateTime might be best. Otherwise you'd need to define quite a list of fields to see what content has changed as part of the After Change If statement.

Just one other thought that crossed my mind, the information for any updates are held in the History tab of the record.So any changes made will be stored there. Does that need to be replicated within the Comments section?

Thanks

Dave

This is an internal process in our company where we need to keep track on every update on the ticket that is being made. For example, even if the engineer is changing the status to Pending vendor, he needs to explain the situation in words also. 

Note that we used work in Service Manager, & the management wanted to implement the same thing. 

The expression will be provided for sure. There is a mandatory field that the engineer needs to modify whenever he's updating the ticket so we'll do the expression based on that field.

As i mentioned previously, we used to work on Service Manager, & we used to have the Journal Updates. 
The only way to keep the updates under one section with all the updates are the discussions. And since it's our process that the engineer should write a sort of update whenever he needs to modify the ticket, then we thought it's the best way to have it under discussions.

I will test it & will get back to you.

Thanks

hi Dave,

I set the Comments as Mandatory, however when I clicked on Save button (primary button - not the one in the discussion section), the record was saved however the comment was not added because the buttons in the discussion section are different, you need to add the comment & save. 

Can we customize this button to be on the top (primary) of the record? 

Hi Ulto,

Simple answer, No. You have to save the Comments first before you save the record. 

What you could do is have an after change rule that adds a comment based upon your Mandatory field being updated or changed.

You would then have a rule that looks something similar to this:

The problem with defining a field mandatory is that once the field has data in it, its then meeting the criteria for being populated not necessarily being updated each time.

So if you are saying there is a Mandatory custom field which must be updated then yes you could use the Rule Add Comment and take the value of what has been added and push this across to the comments.

You then see the following being held in the Comments:

Hopefully that at least gives you some idea of what you could do.