Zum Hauptinhalt springen

Flair Doctor

Flair Doctor is a diagnostic and repair tool that helps troubleshoot and fix data inconsistencies in your flair org. It consists of specialized controller classes that can identify and automatically repair common data issues, saving you time and ensuring data integrity.

What is Flair Doctor?​

Flair Doctor provides automated tools to diagnose and repair data problems across various areas of flair. Instead of manually fixing issues one by one, you can use Flair Doctor to scan your org for problems and repair them systematically.

Permission Required

To access Flair Doctor, users must have the Flair Doctor permission set assigned. Contact your Salesforce administrator to request access.

Accessing Flair Doctor​

To access Flair Doctor:

  1. Navigate to the flair HR app in Salesforce
  2. Go to the HR Admin page (or the location where Flair Doctor is available)
  3. Look for the Flair Doctor section or tab
hinweis

The exact navigation path may vary. If you cannot locate Flair Doctor, ensure you have the Flair Doctor permission set assigned and contact your administrator.

Available Doctors​

Flair Doctor includes several specialized tools, each designed to fix specific types of data issues:

Employment Doctor​

What it fixes: Manager field inconsistencies based on employment terms. When an employee's manager field doesn't match what's defined in their employment term, this doctor can automatically repair it.

When to use:

  • Manager field is not set correctly according to employment terms
  • Employee's manager doesn't match their employment term configuration
  • Work structure appears broken due to incorrect manager assignments

How to use:

  1. Navigate to Flair Doctor and select Employment Doctor
  2. Review the list of employees with manager field issues (if displayed)
  3. Click the repair action button
  4. The doctor will automatically update manager fields based on employment terms
  5. Refresh the employee record page to verify the manager field has been corrected

How it works: The Employment Doctor calls the same service used by Employee Triggers, ensuring consistency with the business logic. This means the repairs follow the same rules that would apply during normal employee record updates.

Example scenario: If an employee named Adamaris has an employment term that specifies their manager should be Cherikin, but the manager field is empty or incorrect, the Employment Doctor will update it to match the employment term.

Absence Allowances Doctor​

What it fixes: Duplicate absence allowances with the same date and amount. This doctor helps clean up duplicate allowances while preserving data integrity.

When to use:

  • Multiple absence allowances exist with identical dates and amounts
  • Need to clean up duplicate allowances systematically
  • Absence balance calculations are affected by duplicate entries

Important Logic:

  • Keeps allowances connected to time balance withdrawals (these will regenerate if deleted)
  • Removes duplicate allowances that are NOT connected to time balance withdrawals
  • Preserves allowances with null dates even if they appear duplicate (if not connected to time balance)

How to use:

Scanning for Duplicates​

  1. Navigate to Flair Doctor and select Absence Allowances Doctor
  2. Click the Scan button
    • The doctor will scan through every employee's absence categories
    • It identifies and counts duplicate allowances based on date and amount
    • The scan process may take a moment depending on the size of your org
  3. Review the scan results showing how many duplicates were found
    • The results will indicate the number of duplicate allowances that can be safely removed

Removing Duplicates​

  1. After reviewing the scan results, click the Remove button
    • The doctor processes and removes duplicates according to the safety logic
    • It will only remove duplicates that are not connected to time balance withdrawals
  2. Wait for the removal process to complete
    • You'll see a confirmation message indicating how many duplicates were removed
  3. Refresh your absence allowances view to verify duplicates have been removed
    • The allowances connected to time balance withdrawals should remain
    • Duplicate allowances without connections should be removed

Verification:

  • Check employee absence categories to confirm duplicates are gone
  • Verify that allowances connected to time balance withdrawals are preserved
  • Confirm the count matches expected results (e.g., if you had 7 allowances and 2 duplicates were removed, you should now have 5)

Example scenario:

  • Employee Shiri has two allowances with the same date and amount
  • One is connected to a time balance withdrawal, one is not
  • The doctor will remove only the one without the time balance connection
  • Employee Adimaris has duplicate allowances (3 and 3, 10 and 10)
  • The doctor will remove the duplicates that aren't connected to time balance withdrawals

AutoBreaks Deduction Doctor​

What it fixes: Validates automatic break deductions to ensure they're configured correctly.

