Is there a way to add the effective date of an address change to the approval email template. It is not one of the text variable replacements on the Resource Address templates. Thank you.
Not sure this is the best approach, but the only thing I can think that may work would be to complete the following:
I have not tested this process myself, but that is how I would get started if we had the same need.
Hope this helps at least give you some ideas.
BJ
Hi BJ,
I ended up using {lpl:BusinessClassRequest.EffectiveDate} on the template and it picks up the effective date the employee put on the change address request.
I have not known effective date to be on a business class. I have only seen it available for ISD uploads. But if you know how I could use that EmployeeContact_effective_date or other effective dates when creating a new field, I would really like to know.
Thanks,
Shannon
Hi Shannon,
Based on your reply, it may be easier to do what you want on the template than what I initially outlined. ☺️
Infor has effective dates on almost every business class, yet they like to keep them pretty hidden within the user interfaces after the initial create or update actions occur because of the negative impact that could be created if one was to change incorrectly.
The reason you can see the effective dates within ISD when performing an upload, is because often times the true effective date of the data being imported may differ from the current date the import is occurring. In that case, if you did not set a specific effective date during an import, most business classes will default to the current one. The presence of an effective date within ISD is also an indication it is a field stored on the business class.
For your specific request, you may try updating the template and set the LPL to:
{lpl:EmployeeContact.EmployeeContact_effective_date}
This "should" work as I would assume there is already a natural relationship between all the business classes at play to make it work. However, if nothing appears, then we would have to trace the relationships and determine which one we could use to make the appropriate connection between EmployeeContact and EmpAddressEmailTemplate. Once the proper relationship is found, or created then your field on the template would look something like {lpl:EmployeeContactRel.EmployeeContact_effective_date}
Anytime I start to do this type of work I always use the "CTRL + SHIFT + Left Click" combination on the field I want to use within the application. That provides the business class and name for my source. From there, I review the destination and determine the best path forward.
