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 (11921)
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
Fabio L Pinto 270003DRX7 Visits (11295)
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