For the URLS and textual descriptions of payment values I would create other objects which provide that information.
For instance, to translate payment type codes into human readable text, have an object available to the template which when given a payment code returns the associated textual description.
In fact, a payment type code is an example of an "enumeration type", and your application probably has several instances of enumerations. So this is an object you could generalize and use for all of your enumerations. Having a single object would also simplify making this service available to the template.
This would work very much like the way localization is implemented in templates.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||