Robbie Nati wrote:
Why email screen need to be charge as one AO...?
In that case, i would rather create an "Email setup page" with "Subject", "Content", "Receiver". Then fetch the respective email content and construct the email on the fly. With such design, i will save a lot if i have 50 different email template :D
True, but the objective of both SU and AO is to account for the advantages you get by using the platform features.
You can work around not using them, but in long term it affects developer productivity, learning security and maintenance of your application.
João Rosado wrote:
I think the same way, but I am disappointed when I realized the email can't attach pie chart