YetiForceCompany / YetiForceCRM

Our team created for you one of the most innovative CRM systems that supports mainly business processes and allows for customization according to your needs. Be ahead of your competition and implement YetiForce!
https://yetiforce.com
Other
1.74k stars 749 forks source link

[bug] Cannot see results of workflow "Update fields" #13010

Closed joao-penguin closed 4 years ago

joao-penguin commented 4 years ago

When a field is updated through workflow Update fields, result is not displayed to the user Nevertheless update is properly performed as a refresh enables user to see the change. I think that after workflow task execution, Yetiforce should read data from database to get & display last version of data.

Hereafter test configuration

Screenshot from 2020-05-11 11-59-40

Screenshot from 2020-05-11 12-00-03

Screenshot from 2020-05-11 12-00-15

Hereafter test I create a correspondance After create, field "date of receiving" is empty: normal Screenshot from 2020-05-11 12-00-49

After update, field "date of receiving" is empty: this is not the expected value Screenshot from 2020-05-11 12-01-09

After refresh, date is set Screenshot from 2020-05-11 12-01-25

apcloic commented 4 years ago

@joao-penguin I suppose you are using quick edit instead of full edit record. I don't think it's a good idea to do a refresh in this case because then it will slower the process while the goal is to be quick. Regards,

joao-penguin commented 4 years ago

Thanks for the quick answer. I agree that refresh the page will slower the process and should be done with caution. But in my use case, to see the result, user has to refresh the page, either by F5 or by going to full edit (that generates a full refresh).

A workaround would be to use a "custom function" Is there a way to force yeti to refresh the page content ?

KatarzynaUlichnowska commented 4 years ago

Hello, thanks for submitting an issue, as far I know, you are in contact via e-mail with one of our team members and you are waiting for a quote. Therefore, I will close the issue.