Feeding your TRIRIGA information needs

Tag Archives: Environments

The user template of the source environment replaces the user template of the destination environment of the same person record after an OM import. In TRIRIGA 3.5.2, when a triPeople user template is migrated from one environment to another, if a user’s people record is associated with the string “Applied Template” in the source environment, the most-recently applied template will be applied to same user’s people record in the target environment.

For example, user James Sullivan has a Project Team Member template applied in the test environment. In the CERT environment, user James Sullivan has a Facilities Manager template applied. But when the Project Team template is migrated to the CERT environment, the template is applied (instead of the Facilities Manager template) to James Sullivan’s people record.

This is working as designed. The root of the issue is that when an OM that has a people template is imported from the source environment to the target environment, and when the published name of the user profile record is the same in both the source and target environments, it will NOT replace, but create additional associations from source to target. All of these associations can be seen in the Associations tab of the user record. However, the form will show that latest template that was applied.

I recently set up a new environment in which I need to migrate the classifications (not just the record data) from the existing system. What is the fastest way to do this and ensure that the classifications are set up properly in the new system?

I migrated the BOs and forms. I checked the Include association for the BO to itself and with the classification BO. The form has been added to the “Includes/Forms” tab of itself as well as the classification form. But I still don’t see this BO added under the classification hierarchy when I click on “New” to create the root record.

I have a couple of software development life cycle (SDLC) questions about Perceptive apps using the TRIRIGA UX Framework:

How do you export changes to Perceptive app components from one environment to another, without exporting the whole application? Example components include web view files and data sources. Currently, if we only change and test a data source or web view in Dev, we cannot figure out how to export them from the Dev environment and import them into the system integration testing (SIT) environment.

How do you add an existing data source to an existing model? We only found an Add button to add a new data source. We would like to associate a pre-defined data source to a model.

TRIRIGA currently supports exporting of the whole app, so you cannot export only a data source. For web view files, you have the option to use the WebViewSync tool to pull the files from one environment and push them into another.

About adding an existing data source, the data sources were designed to be part of a model and that’s why there is no button to add an existing data source to a model. However, you can manually associate them by using the Association tab.

We have a Training environment, which is a copy of a Production environment. The Training environment is on TRIRIGA 3.5.2.1 and the source came from a TRIRIGA 3.5.1.2 Production platform. We are witnessing unusual behavior across the Training environment, including the following case.

Within the Contact Center, we select the Requested By, which we would expect to auto-populate the Requested For and a number of other fields. The OnChange workflow that takes care of this fires, but the first workflow task (Get People Record) returns 0 results the first time around, causing the Modify Record tasks later in the workflow to fail. When we attempt to clear the Requested By field, the OnChange workflow is called again and this time, fires and then maps the data as it should have done with the first process of selecting the Requested By.

We needed to call an internal platform construct a different way. This is a regression because of the Spring Framework (Spring.io) upgrade from TRIRIGA 4.0.5 to 4.3.0. Moving forward, when an OnChange workflow is triggered by a locator field update, the workflow will now retrieve referenced data used in Modify Metadata tasks.

IBM TRIRIGA Support does all that it can to assist our clients. However, there are processes in place to help all of our clients get a consistent level of help…

A Service Request (SR) or Problem Management Report (PMR) is created to request assistance from IBM TRIRIGA Support to help with investigating a problem or to request an answer to a question regarding TRIRIGA. Due to the complexities of the environments supported and the potential scope of work involved with enterprise software, it may take some time to complete an investigation and can result in a number of outcomes, such as the following SR/PMR resolutions:

Resolved as a question answered.

Resolved as a product working as designed (even when a client may disagree with the design).

Resolved as a request outside the scope of support.

Resolved as a defect (which will result in the creation of an Authorized Program Analysis Report, or APAR).

With each of these outcomes, IBM TRIRIGA Support has completed its investigation and the SR/PMR has been resolved. What happens next?

[Admin: This post is related to the 07.14.15 post about collecting data to resolve PMRs, and the 07.07.15 post about resolving PMRs as soon as possible. The same article is also posted in the Watson IoT Support blog.]

I have created an object migration (OM) with its workflow. The execution works well on the Development environment. But after an import of the OM package with all objects needed, the execution didn’t work on the Test environment. The object migration launch works. The triIntegration workflow launch works. The execution of the request works in SQL Server. The connection in my object migration works.

Is it possible to (OM) migrate integration object records? I’ve created two integration objects in my Dev environment. But I’m not sure which BO to use to (OM) migrate my two records to my Test environment.