Have you found yourself sighing when a Clarity PPM (CA PPM) page took a little too long to load? Maybe you even know the problem. It's loading every available record . . . before you've even had a chance to pick search terms and FILTER.
Well, guess what? You can make that page so much faster. We'll show you how today. And if you want something more comprehensive, here's the best place for Clarity PPM performance help. (Hint: it comes with a free PPM Health Assessment.)
We also have a few spots left for our Clarity PPM Conference: regoUniversity 2017! It's in San Antonio at the fanciest resort I've ever booked a room. And if you've already invested in Clarity, there's no better place to be—no matter your skill level or focus. Here's a link to see why people return to regoU year-after-year for more Clarity training.
Now, on to the Q&A!
Learn with Rego | Clarity PPM Q&A
1. Does it matter if I use timesheets or the WIP to adjust time?
2. Why won't tab delimited work?
3. We have a Clarity page loading slow! It has a large portlet with a filter. Is there a workaround, so it doesn't populate records until we hit filter?
Please feel free to comment on any alternative answers you've found. At Rego, we always love your input.
Does it matter if I use timesheets or the WIP to adjust time?
When you adjust time, AKA "historical hours," the adjustment should be made in the same way the time was created.
DON'T use a WIP Adjustment to change hours created with a timesheet. Why? Timesheet Adjustments are stored in tables, and if an adjustment to a timesheet is done through a WIP adjustment, all of the tables won't be updated the same . . . which will cause data integrity issues, depending on what portlet/report is being used.
If the hours were originally created through a manual or imported transaction, then the adjustment can be made through a WIP Adjustment.
It’s best to adjust hours the same way they were created.
How do you get tab delimited to work with the OOB tag?
Sometimes people have problems with tab delimited when they copy/paste into Explorer. You'll find that delimiter="	" may be replaced with delimiter=" ", and that messes with the format.
1. delimiter="	"
2. XOG-in the gel script for the process.
We have a Clarity page loading slow! It has a large portlet with a filter. Is there a workaround, so it doesn't auto-populate records until we hit filter?
The easiest workaround is to force one of the defaults to an invalid value, to not show data. We changed the slice Period Type to "None" which results in the query not returning data. It forces the user to update the filter, if they want to use it, and greatly speeds up the overall page load times.