I have a requirement to show some records in a table as we are passing some batch data.
I know there was a ncolumntable function but looks like it is deprecated.
Can any one Help me with this?
Discussion posts and replies are publicly visible
For the above requirement you will have to do following things :
1. Prepare a HTML template like this and store in your KC :
<html> <head> <style> table, th, td { border: 1px solid black; } td{ word-break:break-all } </style> </head> <body> <p>Hello,</p> <p>Please find data below.</p> <table cellpadding="5" rules="none" style='width:100%'> <tr bgcolor="#CCCCCC"> <th align="center" >Col 1 with Link</th> <th align="center" >Col 2</th> <th align="center" >Col 3</th> </tr> ###Data### </table> </body></html>
2. Secondly you have to form data using HTML tags in your expression rule. Once formed you store in a PV.
To give link to one column you can use urlforrecord.
3. Go in Configure Send E-mail Setup
You have to select Use a text or HTML template .
Browse the template formed in step 1 and when scanned it will ask for Data, at that time map the formed data PV.
I suppose all this will be helpful to you
thanks for the information, can you be specific about how "form data using HTML tags in expression rule"?
regards,
L
That means that If you need to add. for example one name "David J", you will need to add it in this way
"<tr><td>David j</td></tr>"
tr means row, and td column---
got it, thanks.
I am having one issue here: for decimal value, when building the form data. it automatically cut to 7digits, like I have the value it's "2671266.78", it cut it to "2671266", tried function "tostring" and "touniformstring", it does not work. what we can do to keep the whole value?
Regards,
linp0001 said:for decimal value, when building the form data. it automatically cut to 7digits
This was already a very old thread, but now this is a completely separate topic from the original subject. I'd suggest you find other threads on the topic (i believe there are many), or if you can't, you could consider starting your own new thread with your question, instead of adding on to an unrelated post.
thanks, I will, and btw, do you have any idea how to fix it.
It's not as much of a matter of "fix" as it is, learning to understand what Appian is showing you and why - the way it renders numbers on the front-end is sometimes unintuitive. As I mentioned, other threads have gone over this.