Can you retire a job plan to get rid of unneeded draft work tasks?


When the Operations team was changing a job plan, the wrong date was entered, and it created over 1,800 work tasks. They have since tried to retire them and they changed to Draft status. To get rid of these, can the job plan itself be retired?

[Admin: To see other related posts, use the Job Plan tag.]

Continue reading

Why doesn’t dependent task go further than planned end date?


In TRIRIGA, why doesn’t my dependent task go any further than the planned end date, if I move the parent task beyond the planned end date?

The task that is being moved (along with its dependent task) eventually violates the planned end constraint. The task that is in violation of the constraint is in red, and the dependent task will not be moved past the planned end. If there is no planned end, then there is no constraint and you can freely move both tasks.

[Admin: To see other related posts, use the Gantt tag or Scheduling tag.]

Continue reading

How do you run a simple Survey Fact ETL job item?


I would like to see an example of running an ETL job item, because simply running the process fails. When users see the activated record, they assume they can click “Run Process” and get results. But you need to enter a set of restraining data to get results.

Every ETL job item is different. You must fill in the record information to get the results necessary for the transformation or processing. More information can be found at the following link: IBM TRIRIGA – Running ETL transforms. This blog entry will describe a sample run of a Survey Fact ETL job item.

  1. First, from the menu, click on Tools > Job Scheduling > ETL Job Item.
  2. Then search for “Survey Fact” and open the record. It’s recommended that you click on More > Copy to create a copy that you can modify, test, and play with.
  3. After that, change the name to an friendly name and enter at least these mandatory fields: Date, Start Date, Fiscal Period, and End Date.
  4. For the Date field, take notice of the “Quarter” and “Month” to enter the other subsequent Start DateFiscal Period, and End Date.
  5. See the example for “Q2/2017 – June”. After all of the fields are entered, click Save. Then you can click Run Process.
  6. The record window will close. Then you can see “Processing” for the status of the record.
  7. After that, you can open it again and it should show “Completed” as the status. You can also click on the Workflow Instance tab to see the completed workflows.

[Admin: To see other related posts, use the ETL tag.]

Continue reading

IV97369: Typed dates do not follow user date-time preference in Gantt


Manually typed dates do not take into account the user’s date-time preference in the Gantt scheduler.

We needed to specify the EditFormat element, in addition to format, when applying the left-column metadata to the date fields. Moving forward, manually editing dates will now take into account the user’s date-time preference in Gantt.

[Admin: To see other related posts, use the Gantt tag.]

Continue reading

Is there a way to track timestamps for barcodes read by mobile?


With TRIRIGA Anywhere, I was wandering is there any way to track the date/time when the asset barcode was read with a mobile device?

[Admin: This post is related to the 03.11.16 post about Anywhere ignoring timeout settings. To see other related posts, use the Anywhere tag.]

Continue reading

IV97201: Durations for room setup and breakdown aren’t correct


Regarding the setup and breakdown tasks for rooms, the Start and End times of these tasks are only influenced by relevant service assignment matrix (SAM) service level agreements (SLAs), and not by the Room Setup and Breakdown times of the space. If there are no SAM records, the duration of the task is taken as 0 (i.e. the Start and End times are the same).

The Start and End date-times on the reserve work task records that were created for the Setup and Breakdown times on the space were populating the values from SAM (not the reservation). The issue has been resolved to populate the date values from the space by adding a new list value “Use Reservation” to the “Task Assignment Dates Rule” list field on the service plan record, which is used for service plan records that are created for reserve functionality. This will allow the dates to be used from the reservation and not SAM.

Also, the list values “Available Mid-Reservation” and “Available for Entire Reservation” in the “Reserve Service Type” list field on the reserve work task template have been removed, since our current structure does not support these two values for the reservation use case.

Note for upgrade customers: These list values have been removed from the as-shipped application. These values will not be removed through an object migration (OM) package. So, you have to manually remove these values from your environment if they are not being used anywhere.

[Admin: This post is related to the 11.16.16 post about searching for rooms with setup and breakdown times. To see other related posts, use the Reservation tag.]

Continue reading

IV97206: Schedule task date issues when importing MS Project files


Logged into TRIRIGA 3.5.2/10.5.2. Set the project. Navigated to the Schedule tab. Imported MS Project (MPP) file. First thing noted was that the Start and End times were set to 9AM. A time zone was set, but no calendar. After fixing dependencies and saving that to the Gantt, we noted that the schedule task and work task times were an hour off, that is, the Gantt section times and the query section times (specifically, the End times).

After saving to the Gantt, but before saving the project, the dates and duration in the Gantt didn’t match. Also after saving, we noted that the Start and End times of the schedule task were updated from 9AM to some different, seemingly arbitrary, values. After the final save, the Duration values changed from Weeks/Days/Hours to Months/Weeks/Days. We also played around with changing the Planned Start Date of the project, and noted that any change that occurs prior to the original date, or any future date, will not recalculate at all.

There is a bug in the MPXJ library where in some instances, the working days needs to be set to 0. Moving forward, we resolved an issue where sometimes, Microsoft Project files (MPP) tasks are coming in with dependencies with an invalid lag time of 95.4733 days when the lag time should be 0 days.

[Admin: To see other related posts, use the Gantt tag.]

Continue reading