I am looking for some explanations for the “Dynamic Workflow” property settings in the Call Workflow task. When should I use it?
The Dynamic Workflow property and fields allows you to pull the workflow name to execute from a task > field, instead of the workflow name being hard-coded in the workflow. The field must contain the workflow name to execute.
Excerpt from the “Application Building” (3.5.3, PDF) user guide:
Dynamic Workflow: The values of this field are used to dynamically define the name of the workflow that this task will launch. For the “Task with Workflow Name” drop-down list, select the task record that contains the workflow name. For the “Workflow Name Field”, select the field on the task record that contains the workflow name. This record field must contain the workflow name that you want to launch.
[Admin: To see other related posts, use the Workflow tag or Workflow Builder tag.]
We are in the process of upgrading our TRIRIGA installation from 3.4.1/10.2.x to 3.5.2/10.5.2 and have run into an issue with Trinity, something that Global Services set up for us to import and export data to external systems. Does anyone know anything about it? Or know where to find any product documentation?
I work in IBM TRIRIGA Support as an L2 Support Engineer. I can tell you that Trinity is not a supported product and you would need to reach out to IBM Global Business Services (GBS) for assistance with this. I recommend starting out with a call to the IBM General Inquiries number to get in touch with GBS. That phone number is: 800-IBM-4YOU (800-426-4968).
Here are several lists of reports delivered with the as-shipped TRIRIGA solution:
Is anybody seeing this issue in TRIRIGA 3.5.2? The Release Notes say that:
“The inner Save action on the Access tab of the Security Manager is removed. The user can make multiple permission changes, mix them with general changes and member changes, and save all at the end with the Save or Save & Close actions.”
But this doesn’t seem to work. Why not?
[Admin: This post is related to the 03.07.16 post about best practices for managing your security groups.]
I’m trying to update a record using Data Integrator. But currently, I have no good results with this. The record is just added, not updated. I would appreciate it if you could show me an example of updating the value of an existing record for an employee’s email address below. I might not have understood the publish name, or the unique key of TRIRIGA.
- (1) triIdTX: 1000004: This is the system generated number at record creation. I assume it’s used as the unique key. (I am not sure if it is the publish name or not.)
- (2) triLastName: Aaaaaaaa: This is the value with the same value when creating a record.
- (3) triFirstName: Bbbbbbbb: This is the value with the same value when creating a record.
- (4) triEmailTX: firstname.lastname@example.org: It was not set when creating a record. And I want to set this value as an update value.
Also, let’s suppose that some values are already set to other fields of triPeople, but are not specified in Data Integrator.
You are correct that it’s adding a record because you’re not using the Publish Name. Take a look at the documentation in Application Building for the IBM TRIRIGA Application Platform 3: Data Management (3.4.x PDF p.35 | 3.5.2 PDF p.31). I confirmed the publish name in our latest release is the same as documented: Last Name + ‘, ‘ + First Name + ‘ – ‘ + ID.
[Admin: To see other related posts, use the Data Integrator tag.]
How do you run the MS SQL “SetVarcharColsToNumeric_MSSS.sql” and “SetVarcharColsToNumeric_MSSS_Publish_BO.sql” scripts after upgrading to TRIRIGA 184.108.40.206? 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 220.127.116.11. 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)?
In the TRIRIGA 10.4.1 Lease > Accounting tab > Schedule Summary section, there is the “Total Rent Present Value” field. In 10.5.2, that field is no longer there, but there is the “Current NPV of Rent” field. What is the difference between the two? Why are they different?
I can’t reply to the specific changes, but since 10.4.1 was released in 2014 and 10.5.2 was released in late 2016, there were scenario enhancements and more scenarios covered in TRIRIGA for Lease Accounting in the releases in between. The Lease Accounting wiki has information about the changes in these releases and might be helpful for questions similar to this (i.e., what is the difference between releases)…
Looks like the difference between present value (PV) and net present value (NPV) is the “net”. The latter “net” basically accounts for the initial capital/investment. As for “why” the change, I’m not sure, but it might be a more useful or accurate value for newer lease calculations/standards…
Both represent the Net Present Value (NPV) for the Operating/Finance schedule. The field from 10.4.1 and 10.5.2 is the same, but the label has changed in 10.5.2. In 10.4.1, it represented the Net Present Value at the time of lease activation and was not updated even if there were review assumptions performed. In 10.5.2, after the new accounting standard finalized, the current NPV now represents the NPV (liability as it is known) either at the time of first activation of the lease, OR after any recalculations might have impacted it due to performing the review assumptions. For example, at the start, it might be $30,000 and 1 year later, the NPV changed to $21,000, due to review assumptions that represent the “current” values at that point. By comparison, in 10.4.1, it would always show as $30,000.
[Admin: This post is related to the 02.22.16 post about the latest information on lease accounting.]