We are working to clean up a rather large list of child records (floors and spaces) that are attached to retired parent records (buildings). Is there an easy way to mass retire child records? Also, is there a workflow that can be run when a building is retired to avoid this issue in the future?
[Admin: To see other related posts, use the Retire 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.]
What is the “Integration” check box for in the workflow Start task?
Assuming you are referring to the Start task of an asynchronous workflow, when this property is selected, the workflow is used to migrate data from staging tables in IBM TRIRIGA records. This type of workflow is used extensively in IBM TRIRIGA DataConnect.
Check out this IBM Knowledge Center topic about DataConnect that describes the “Integration” check box: Workflow task settings.
[Admin: The same question is also posted in the main Application Platform forum. To see other related posts, use the Staging tag or DataConnect tag.]
I’m seeing issues within report results, where if the user profile language is in US English, the results are of one type, but if the user profile language is in German, it is showing some other data. The record while checked is the same for both cases. While opening and checking the record, the ID and name of the record varies from what it showed as a result in the report. While investigating, what we observed is that these fields are marked as “Localizable” in Data Modeler. What is the use and impact of the “Localizable” field property? Any suggestions?
Here is a PDF link to the 3.5.3 Globalization (Localization) user guide. Also, perhaps this technote on localized database storage will help provide some insight.
[Admin: The same question is also posted in the main Application Platform forum. To see other related posts, use the Localization tag or Language tag.]
We have some reservable spaces with system geography and system organization settings. A non-Admin user also has the same geography settings. There are security groups for reservations, and organizations and geography security groups are assigned to him. The geo and org security groups have the same geo and org as the space and profile. But the non-Admin user still isn’t able to see spaces.
He is only able to see them when the first level of the org hierarchy is provided in the group (i.e. \Organization). But as soon as the second level is given in the group, he isn’t able to see them. Can anyone help me on this? I think there is some issue in the org, but I don’t know exactly where it is.
[Admin: To see other related posts, use the Geography tag or Organizations tag.]
Filtering on a word in a date or date-time column produces unexpected results.
The platform treated any invalid string as “Today’s Date”. Moving forward, for query reports that have filters enabled, a check was added whenever a user attempts to use an invalid filter in a date or date-time field. If a non-date or non-date-time string is used in this filter, then a “No data to display” message is shown to the user in the body of the query results table, and zero results are returned.
[Admin: To see other related posts, use the Date tag or Filter tag.]
Object Labels and Revisions
Starting in TRIRIGA 3.5.3, consider converting the TRIRIGA as-shipped objects that you renamed and modified back to the TRIRIGA objects from which they originated.
The purpose of the new conversion process is to enable the objects to use the new TRIRIGA object revisioning capabilities while preserving your object modifications. When you make future modifications to the objects, the modifications are saved in object revisions. Ultimately, the object revisioning and object labeling capabilities and tools aid in the future upgrade of your TRIRIGA applications.
[Admin: This post is related to the 09.24.15 post about the best practices for configuring and upgrading TRIRIGA applications. To see other related posts, use the Best Practices tag or Object Label tag.]