...
b) An accordion (or any other UI Element) that would list the context sensitive “placeholders” for the selected entity in an visually (easily visually ) discernible manner.
Placeholders would be used in the rich text editor enclosed by “${}” for easy detection and parsing Ex :${clientName}
...
Ex: The placeholder ${repaymentSchedule('date','principalAmount','interestAmount') } would create a HTML table for repayments with the table columns based on the passed in parameters ‘date', 'principalAmount', 'interestAmount'
2 Parser
2.1 Server Side Parser
Ideally, we would have a parser at the server side (Java) which would replace the placeholders with context sensitive data and then serve HTML reports to the Client.
Some of the advantages of having the parser at the server side would be
- Better performance
- We can carry out various optimizations like fetching values for only those placeholders which are present in the particular document
The Restful URL for server side document generation would look similar to
/{entityName}/user.defined.report/{reportId}?entityId=10
where
| Wiki Markup |
|---|
{entityName} = Name of the entity (Client, Loan etc)
{reportId} = The Identifier for the report template
entityId = An Identifier for compound Entities (Ex: The Loan Product Id for a Loan) |
Alternatively, we could also have services at the server side that exposes the context sensitive data and a Client side parser that would take care of merging the report template with the actual values exposed by the RESTful service
...