IV97838: Working hours in task are not always calculated correctly

If a work task has a calendar and the “Planned End” or “Actual End” date-time field values are updated, the “Working Hours” are not always calculated correctly. The working hours do not seem to factor in the calendar hours.

The working hours were not being calculated correctly. The issue was that the values for the calendar fields (Year, Month, Day, etc.) were not being set correctly. The fix was to set the calendar fields exactly as we do for the other calculation methods. Moving forward, we resolved a work task record and Gantt chart issue, where the Actual Working Hours and Actual Working Days were not being correctly calculated when an Actual End date value was entered.

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

Advertisements

Is there a way to export query results as attachment to email?

I have two questions:

• (1) Is there any way to export the results of a query and send them as an attachment to a particular email ID?
• (2) Is there any way to schedule to get the report results and automatically send them in Excel to an email ID?

[Admin: This post is related to the 03.15.16 post, 05.04.15 post, and 01.24.15 post about sending BIRT reports via email.]

How do you set the PM schedule for every 2, 3, or 4 years?

I was wondering if there is a way to set the PM work schedule for every 2 years, maybe even 3 or 4 years?

When entering the schedule for a PM task, you would think that you could select the Recurrence Pattern Type of “Yearly”, and then enter every 2 years, 3 years, and so on, but no, you can’t! One rather cumbersome solution is to enter a yearly schedule (i.e. every year) and then set a number of exception dates for the years when you do not want the task to happen. That is a bit awkward.

The better, but less obvious, solution is to choose the Recurrence Pattern Type of “Monthly”. This offers two options to set the schedule to either “Day [x] of every [x] months” or “The [first] [Monday] of every [x] months”. Choose whichever one suits your needs, and set the “every [x] months” value to every 24 months, 36 months, 48 months, etc. The main downside of this is that the word “Monthly” appears in the name of the tasks produced, which is misleading when the schedule is effectively based on a number of years.

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

IV97614: Cannot revise project in Schedule tab with Gantt section

If you attempt to revise a project from the Schedule tab, where the Gantt chart is visible, your session is expired and you receive an invalid session error. The issue was observed in Internet Explorer and Chrome, but not in Firefox.

An analysis from a Fiddler trace shows that when revising the project in Chrome, this POST to GanttDataUpload.jsp seems to kill the session. In Firefox, for whatever reason, this POST doesn’t occur, and the state transition is successful. To confirm that this is the scenario you are experiencing, use the following technote to run a Fiddler trace and check for the same GanttDataUpload.jsp call: IBM TRIRIGA using Fiddler for tracing web browser traffic.

As a temporary fix, use Firefox. When the record is in a read-only state, no Save action should be called on the Gantt. Moving forward, we resolved the session-kill issue when the user performs a Revise action on a project in the Schedule tab.

[Admin: This post is related to the 08.18.15 post about using Fiddler to trace TRIRIGA web traffic. To see other related posts, use the Gantt tag or Fiddler tag.]

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.]

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 Date, Fiscal 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.]

IV97411: Adjusting task status on Gantt not working uniformly

Adjusting the task status on a Gantt chart with Ctrl/Cmd+click is not working uniformly across client operating systems.

We needed to disable the Ctrl+left/right-click and Shift+left/right-click, which are not working consistently across browsers and Mac, and reintroduce the right-click > “Set Percentage Complete” to the right-click menu. We also needed to update the “Percent Complete” message to be shorter, and update the message minimum width to be wider.

Moving forward, we removed the ability to set the percentage complete by using Ctrl+click, which does not work correctly on all browsers on all operating systems, replacing it with the ability to “Set Percentage Complete” by using the right-click context menu when right-clicking a Gantt task.

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