if you look at the Release delegate - you will find a public ‘AfterRelease’ method that you can plug into/over-ride with a graph extension. Well, for visual editor the problem stays.<Fields to Update After Transition> grid has the only fields from the Quick Check screen.For via code in workflow class, I guess, the same situation.I think it is not possible yet.Or should be some gimmicks to do this.Or it should be done as usual: via graph extension, via declaring a delegate and then declaring an extended method.
What the lessons I’ve learned with this case.Under server I’ll mean server or local PC where the instance is installed for developing or testing.Now() and NowUTC() functions utilize time of instance’s server, wherever it stands. Check time and time settings of your server. As well of your PC, if you access server remotely. GMT shifts may have same hours shift but different settings. E. g. the same GMT+X time zones may have different parameters for daylight savings time. Also, time zones settings may differ between different application (e.g. Acumatica and server’s OS). Might be surprises. Check time settings for the site and your user. Acumatica stores date/time fields in UTC. But may show converted to time zone of the server. When you enter in GI only the field (like [CRActivity.StartDate]) Acumatica will display it value converted to server time zone. But if you use the field in calculations, right, Acumatica use the value as it was stored (i.e. in UTC). Gratitude to @hkabiri for a t
With regards to your different times on different sites, have you checked the Site Preferences? Yes, this was the point. But not of the instance itself – of instance server.
@kbeatty21 , no, this is not the issue for this case.But your advice helped me to solve another similar issue.We tested GIs on different servers, and different sites had different time settings.But we did not pay enough attention to this.
I checked system resources, and have found out that the notifications queue is overfull.To discover this I used the System Queues Monitor (SM302010) screen.In my case it has dozens of thousands 😲 notifications. And thus new events may not wedge into to the queue.About further actions. I wait for the customer confirmation to perform queue cleaning and (as next step) application restart.
@olexandrProkopovych94 - you may want to try a restart on the customer instance 💡 Your proposition gave me an idea what to check!
@dherr70 , The T190 course (let's say) is the shortened version of T200-T250.Thus it's better to deploy a new instance. And there to create a new customization for training.
@olexandrProkopovych94 I was able to create and trigger the same BE you have shown in version 21.123.0012 Well 🙄, I am also able to trigger an event on the local instance restored from customer's instance snapshot.But I may not trigger on customer's instance.
@olexandrProkopovych94 what are you using for a Trigger condition on the BE / Trigger condition Tab ? @dales50 , for testing I've used even the simplest, but it had no impact.I think, there is some issue with the system or the screen. Like someone or something forbids or overwrites triggering of events.
Does it show any errors in business event history? That is the trick, the event even does not appear in the Business Event History screen. 😥
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.