New to using Breaking and Routing, but I do not see a way to tie the callContextClientData to UserFile (for email address) in Routing and Breaking. I can do with the ChangedBy/CreatedBy fields but not the user actually doing the reporting so they get a copy of the report/pdf.
Another approach IF your Epicor user IDās match your email addresses⦠you can āInsert System Constantā and pull in the āCurrentUserIDā. Then just append to the value to complete the email address with your @whatever.whatever
Very true, but just in case they ever donāt linking back to the EMailAddress in the UserFile, I avoid someone not doing what they should and breaking it
Are we editing the RDD to get UserFile in this case? My understanding is that breaks existing routings. If so, we have to redo routing from scratch, true?
I am not aware of making modifications to RDDās with existing routings breaking anything⦠unless of course you remove a table or columns the routing is using, or the routing is using a base RDD. Might run into a problem there, been awhile since I used APR
Thanks. Was told that at ARP EE, Insights '25. Perhaps I misunderstood. Perhaps not breaking but that RDD changes are simply not picked up by existing routings neccessitating re-do from scratch. Something like the routing āsavesā the RDD schema at creation and doesnāt update or some such.