Skip to Content

Part 1: Introduction

Part 2: Configuration table and rendering class

Part 3: Creating a template and a demo report

Part 4: Conclusion

In order for this solution to be as efficient as possible, it should be both easy to use and even easier to maintain. In order to see which email and when to send it, the email framework reads data from a database configuration table.

/wp-content/uploads/2014/04/config_table_435133.png

Data element YERF_DTE_SOURCE_TYPE is defined by it’s underlying domain YERF_DOM_SOURCE_TYPE, which is also defined by it’s value range { ‘C’ (Content), ‘I’ (Image) }.

All this will make sense in just a little bit. So, here’s the rest of the structures:/wp-content/uploads/2014/04/config_id_435146.png/wp-content/uploads/2014/04/config_data_435147.png

/wp-content/uploads/2014/04/recipient_435148.png

/wp-content/uploads/2014/04/attachment_435149.png

/wp-content/uploads/2014/04/image_435150.png

/wp-content/uploads/2014/04/file_content_435151.png

/wp-content/uploads/2014/04/file_source_435153.png

The corresponding table types must be created. I’ve used ‘STR’ and ‘TTY’ for naming conventions and ‘T’ for database tables.

The following picture describes the rendering class which makes use of the above configuration:

/wp-content/uploads/2014/04/methods_435154.png

I haven’t directly inserted the code here, as the content would grow out of proportions, but I’ve attached the class in source code-based at the bottom. Also for this to work, a number of exception classes must be created.

The QUERY_DIR method can of course be rewritten using the /PLM/ framework. I chose not to do this because of authorization problems.

In the next part, I’ll show the steps to generate a template followed by a demo report.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply