Oracle Agile PLM 9.3.5定制咨询：ECO模块新增Affected Items打印按钮需求

Hey there! Since you're new to Oracle Agile PLM 9.3.5 and starting totally fresh with no prior customization work, I’ll walk you through a clear, step-by-step process to add that print button on the ECO’s "Affected Items" tab. Let’s break this down into easy-to-follow chunks so you don’t get overwhelmed:

• First, make sure you have access to the Agile Java Client (AJC)—this is where nearly all PLM customization happens. You’ll also need an Admin or PLM Developer role to modify page layouts, create custom actions, and adjust permissions.
• Backup first! Save a copy of your current Agile environment (database + core config files) before touching anything. It’s a lifesaver if you accidentally break something as a new user.
• Spend 10-15 minutes getting familiar with two key tools:
  • Page Composer: The visual editor for modifying PLM page layouts and adding UI elements.
  • Agile SDK Basics: If you need custom print logic (beyond out-of-the-box templates), you’ll use the Java-based SDK to build functionality.

2.1 Get the Affected Items Tab’s Unique ID (AJC Action) #

• Open AJC, log in, and pull up any existing ECO. Switch to the "Affected Items" tab.
• Go to Admin > Page Composer (or Tools > Page Composer in some 9.3.5 builds) to enter edit mode for the tab.
• Locate the tab’s unique ID (it’ll look something like ECO_AffectedItems) and jot it down—we’ll need this to target the right page later.

2.2 Build the Print Action (Core Functionality) #

You have two options here, depending on how custom your print output needs to be:

Option A: Use Agile’s Built-In Print Templates (Fast & Simple) #

• Create a print template first: Go to Admin > Data Settings > Print Templates, click "New", select Item as the object type, and add the fields you want to print (e.g., part number, description, version, ECO reference). Save the template.
• Create a custom action: Head to Admin > Workflow > Custom Actions, click "New", choose Print as the action type, link it to your new print template, and set the trigger to "Only available on the Affected Items tab".

Option B: Custom Print Logic (Using Agile SDK) #

If you need to merge ECO details with item data or export to a specific format (like branded PDF), use the Agile Java SDK:

1. Write a Java class that implements the IAction interface. In the execute() method, pull the list of affected items from the current ECO, then generate your print output (use tools like JasperReports or Apache POI for PDFs/Excel files).
2. Compile your code into a JAR file and drop it into the Agile server’s $AGILE_HOME/integration/sdk/lib directory.
3. Register the action in AJC: Go to Admin > Workflow > Custom Actions, click "New", select Java as the type, and enter the full class path of your custom code.

2.3 Add the Button to the Affected Items Tab #

• Return to the Page Composer edit mode for the ECO’s Affected Items tab.
• In the toolbar/action bar area, click Add > Button, select the custom print action you created, and set the button text to "Print Changed Items" (or whatever makes sense for your team).
• Save the page configuration and exit edit mode.

2.4 Test & Validate #

• Open an ECO with affected items, switch to the tab, and confirm the button appears.
• Click the button to verify the print output includes all the right items and fields.
• If you hit permission errors, go to Admin > Roles > [Your Role] > Permissions > Custom Actions and make sure your role has access to the new print action.

• 9.3.5’s Page Composer has minor limitations—if you need precise button placement, use the Layout Manager tool instead.
• Never test customizations directly in production! Do all work in a staging environment first, then migrate once you’re confident it works.
• For SDK troubleshooting, check the local Agile docs at $AGILE_HOME/doc/sdk—it has full API references and sample code for common tasks.

内容的提问来源于stack exchange，提问作者Prabu M