Hi @Samuelraj
You can't really prevent that from being updated after it is changed like that very easily. You can create an automation like Mohamed suggest to set it back to the previous value - and I would also email the user and tell them not to update it in the future.
What I would do is create a custom date field that is not on the screen. Then when the date is updated the first time, capture the date.
The other option is to have the date on the Create screen but not the Edit screen. So if it is added during the create process, then it cannot be changed later. This is the easiest solution.
However, if it will not always be added during the create process but added later, then you create a new screen that just has the date field on it. Then you could do the above Create and Edit screens and add a self looping transition to the status. There attach the screen to the transition that only has the date field on it.
I would still create a custom field - but it can be a date field or any other type really, that is populated when the field is first populated - basically the same automation above.
I would then also add a few conditions to the self looping transition that 1. Only allow the Assignee to execute the transition and 2. the custom field is empty. So once the field is populated the first time, the custom field is populated. Then subsequent tries to update will not show the self looping transition to the user so therefore, they cannot update the field. I would also add a Condition that allows the Admin group to perform the transition so that someone has the ability to update it if necessary.
That's a very long and sorted way to do it, but you could achieve it that way.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.