When to use:

  • Break deductions are not being applied correctly
  • Need to verify break deduction configurations
  • Time tracking shows incorrect break calculations

How to use:

  1. Navigate to Flair Doctor and select AutoBreaks Deduction Doctor
  2. Run the validation scan
  3. Review any issues found
  4. Apply fixes if available
hinweis

Detailed usage instructions for AutoBreaks Deduction Doctor will be added as more information becomes available.

Doctor Migrations​

What it fixes: Handles data migrations and ensures migrated data is consistent.

When to use:

  • After migrating data from another system
  • When data migration issues are suspected
  • Need to verify migrated data integrity

How to use:

  1. Navigate to Flair Doctor and select Doctor Migrations
  2. Run the migration validation
  3. Review migration status and any issues
  4. Apply fixes if needed
hinweis

Detailed usage instructions for Doctor Migrations will be added as more information becomes available.

Doctor Positions Structure​

What it fixes: Repairs position structure data and organizational hierarchy issues.

When to use:

  • Position structure appears incorrect
  • Organizational hierarchy has inconsistencies
  • Employees are not appearing in the correct positions

How to use:

  1. Navigate to Flair Doctor and select Doctor Positions Structure
  2. Run the structure validation
  3. Review any structural issues found
  4. Apply repairs if available
hinweis

Detailed usage instructions for Doctor Positions Structure will be added as more information becomes available.

Doctor Salary Access​

What it fixes: Checks salary object access and permissions.

When to use:

  • Salary data access issues are suspected
  • Need to verify salary object permissions
  • Users cannot access salary information they should have access to

How to use:

  1. Navigate to Flair Doctor and select Doctor Salary Access
  2. Run the access check
  3. Review access issues found
  4. Apply fixes if available
hinweis

Detailed usage instructions for Doctor Salary Access will be added as more information becomes available.

Doctor Workload​

What it fixes: Fixes workload-related issues and calculations.

When to use:

  • Workload calculations appear incorrect
  • Employee workload assignments are inconsistent
  • Need to repair workload data

How to use:

  1. Navigate to Flair Doctor and select Doctor Workload
  2. Run the workload validation
  3. Review any workload issues found
  4. Apply fixes if available
hinweis

Detailed usage instructions for Doctor Workload will be added as more information becomes available.

Best Practices​

Before Running a Doctor​

  • Review the issue first - Understand what problem you're trying to solve before running a doctor
  • Use scan functions - Always use scan functions (when available) to review what will be changed before executing repairs
  • Backup considerations - Consider backing up data before running doctors on production orgs, especially for large-scale repairs
  • Test in sandbox - If possible, test doctors in a sandbox environment first to understand their behavior

After Running a Doctor​

  • Verify results - After running a doctor, refresh relevant records to confirm the fixes were applied correctly
  • Check related records - Verify that related records (like employee records, absence categories, etc.) reflect the changes
  • Monitor for issues - Keep an eye on the affected areas to ensure the repairs resolved the issue

When to Use Flair Doctor vs Manual Fixes​

  • Use Flair Doctor for: Systematic issues affecting multiple records, data inconsistencies that follow patterns, issues that would be time-consuming to fix manually
  • Use manual fixes for: Isolated problems affecting single records, issues requiring business judgment, one-off data corrections

Troubleshooting​

Doctor Not Available​

If you cannot see Flair Doctor:

  • Verify you have the Flair Doctor permission set assigned
  • Check with your Salesforce administrator
  • Ensure you're accessing the correct location in the flair HR app

Doctor Doesn't Fix the Issue​

If a doctor doesn't resolve your issue:

  • Review the doctor's logic to ensure it applies to your specific problem
  • Check if there are additional underlying issues
  • Consider manual fixes for edge cases
  • Contact flair support if the issue persists

Unexpected Results​

If a doctor produces unexpected results:

  • Review what the doctor changed
  • Check if the changes align with the doctor's documented behavior
  • Verify related records are still correct
  • Consider reverting changes if necessary (if possible)

Getting Help​

If you need assistance with Flair Doctor:

  • Review this documentation for usage instructions
  • Contact your Salesforce administrator for permission issues
  • Reach out to flair support for technical assistance
  • Check the flair changelog for updates to Flair Doctor features