CAD file check-in fails due to locked lifecycle status in lifecycle management

PLM Oracle Agile PLM
, , , , , , , ,
1

Our design team is unable to check in updated CAD files because the part’s lifecycle status is locked. When users try to check in revised CAD models through JavaClient, they get an error message saying “Check-in not allowed - object lifecycle status prevents modification”. The parts are currently in Released status, and we need to incorporate design changes that came from a customer ECO.

The lifecycle configuration appears to prevent any file modifications once a part reaches Released status, which makes sense for production parts. However, we have an approved ECO that authorizes these specific design changes. The ECO is fully approved and in implementation phase, but the lifecycle status check happens before the ECO association is validated, so the check-in fails immediately.

We’ve tried having users with admin privileges attempt the check-in, but even they hit the same lifecycle lock. The JavaClient doesn’t seem to have an option to override lifecycle restrictions for authorized changes. Is there a proper workflow to check in CAD files against Released parts when you have an approved ECO? Or do we need to modify our lifecycle configuration to allow check-ins under certain conditions? We’re on Agile 9.3.5 using standard JavaClient.

2

Your lifecycle configuration needs a “Pending Change” or “In Rework” status that allows file check-ins while maintaining control. Add this status between Released and the next revision, then configure your ECO workflow to automatically move parts to Pending Change when an ECO enters Implementation phase. This gives designers a window to check in updated CAD files while still maintaining lifecycle control. Once all changes are checked in, the ECO completion moves the part back to Released with the new revision.

3

Check the part’s properties in JavaClient - there’s usually an “Allow Check-in” flag that can be enabled temporarily. This requires specific admin permissions though. Navigate to the part, right-click, select Properties, go to the Lifecycle tab, and look for override options. If you don’t see these options, your user role might not have the necessary privileges.

4

I’ve seen this scenario many times. The problem is that JavaClient’s check-in operation evaluates lifecycle status before it checks for associated ECOs. You need to modify the check-in validation order. There’s a configuration parameter in the Agile server settings that controls this - something like checkin.validation.order - that you can set to check ECO authorization before lifecycle status. This allows check-ins when there’s an approved ECO even if the part is Released.

5

I’ll provide a comprehensive solution that addresses lifecycle status configuration, check-in permissions, and proper JavaClient admin procedures for ECO-driven design changes.

Understanding Lifecycle Status and Check-in Control:

Your lifecycle configuration is correctly preventing modifications to Released parts - this is fundamental to PLM data integrity. However, you need to implement a controlled process that allows authorized changes through ECOs while maintaining this protection. Here’s the complete solution:

Step 1: Lifecycle Status Configuration

Modify your part lifecycle to include a transitional status for ECO-driven changes:

Current lifecycle: Preliminary → Released → Obsolete

Recommended lifecycle: Preliminary → Released → Pending Change → Released (new revision) → Obsolete

Configure the Pending Change status:

  1. In JavaClient Admin, navigate to Admin > Settings > Lifecycles
  2. Open your part lifecycle definition
  3. Add new status: “Pending Change”
  4. Position it after Released in the lifecycle sequence
  5. Configure Pending Change properties:
    • Allow Check-in: YES
    • Allow Checkout: YES
    • Allow Modifications: LIMITED (only CAD files and ECO-related fields)
    • Require ECO Association: YES
    • Auto-return to Released: After ECO completion

Step 2: ECO-Triggered Lifecycle Transitions

Configure your ECO workflow to automatically manage part lifecycle transitions:

  1. When ECO enters Implementation phase:

    • Automatically move affected parts from Released to Pending Change
    • This transition should be triggered by ECO workflow script
    • Only parts included in the ECO’s affected items list should transition
    • Send notification to designers that check-in is now allowed

  2. When ECO is completed:

    • Automatically move parts back to Released status
    • Increment part revision
    • Lock CAD files at new revision
    • Generate change history record

  3. If ECO is cancelled:

    • Revert parts to Released at original revision
    • Discard any checked-in but not released CAD changes
    • Log the cancelled change attempt

Step 3: Check-in Permissions Configuration

Set up conditional permissions that enable check-ins based on ECO context:

In JavaClient Admin:

  1. Navigate to Admin > Roles and Privileges

  2. Open your Design Engineer role

  3. Add conditional privilege: “Check-in to Released Parts”

  4. Set conditions:

    
