We have an issue from a user where he mentions that “Report filters for dates are not displaying properly”. This issue is happening when the user is using the triCreatedSY field in user filters. I added a date-time field to an existing report and chose the filter of “After”. When I run the report, the filter says “Contains” that also does not work. I entered the date of one of the items in the report and it did not return that item…
The system is providing the filter operator similar to the date fields, but it is not working no matter what date we give or what operator we use. We tried the same for other date fields which ends with “DT” but those work fine. I looked in the field properties of the triCreatedSY field and found the property “Sub Attribute Type = Created DateTime (Number)”. In the TRIRIGA user guide (PDF), I found the following information…
My understanding is if the user wants to use the triCreatedSY field, then we have to add a field “Created DateTime Number” on the BO. Based on the PDF, when I added a field on the BO, no information is getting populated in that field. It looks like there should be a way to map it. Is my understanding correct? Will it be a good solution to apply the changes as mentioned in the user guide? Or can we suggest an alternative to the user?
The triCreatedSY field is actually a timestamp field, so it acts like a string. You’ve started in the right direction by creating a new Created DateTime field, but it needs to be a Field Type = “System Read Only” and the Sub Attribute Type = “Created DateTime (Number)”. Note that previously created records will not have this field populated.
[Admin: To see other related posts, use the Filter tag or Date tag.]
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.]
Is there any way we can specify the sequence of resource attributes to appear in the JSON-formatted Get query output? We are looking for a pre-defined set of ordered resource attributes to appear in the OSLC Get query output.
You should be able to use the oslc.orderBy parameter to define the ordering of results. If you are talking about the default ordering without that parameter, then I think the query definition of the query capability should define the ordering.
[Admin: To see other related posts, use the JSON tag or OSLC tag.]
How do you run the MS SQL “SetVarcharColsToNumeric_MSSS.sql” and “SetVarcharColsToNumeric_MSSS_Publish_BO.sql” scripts after upgrading to TRIRIGA 188.8.131.52? According to the TRIRIGA 10.5.2 and 3.5.2 release notes:
- “There are two scripts for MS SQL, SetVarcharColsToNumeric_MSSS.sql and SetVarcharColsToNumeric_MSSS_Publish_BO.sql. Run SetVarcharColsToNumeric_MSSS.sql first. When it completes, run SetVarcharColsToNumeric_MSSS_Publish_BO.sql.”
- “Run the script PRIOR to installation of IBM TRIRIGA Application Platform version 3.5.0. NEVER run the script after upgrading to 3.5.0.”
Our application is 10.4 and platform is 184.108.40.206. How can the SQL script be applied to update the system fields with the sub-attribute type of CreatedDateTime to CreatedDateTime (Number) and ModifiedDateTime to ModifiedDateTime (Number)?
To update an element’s value that has a data binding from another element’s value (or other elements’ values), for example, a paper-input, you can set the attribute on-change for the paper-input to a custom function. You can define the custom function to set the element’s value however you want, for example, copy or concatenation.
In most cases, your UX application will consist of several pages that a user can navigate into and these pages may not necessarily be shown to the screen when the user initially accesses your application. If you are using the <link rel=”import”> tag to import your routing pages, the resources of these pages will be requested and loaded as the page containing these links is being accessed or loaded. If you have a complex application that consists of layers and layers of routing pages, it may not be good to load all your resources at once by using the <link> tag declaration.
In this article, we will show you how to lazy-load your pages to improve the performance of your application, if you are using a <triplat-route> component when handling their routing behavior. Here are the basic steps you need to do to lazy-load your pages:
- Do not use <link rel=”import”> when loading your routing page.
- Add the on-route-active event handler to your triplat-route declaration.
- Add the id attribute to your routing page declaration.
- Lazy-load your page using Polymer importHref API.
Let’s take a closer look at each step…