by Dalia Vazquez

Share

Clarity is built to handle Investment, Project and Portfolio information across organizations. Constantly churning and processing:

  • High volume of data across investments and resources

  • Providing a web experience which can easily handle thousands of users

  • Deeply integrated job and process engines which ensure financial processing, data aggregation, reporting, among other core functions.

When it’s implemented well, it becomes the system teams rely on to see clearly and plan confidently.

Like any system that’s actively used, Clarity produces a lot of information along the way. That’s not a flaw. It’s a sign that the platform is doing its job.

Housekeeping is how high-performing teams keep their systems healthy over time: purging volatile data within organizational retention rules, and staying disciplined about processes, job schedules, and configuration so things stay clean, fast, and dependable.

At Rego, we don’t see housekeeping as “cleanup.” It’s good stewardship of a system that’s already doing important work, supported by clear housekeeping phases that keep teams proactive. The goal isn’t reactive housekeeping after something breaks. It’s steady, intentional care that prevents fires in the first place.

Housekeeping Is How Systems Age Well

One of the biggest misconceptions about housekeeping is that it’s something you do because something is wrong. The teams that handle housekeeping best are rarely reacting to issues at all. They are intentional.

Clarity continuously records activity such as sessions, process executions, job history, reports, and notifications. Some of that data is essential for audits, troubleshooting, and historical reference.

This is a theme we emphasize in Rego University, especially in the Housekeeping and Maintenance with Clarity Out-of-the-Box Jobs course. Systems don’t degrade because they’re heavily used. They degrade when early assumptions are never revisited.

Retention decisions that made sense early on may not scale forever. Housekeeping gives teams a way to pause, reassess those decisions, and refine them without slowing the work Clarity supports every day.

The Four Areas of Housekeeping in Clarity

Before getting into individual jobs, it helps to zoom out. Housekeeping in Clarity isn’t one thing. Strong environments stay healthy because teams take care of four connected areas over time:

  • Processes
    Workflows evolve as organizations mature. Housekeeping means revisiting old processes, retiring what no longer reflects reality, and keeping automation aligned to how teams work today.
  • Jobs
    Jobs keep the platform running in the background. Housekeeping means scheduling the right jobs on the right cadence, reviewing failures, and adjusting configurations as data volumes and usage patterns change.

  • Volatile Data
    Clarity generates operational data like sessions, logs, notifications, and outputs. Housekeeping means purging this data within retention and compliance policies so only what’s useful sticks around.

  • Configurations & Customizations
    Fields, reports, views, and integrations accumulate over time. Housekeeping means pruning what’s no longer used and keeping customizations aligned to current governance and ways of working.

    Together, these areas reinforce each other. Jobs help manage volatile data, but true system health comes from caring for processes and configuration too and not just running cleanup jobs.

How Out-of-the-Box Jobs Support Teams

Clarity doesn’t leave teams to manage system data on their own. It provides out-of-the-box jobs designed to support responsible data stewardship. These jobs offer a repeatable way to manage system data without custom scripts or risky database intervention.

Before looking at individual jobs, it helps to understand the intent behind them. Different types of system data exist for different reasons and for different lengths of time. Housekeeping simply aligns each type of data to how long it remains useful.

Data Type Why It Exists
User sessions Tracks active usage, expires naturally
Logs and audit trails Supports troubleshooting and validation
Process instances Records execution history
Job and report outputs Confirms work completed

User sessions matter while someone is actively working in the system. Once a session expires, it fulfills its purpose. Clearing expired session data keeps the environment lighter and more responsive without affecting how users work.

Log analysis data and audit trails follow a similar pattern. They’re essential in the moment, especially when validating changes or troubleshooting issues. Over time, their relevance fades. Retention should be driven by business needs and compliance requirements, not default behavior.

Process instances often represent the greatest opportunity for intentional cleanup. Processes evolve as organizations mature. Logic changes. Automation becomes more sophisticated. Completed instances tied to outdated logic rarely provide insight once their work is done.

Using out-of-the-box jobs allows teams to work with the platform rather than around it. That consistency reduces risk, lowers administrative overhead, and makes housekeeping part of normal operations instead of a special project.

What These Jobs Do in Practice

Each housekeeping job in Clarity exists to manage a specific type of system data and enforce intentional retention.

  • Clean User Session Job
    Removes expired session-based user data stored in the application.
    Criteria: session has expired

  • Delete Log Analysis Data Job
    Removes Clarity log analysis data so older logs don’t accumulate indefinitely.
    Criteria: log date

  • Purge Audit Trail Job
    Enforces audit trail retention settings defined at the object level in Studio.
    Criteria: retention rules defined on the object’s Audit Trail tab

  • Remove Job Logs and Report Library Entries Job
    Clears older job log entries and report library records to reduce administrative clutter.
    Criteria: job or report age in days

    Some jobs offer even more flexibility. The following jobs can be configured multiple times with different conditions, allowing teams to retain certain records longer when needed for audits, compliance, or reporting purposes.

  • Delete Process Instance Job
    Removes completed or obsolete process instances. Rego expert guides often recommend running this job before each application upgrade.
    Criteria: process, date range, status

  • Purge Notifications Job
    Removes notifications that are no longer relevant once they’ve served their purpose.
    Criteria: notification type, created date, assignee

  • Purge Report Output Job
    Removes stored report output to keep reporting-heavy environments lean.
    Criteria: report output format, report name, run dates, run by

Together, these jobs give teams precise control over system data without disrupting active work.

How Clarity Stays Current and Clean

The strongest Clarity environments aren’t necessarily the most customized. They’re the ones where the system reflects how the organization actually operates today. That includes current governance models, active workflows, meaningful reports, and relevant historical context.

Housekeeping supports this alignment by allowing older artifacts to fade quietly into the background. When that happens, users trust what they see more readily. Reports feel intentional. Navigation makes sense. Decisions move faster.

Administrators benefit too. When job logs, report outputs, and notifications are managed intentionally, they spend less time hunting for what matters and more time supporting users effectively.

Scheduling Makes Housekeeping Seamless

Good housekeeping is invisible.

Strong teams don’t rely on manual execution or sticky-note reminders. They schedule preventive housekeeping jobs on a cadence that fits their environment, then let Clarity do its thing in the background.

Over time, housekeeping becomes predictable, reliable, and easy to forget. That invisibility is a sign of maturity. Users aren’t disrupted. Admins aren’t scrambling. The system just runs.

But real housekeeping isn’t only about scheduled jobs. A healthy environment takes a holistic approach:

  • Preventive housekeeping runs on a schedule to keep things clean and performant.

  • Adaptive housekeeping happens when Clarity changes with new configurations, new processes, new ways of working.

  • Corrective housekeeping is what you do when something breaks or starts misbehaving.

The goal is to live mostly in the first two. Reactive cleanup after a fire is sometimes unavoidable, but it’s the last place mature teams want to spend their time.

Housekeeping works best when it’s part of the platform’s rhythm, not a special event.

A Final Thought from Rego

When the system reflects what matters today, Clarity does what it does best. It helps organizations plan, prioritize, and move forward with confidence.

For teams looking to go deeper, the Housekeeping and Maintenance with Clarity Out-of-the-Box Jobs course in Rego University offers practical guidance grounded in real environments and decisions. And if you want to talk through what stewardship looks like in your Clarity instance, that’s a conversation we’re always happy to have!

STAY IN THE LOOP

Get Notified of Updates.

Stay ahead of the curve by subscribing to our newsletter. Get the latest insights, strategies, and tools delivered straight to your inbox, and empower your business to achieve more.