Condition: Part has associated ECO in Implementation status
Permission: Allow CAD file check-in
Scope: Only files specified in ECO change description
Audit: Log all check-in attempts with ECO reference

  5. Configure privilege escalation:

    • Base users: Can check in ONLY when part is in Pending Change status
    • Power users: Can request temporary check-in override
    • Administrators: Can force check-in with audit trail and justification

Step 4: JavaClient Admin Actions for Immediate Needs

For your current situation with approved ECO and blocked check-ins, here’s the immediate workaround:

Option A: Temporary Status Override (Recommended)

  1. Log into JavaClient as PLM Administrator
  2. Open the affected part
  3. Right-click and select “Properties”
  4. Go to Lifecycle tab
  5. Click “Override Status” button
  6. Select “Pending Change” from dropdown
  7. In the justification field, enter: “ECO [number] approved - enabling design change check-in”
  8. Associate the ECO number
  9. Set automatic revert: “After ECO completion”
  10. Click Apply

This temporarily moves the part to a status that allows check-ins, with automatic return to Released when the ECO completes.

Option B: ECO-Based Check-in Process (Best Practice)

  1. Open the approved ECO in JavaClient
  2. Go to the Affected Items tab
  3. Select the part that needs CAD updates
  4. Click “Enable Check-in” button (this should be available in ECO context)
  5. System will temporarily grant check-in privileges to designers listed on the ECO
  6. Designers can now check in revised CAD files
  7. Files are checked in as “Pending” until ECO completion
  8. ECO completion finalizes the check-ins and updates part revision

Step 5: Configure Automated ECO-Lifecycle Integration

Implement workflow automation to handle this process systematically:

Create a workflow script (PX or equivalent) that runs when ECO status changes:


// Pseudocode - ECO lifecycle automation:
1. When ECO status = Implementation:
   a. Get list of affected parts
   b. For each part in Released status:
      - Create lifecycle override record
      - Move part to Pending Change
      - Enable check-in permission
      - Log change with ECO reference
   c. Notify designers check-in is enabled

2. When ECO status = Completed:
   a. For each affected part:
      - Finalize checked-in CAD files
      - Increment part revision
      - Move part to Released status
      - Lock CAD files
      - Generate change history
   b. Send completion notification

3. When ECO status = Cancelled:
   a. Revert any lifecycle overrides
   b. Discard pending check-ins
   c. Return parts to original Released status

Step 6: User Training and Process Documentation

Document the new process for your design team:

Designer Workflow for ECO-Driven CAD Changes:

  1. Wait for ECO to reach Implementation status
  2. Receive notification that check-in is enabled
  3. Open part in JavaClient
  4. Verify part status shows “Pending Change”
  5. Check out CAD file for editing
  6. Make approved design changes
  7. Check in revised CAD file
  8. Add check-in comment referencing ECO number
  9. Wait for ECO completion to finalize changes

Administrator Responsibilities:

  • Monitor parts stuck in Pending Change status
  • Handle exceptions where ECO completion fails
  • Audit check-in activities against ECO authorization
  • Manage lifecycle override requests

Step 7: Validation and Testing

Test the new configuration before rolling out:

  1. Create test ECO with test part
  2. Move ECO to Implementation phase
  3. Verify part transitions to Pending Change automatically
  4. Test designer check-in capability
  5. Complete ECO and verify part returns to Released
  6. Confirm revision incremented correctly
  7. Test cancellation scenario

Best Practices for Ongoing Operations:

  1. Lifecycle Governance:

    • Never allow direct Released → Released changes without ECO
    • Always use Pending Change as intermediate status
    • Maintain audit trail of all lifecycle overrides

  2. Permission Management:

    • Grant check-in overrides sparingly
    • Require ECO association for all Released part changes
    • Review override usage quarterly

  3. ECO Process Discipline:

    • Complete ECOs promptly to avoid parts stuck in Pending Change
    • Monitor parts in Pending Change > 30 days
    • Escalate stalled ECOs to change board

  4. CAD File Control:

    • Lock CAD files immediately after ECO completion
    • Prevent multiple concurrent ECOs affecting same part
    • Archive superseded CAD versions properly

This solution maintains your lifecycle control while enabling authorized design changes through proper ECO processes. The key is using the Pending Change status as a controlled window for modifications, automatically managed by ECO workflow.