AcdntlPoet 2700019V2G Visits (8774)
Setting up TRIRIGA Notifications with Office 365 - If you are using Office 365 as part of your Reserve integration, then you probably want to have notifications set up as well. Kenny To has posted a quick and easy solution in the Real Estate and Facilities Management blog here.
Learning the IBM TRIRIGA 10.3 Porfolio is a must - In a continuation to his previous blog post (Being a New TRIRIGA Engineer) Mark Raymund Dunham writes about the importance of the IBM TRIRIGA 10.3 Porfolio Self-Paced Virtual Class here.
AcdntlPoet 2700019V2G Visits (10775)
Welcome to the Cognitive Era - A new era of technology. A new era of business. A new era of thinking. A Cognitive Business is a business that thinks. A new era of technology is giving rise to a new era of business. Digital is not the destination but the foundation for a new era of business; we call it cognitive business, and IBM Watson is the platform. Today Watson is helping doctors re-imagine medicine, and leaders reshape industries as diverse as retail, banking and travel. And Watson is taught by industry experts, so their know-how can reach more practitioners.
AcdntlPoet 2700019V2G Visits (11447)
Migrating data from IBM Rational DOORS to IBM Rational DOORS Next Generation- With the release of IBM Rational DOORS 18.104.22.168 and IBM Rational DOORS Next Generation V6.0.1 the migration has been optimized, now automatically creating a global type system and artifact types in IBM Rational DOORS Next Generation, considering the commonalities of the type system defined in modules within DOORS, as well as links relationships. In addition, you can now incrementally migrate a project, and the two applications will automatically maintain and update link relationships with every incremental migration.
Migration is not interchange of data where data can go from one tool to another and possibly back again. Migration is a one-way move from Rational DOORS to Rational DOORS Next generation, with traceability back to the source.
Using a migration package, migration can include one or more modules and can be incremental, migrating a little at a time, and only what you need. The current version of modules is migrated along with internal external and OSLC links, OLE objects, pictures and so forth.
The history of the migrated data is not migrated however, the migration creates links in Rational DOORS Next Generation that link back to the corresponding records in Rational DOORS.
AcdntlPoet 2700019V2G Visits (11024)
Migrate data from Rational DOORS to Rational DOORS Next Generation- Kim Letkeman, Senior Technical Staff Member, IBM and Martin Henderson, Development Manager, IBM, lead you through planning and implementing a DOORS migration project.
Plan and execute a migration project from IBM® Rational® DOORS® to IBM Rational DOORS Next Generation. This article provides a list of migration terms and definitions (as opposed to interchange) and describes the phases and tasks involved when moving active data into a Collaborative Lifecycle Management environment.
AcdntlPoet 2700019V2G Visits (9995)
Maximo 7.5 - Configuring AUTOKEY: How to set up AUTOKEY to auto number a field by Leandro Garcia
Thousands Workflow Events in Tririga queued up by Data Integrator or Web Services will prevent regular user & system Workflows from executing
Fabio L Pinto 270003DRX7 Visits (8077)
If you have developed an interface submitting thousands of Workflow Events to be executed by your process server, they will likely create a huge queue to be processed leading following required and essential user & system Workflows to get queued up as well, waiting for those Events to be processed. At this point your system will get stuck, with sessions waiting for required Workflows to run.
Ideally you should be submitting such Workflow events in "chunks" or small batches so that system is not impacted with lots of Workflows queued up waiting for processing to finish.
If it is too late and you have submitted those thousands of records already, this may take a consider amount of time to process; hours or even days depending on the quantity, complexity and system resources available.
The current count of Workflow Events can be confirmed by checking "IBM TRIRIGA Admin Console" -> "WorkFlow Events" managed object page. You may have an idea of how much time all those queued up Workflow events and the recently added ones (user & system) will take to process by checking that regularly and taking notes of how many records have been moved out from the queue (number of Events queued up, trend).
For managing this situation properly, review the following actions:
A01) Make sure you do have
A02) Make sure you only have one Workflow agent running with open filter (no filter, no list of users). Having two or more Workflow agents running with no filter criteria will slow down process likely since they might be competing for the same resources and records. See more information on our IBM TRIRIGA Wiki page "Whe
If adjusting your system to those recommendations does not help, you may try the following alternative way for handling this situation.
***NOTE! The following procedure is NOT a supported process. This document is intended to assist clients find a workable solution when they have not followed best practices and the system function properly. The steps below are presented as an option but may present a risk if not executed correctly;
AL01) First, you need to get familiar with how Workflow Events work, so please review our IBM TRIRIGA Wiki page "Wor
AL02) Make sure you do have a good backup of your database in place. It is strongly recommend you try the following steps on a lower environment first (testing, sand-box, development).
AL03) You need to determine the criteria for selecting the Workflow records you are bringing from your Interface, so that you can separate them from the user & system required ones. Once you have this information you are able to proceed;
AL04) Review, adapt, and follow the instructions below:
1) Stop the Workflow agent (IBM TRIRIGA Admin Console -> Agent Manager);
2) Create a table wf_event_backup as the current wf_event table. Truncate the wf_event after that (Make sure you do have a good database backup in place);
drop table wf_event_backup;
4) Insert into wf_event table selecting the workflows for the users that are not involved in your interface process, delete those out of the wf_event_backup table once inserted and processed;
Example given (note, you need to user your criteria here, you need to adapt and replace the where clauses below);
insert into wf_event select * from wf_event_backup where user_id <> [user-id];
... or ...
insert into wf_event select * from wf_event_backup where event_id not like '%Associate%';
5) Once those Workflows above have processed, insert 500 records at a time into the wf_event table, from the wf_event_backup table based on row_number (where row_number < 500). See that now you will be working with the Workflow Events coming from your interface Delete from wf_event_backup where row_number < 500.
Example given (for Oracle):
insert into wf_event select top(500) * from wf_event_backup where event_id like '%Associate%' ;
6) Repeat step 5 above until all of those records have been processed (the ones coming from Interface).
What is the Tririga WF started for Schedule Event generated by a Payment Reconciliation from a Lease with Audit Clause?
Fabio L Pinto 270003DRX7 Visits (12211)
The Tririga workflow fired is "tri
This is how it works:
a) When a lease is activated, This workflow "triLeaseClause - Synchronous - Create Audit Service Included from Selected" is fired on Lease Clause to create Payment Audit Setup record.
b) Then the "tri
on scheduled start dates.
If you see no WorkFlow being started for the Schedule Events created for the Payment Reconciliation on Leases with Audit Clauses and you have Microsoft SQL Server in place, check if you have the following fix included on your IBM TRIRIGA Platform version:
APAR #: IV76293
If you are still seeing issues with this process and you can be reproduced on a lower environment (testing, sand-box, QA), it is good temporary set Workflow Instance Recording on this lower environment for tracing the Workflows & actions fired for the lease record, and check the flow and warning/error messages issued during the process. But see that using Workflow Instance Recording can cause slow downs and performance issues all over system, so it needs to be used only for lower environments (it should never be used for Production environments!) for temporary tracing and debugging workflows, meaning this needs to be changed from "Always" to "Errors Only" as soon as you are done with your analysis.
For more information on using Workflow Instance Recording, kindly review our
AcdntlPoet 2700019V2G Visits (10545)
How to index DOORS 9.6 artifacts in Lifecycle Query Engine - John Carolan demonstrates the steps required to enable DOORS 9.6 as a Tracked Resource Set (TRS) provider and how to add that feed to Lifecycle Query Engine (LQE) as a new Data Source.
Fabio L Pinto 270003DRX7 Visits (11600)
a) triPeople - triRetire - Remove TRIRIGA User and Read Only Dependant Records
b) triPeople - Synchronous - Remove TRIRIGA User My Profile
This move the record to Retired state, meaning they are still retained in the system. The only transitioning able to remove them from the database is setting them to NULL.
Each People BO record occupies 50 KB in average, so if you are performing massive deletion, for instance, deleting 100,000 records, this means about 5 GB being processed and worked by triRetire process at that time.
Using triRetire is the only supported process for archiving triPeople BO records.
If there is need to perform a massive retire process in system, Data Integrator may not be a good choice. Using WebServices will be a better option, but this could be enhanced to look at the number of workflows in the queue by looking at the "monitor.jsp" - Monitor a single value.
The web service code would parse and check for the numeric value returned from a URL like http
If the value is over a number (start with 9000 for example) then it would pause the integration and wait for a while until the queue is halved (4500 for example).
See that there isn't a direct way to call a workflows using WebServices. You would cause it to be executed for a given record by performing the action(transition) on the record that the workflow it tied to. For instance, if you have a workflow tied to an 'Activate' action, then using the WebService to activate the record will cause the required workflows to execute.
More information about IBM TRIRIGA WebServices can be found on our