I just discovered Message Template Maintenance ! Now when we reset the password, I can send a more meaningfull message in french with details on how to proceed to set it.
It is all fine but, I do those resets both in Prod and in Training env. I can add in the subject the word Production in Prod, and in Training the same ..
The problem is when I restore Prod into Training, the template will have Production in it’s subject, since the DB got replaced.
The ideal would be to have the ability to add a dinamic parameter to be added into the template that we can add the environment, name of the user etc…
How can I acheive that? I saw the {0} which is the new temp password… but can I set up more ? via a BPM ? how to proceed then to use it ?
Anyone done this ?
Ideally, being able to add fields the same with a BPM email would be great !
I know I could add a line in my post-restore script to change the info in the Ice.MessageTemplate , but eventually we will go saas and I have read it will not be available to do that… So bpm way might be a more longterm solution unless future versions of Epicor has this ability already (I am currently on 2022.2.40 )
Ohh OK, so the BPM would send the email instead of being from the template ? what is needed to make sure the template is not fired ? For instance, if the env is not PROD, use the bpm email and cancel the use of the template, else it will use the template (or not use another email from bpm…so cancel the template whatever env… ) Or canceling is not possible ?
For BPMs I have a Condition widget that checks the SysCompany.IsLive field to see if it’s true. If so then that’s PROD if not it’s Pilot or other non-PROD version.
Edit: Just need to make unchecking that box in Company Maintenance part of your DB refresh plan.
in the BPM, I noticed there is condition with that purpose:
Under the admin console, server management, there is the option “Set as Production” (we never set it… ) but this condition uses this option…
But for me I would need to Remove Production Status when I restore in my 2 other environments…it is not something to be done via a sql script I was told … so manual activity to not forget during restore process…