What HTML tags and attributes that can be used for outgoing mail messages and notifications from IBM TRIRIGA Application Platform?
The following lists cite the HTML tags and attributes that can be used for outgoing mail messages and notifications.
- HTML tags that can be used for outgoing email: html, head, title, body, h1, h2, h3, h4, h5, h6, p, br, hr, pre, em, strong, code, b, i, a, ul, li, ol, dl, dd, dt, table, tr, td, thead, tbody, th, input, form, select, option, textarea, blockquote, div, span, label, style, img
- Within the HTML tags, the following attributes are allowed: id, class, src, value, href, alt, width, colspan, rowspan, readonly, style, type, align, nowrap, height, valign, cellspacing, cellpadding, checked, selected
[Admin: To see other related posts, use the HTML tag or Email tag.]
I have a requirement. Whenever a user receives an email from the TRIRIGA application, the date-time should be displayed in local time, not the current server time. This should be based on different multiple time zones and not any particular one. Can anyone help me to achieve this through workflow activities in TRIRIGA?
[Admin: To see other related posts, use the Time Zone tag or Email tag.]
We are using IdP-initiated SAML, and we access TRIRIGA via a link that looks something like this: http://idpprovider/applications/Tririga. Can we pass this link in FRONT_END_SERVER in TRIRIGAWEB.properties so that users can click on the link that they get in a work task email, and they can be redirected to TRIRIGA?
SAML does not support basic authentication for non-browser clients. This is a SAML limitation. See the following APAR IV88274 link.
[Admin: For convenience, here are the meanings of the acronyms: Identity Provider (IdP), Security Assertion Markup Language (SAML).]
[Admin: This post is related to the 08.18.16 post about lack of support for non-browser clients. To see other related posts, use the SAML tag.]
We turned on the SSO in our environment. (1) If we want to connect to one of the forms on our system, it shows us that we need to login first. (2) But if I use the link in the email notification that TRIRIGA sent out, it will login and open directly. What’s the difference between these two methods? Is there a way to open a form directly without login?
Because the URL that is being used is an “anchor” (it uses the # character to define the parameter), it isn’t possible to use that in an SSO environment. So you need to determine what the underlying WebProcess.srv call is to that form. For example…
[Admin: To see other related posts, use the SSO tag.]
I’ve found that there’s an email address in both triPeople and My Profile. Sometimes these two email address can be different. Which one will be used when I create a triNotificationHelper in a workflow to send a notification out?
Emails will be sent to the email ID present in the My Profile of the person that you intend. Both triPeople and its My Profile will always have the same address unless you explicitly change it in the My Profile record, because whenever you make any changes to triPeople by revising, it will be carried forward to My Profile when saved or activated.
“Whenever a user submits a request for resource reservation, he gets a notification in his portal. However, I am not able to get that notification in a personal email like email@example.com. I have added this email in the user profile. Also, in the notification window, it shows that the external mail is firstname.lastname@example.org. But I am still not able to get any emails if I login in that email account.”
I have a similar question as well. I would like the service technician to get an email notification if the work task has been assigned to him. Is that possible in TRIRIGA?
[Admin: To see other related posts, use the Email tag or Notifications tag.]
I have two questions:
- (1) Is there any way to export the results of a query and send them as an attachment to a particular email ID?
- (2) Is there any way to schedule to get the report results and automatically send them in Excel to an email ID?
[Admin: This post is related to the 03.15.16 post, 05.04.15 post, and 01.24.15 post about sending BIRT reports via email.]