Skip Headers

Agile Product Lifecycle Management Product Governance and Compliance User Guide Release 9.3.3 E39296-01 |
| Contents

Previous | Next |

# B Overview of the Microsoft Excel-based Client for Agile PG&C

Important: Configuration steps described in this chapter apply only to customers who have purchased Agile Product Governance & Compliance. Agile Product Governance & Compliance (PG&C), one of the Agile PLM product solutions, is designed to help manufacturers audit the presence and amount of regulated substances used in their products, and to demonstrate that they responsibly dispose of, recycle, or reuse parts containing those substances. Agile PG&C includes built-in support for the Microsoft Excel-based client for OEM manufacturing regulations, including the Japan Green Procurement Survey Standardization Initiative (JGPSSI), and substances and weights rollups.

Important: Although Agile provides two Microsoft Excel templates for Agile PG&C, the solution is extensible. You can develop other Microsoft Excel templates to handle other Declaration classes your company has defined. For information about how to develop Microsoft Excel templates for use with Agile PG&C, contact your Oracle Consulting Services representative.

Important: After installing Agile PLM, if any of the changes detailed in this chapter are required for your Excel integration, the correct sequence is: (a) stop the application server(s); (b) undeploy; (c) make the changes in <standard <agilePLM> Install folder> > application.ear; (d) re-deploy; and (e) re-start the servers.

## B.1 JGPSSI Support

JGPSSI has created a standardized digital form that companies can use to inquire about the chemical substances contained in parts and materials they procure in Asia. For more information about JGPSSI, see the Japan Electronics and Information Technology Industries Association Web site: http://home.jeita.or.jp/eps/greenTOP-eg.htmlhttp://home.jeita.or.jp/eps/greenTOP-eg.html

JGPSSI uses Microsoft Excel tools for collecting information about substances contained in assemblies for Japanese Green Procurement. Agile provides a flexible and reusable integration between Agile PG&C and Microsoft Excel that allows customers to use the JGPSSI spreadsheet without modification, and then upload the information to Agile PG&C after validation.

Agile PLM supports a Japanese-language template of the JGPSSI spreadsheet. The Japanese-language templates are only available to customers who have purchased the Japanese Server License. Also, the administrator must set users' Language and Encode user preferences to the appropriate setting to work in that language in the Agile clients' user interfaces. Please contact Oracle Consulting Services for more information.

## B.2 Substances and Weights Rollups

You can use Microsoft Excel to perform analysis of the Bill of Substances (BOS) information for an assembly. Using the Actions menu command Rollup in Excel, the integrated Excel spreadsheet can roll up the substances and weights for the top-level assembly.

Note: Agile PLM supports a Japanese-language template of the Substances and Weights spreadsheet.

PLM also supports localized versions in Chinese, French, and German of the Substances and Weights Rollup feature used in Microsoft Excel-base Client. However, the localized template does not work for these languages out-of-the-box, the template must be adjusted by Oracle Consulting-Agile Practice.

The Japanese-language templates are only available to customers who have purchased the Japanese Server License. Localized versions also need appropriate License Key. Also, the administrator must set users' Language and Encode user preferences to the appropriate setting to work in that language in the Agile clients' user interfaces. Please contact Oracle Consulting-Agile Practice for more information.

## B.3 Client Software Requirements

The Microsoft Excel-based client for Agile PG&C requires the following client-side software:

### B.3.1 Operating System

- Windows 2000 Pro SPX

- Windows XP Pro SP2

- Windows 2003 Pro SP1

### B.3.2 Client Applications

- Microsoft Excel XP, Microsoft Excel 2003, Microsoft Excel 2007, or Microsoft Excel 2010

- Microsoft Internet Explorer 7.0 or above

For complete Agile PLM software requirements, see the Agile PLM Capacity Planning and Deployment Guide.

## B.4 Microsoft Excel-based Client FAQ

This section answers some common questions about the Microsoft Excel-based client for Agile PG&C.

How does the Microsoft Excel-based client work? What is the underlying technology used to integrate with Agile PG&C?

The Microsoft Excel-based client uses the following technology:

- Agile PLM Process Extensions - Agile Web Client launches the Microsoft Excel-based client through process extensions (PX), which are programs that extend the functionality of the client interface.

- Agile PLM ActiveX Control - an Internet Explorer plugin that monitors use of the Microsoft Excel-based client and downloads and uploads data from the Agile PLM server as requested by the client.

- HTTP, HTTPS, or SMTP - standard protocols used to move data between the server and the client

- Microsoft Excel - spreadsheet client with its own client-side business logic.

Other than Microsoft Excel, is any other client software required for the Microsoft Excel-based client?

The Agile PLM ActiveX Control, an Internet Explorer plugin, is required. It's downloaded and installed automatically the first time a user launches the Microsoft Excel-based client from Agile Web Client. Of course, Internet Explorer 7.0 is also required, as well as a Windows operating system.

What Microsoft Excel templates does Agile PG&C provide by default?

There are two Excel applications provided out-of-the-box with Agile PG&C:

- JGPSSI Declaration application - supports Japanese Green Procurement

- Rollup In Excel application - calculates substances and weights rollups for top-level assemblies

Can I create new Microsoft Excel templates for use with Agile PG&C?

Yes, the solution is extensible. For information on how to develop Microsoft Excel templates for Agile PG&C, contact your Oracle Consulting Services representative.

Can I create Microsoft Excel templates for use with other Agile PLM solutions, such as Product Collaboration?

No. Currently, only Declaration classes and their subclasses are supported. Other classes may be supported in future Agile PLM releases.

Can I use the Firefox browser to launch the Microsoft Excel-based client?

No. Only Microsoft Internet Explorer 7.0 is supported.

Must I be logged into Agile Web Client to use the Microsoft Excel-based client for Agile PG&C?

No. You can use the Microsoft Excel-based client synchronously (that is, by opening a spreadsheet from Agile Web Client) or asynchronously (that is, by opening a spreadsheet attached to an email message).

How do I launch the Microsoft Excel-based client from Agile Web Client?

Process extensions are used to launch the Microsoft Excel-based client. The process extension for launching JGPSSI-in-Excel is initiated from the Actions menu of JGPSSI declarations. The process extension for launching Substances and Weights rolllup in Excel is initiated from the Actions menu of items. For information about developing process extensions, see the Agile SDK Developer Guide.

Can I sign the Agile PLM ActiveX Control with my company's certificate?

Yes. See "Digitally Signing the Agile PLM ActiveX Control".

Does the Microsoft Excel-based client require any special authentication?

The Microsoft Excel-based Client uses the same credentials that you use to log into Agile Web Client, and it prompts you to log into a separate Agile PLM session when you choose Agile > Submit Response or Agile > Open Request.

Where does the client-side business logic for the Microsoft Excel-based client reside?

Client-side business logic resides entirely in the Microsoft Excel template.

How does the Microsoft Excel-based client handle notifications for Declarations?

Agile PLM provides four system-generated notifications related to the Microsoft Excel-based client:

- Declaration Excel Submit Success Supplier Notification - notification sent to the supplier to confirm successful submission of a Declaration.

- Declaration Excel Submit Import Failure - notification sent to the compliance manager or originator to inform him that the submitted Declaration failed to be processed on the server due to import problems.

- Declaration Excel Submit Failure - notification sent to the compliance manager or originator to inform him that the submitted Declaration failed to be processed on the server due to an exception.

- Declaration Excel Submit Failure Supplier Notification - notification sent to the supplier to inform him that the Declaration failed to be submitted due to import errors.

Each notification includes text for the subject and body of a message. The Agile PLM administrator can modify these notification messages.

To customize these notifications, start the Agile Java Client and log in as an administrator user. Click the Admin tab, and choose System Settings > Notifications > Declaration Notifications. Microsoft Excel-based client notifications are listed under "Declaration Miscellaneous Notifications."

For more information about Agile PLM notifications, see the Agile PLM Administrator Guide.

What languages does the Microsoft Excel-based client support?

The JGPSSI and Rollup in Excel standard templates support English only. Other templates can be developed to support other languages.

Microsoft Excel-based client messages and captions support all languages supported by Agile PLM 9.3.3. Additionally, the menus of Microsoft Excel templates can be customized for different languages.

Does the Microsoft Excel-based client use VBA macros?

The Microsoft Excel templates provided for Agile PG&C do not use VBA macros. Although you are not prevented from developing a Microsoft Excel template that uses VBA macros, antivirus software may prevent the macros from running, and you should set the security level in Microsoft Excel to at least Medium (choose Tools > Macro > Security).

## B.5 Configuration Sequence

To enable support for the Microsoft Excel-based client for Agile PG&C, you must perform the following manual configuration steps after Agile PLM has been installed:

1. Set up privileges for Agile PG&C objects (such as Substances and Declarations).

2. Enable specific attributes in PG&C-related classes to ensure the Microsoft Excel-based client functions correctly.

3. Restrict Declaration names to 50 characters for every class that you are enabling the Microsoft Excel-based client.

4. Obtain a production license for the Agile PLM ActiveX Control from your Agile Account Executive and deploy the related files on the Agile Application Server

5. Optionally, digitally sign the Agile PLM ActiveX Control.

6. Use Agile Java Client to set the Allow Download of Productivity Components preference to Yes. This allows Agile Web Client users to download the Agile PLM ActiveX Control from the server.

7. Install the Agile PLM ActiveX Control.

8. Test that the Microsoft Excel-based client for Agile PG&C works properly.

## B.6 Setting Privileges for Agile PG&C Objects

This section describes how to set privileges for Agile PG&C objects. If you don't ensure that privileges are properly set, you may not be able to move data from the JGPSSI spreadsheet into Agile PLM and vice versa.

To set privileges for Agile PG&C objects:

1. Log into Agile Java Client as a user with Administrator privileges.

2. Click the Admin tab.

3. Choose User Settings > Privileges.

4. Open the following privilege masks, and for each one click the drop-down arrow next to the Applied To field and add the following attributes:

5. After modifying the Applied To field for each of the privilege masks listed above, click OK.

6. To save the privilege mask, click Save.

7. Click Close.

8. Click Close.

## B.7 Enabling Attributes that are Required for Excel Rollups

The following attributes must be enabled (Visible property is set to Yes for each attribute) at the class level for the Microsoft Excel-based client to function correctly.

### B.7.1 Classes: Parts, Manufacturer Parts, and Documents

xxxx

#### B.7.1.1 Compliance Tab>Composition Table

- Specification Name

- Declaration Name

- Declared Weight

- Supplier

#### B.7.1.2 Compliance Tab > Substances Table

- Child Level

- Substance Name

- Substance Type

- Mass

- Declared PPM

- CAS Number

- Conversion Factor

### B.7.2 Classes: Parts and Documents

xxxx

#### B.7.2.1 BOM Tab

- Item Number

- Item Description

- Item Rev (Item Revision)

- Qty (Quantity)

#### B.7.2.2 Manufacturers Tab

- Mfr. Part Number

- Mfr. Part Description

- Mfr. Name

## B.8 Restricting the Length of Declaration Names

Agile's Microsoft Excel-based client requires Declaration names to not exceed 50 characters. If a Declaration has a name longer than 50 characters, you might not be able to open it in Microsoft Excel.

To avoid potential problems opening Declarations with long names, you should restrict Declaration names to 50 characters for every class that you are enabling the Microsoft Excel-based client. You can do this by making autonumbers required (assuming that each number in the autonumber sequence does not exceed 50 characters) or by adjusting the maximum length of the Cover Page > Reference Number attribute.

To make autonumbers required for a Declaration subclass:

1. Log into the Agile Java Client as an administrator.

2. Click the Admin tab.

3. Under Data Settings, double-click Classes.

4. Open a Declaration subclass that has enabled the Microsoft Excel-based client (for example, JGPSSI Declaration).

5. Select the General Information tab.

6. In the Autonumber Required list, select Yes.

7. In the Autogenerate list, select Yes.

8. Click Save.

To adjust the maximum length of Declaration names:

1. Log into the Agile Java Client as an administrator.

2. Click the Admin tab.

3. Under Data Settings, double-click Classes.

4. Open a Declaration class that has subclasses that have enabled the Microsoft Excel-based client (for example, JGPSSI Declarations).

5. Click the User Interface Tabs tab.

6. Double-click Cover Page.

7. Click the Attributes: Cover Page tab.

8. Double-click the Reference Number attribute.

9. Set the MaxLength property to 50 or less.

10. Click Save.

## B.9 Deploying License Files for the Agile PLM ActiveX Control

To enable support for the Microsoft Excel-based client for Agile PG&C, you must obtain a valid license for the Agile PLM ActiveX Control, an Internet Explorer plugin. This license is specific to the server on which the Agile Application Server is installed. To obtain the license file (license.xml) and a properties file (properties.js), contact your Agile Account Executive.

After you obtain the license file and properties file, you need to deploy the files on the Agile Application Server.

Note: If you have an application server cluster, you must deploy the Agile PLM ActiveX Control license files on the Repository Host server for Oracle Application Server or the Administration Server for WebLogic Server. The application server will then propagate the license files to other servers in the cluster.

To deploy license files for the Agile PLM ActiveX Control:

1. Stop the Web proxy server.

2. Stop the Agile Application Server.

3. Windows: On the application server computer, open a command prompt window.

   UNIX: On the application server computer, open a terminal window and log on as the user who installed the Agile Application Server.

4. Expand the Agile application.ear file:

   Windows: \AGILE_HOME\install\bin\ExtractArchive.cmd

   UNIX: /AGILE_HOME/install/bin/ExtractArchive.sh

5. Copy the license.xml and properties.js files that you received from Agile to the following location:

   \AGILE_HOME\agileDomain\applications\ExpandedEar\ExpandedWar\ambassador

6. Repack the Agile application.ear file:

   Windows: \AGILE_HOME\install\bin\RepackArchive.cmd

   UNIX: /AGILE_HOME/install/bin/RepackArchive.sh

7. Undeploy the Agile application, and then redeploy it.

   <windows>:

   \AGILE_HOME\agileDomain\bin\UnDeployAgilePLM.cmd

   \AGILE_HOME\agileDomain\bin\DeployAgilePLM.cmd

   UNIX:

   /AGILE_HOME/agileDomain/bin/UnDeployAgilePLM.sh

   /AGILE_HOME/agileDomain/bin/DeployAgilePLM.sh

8. Start the Agile Application Server.

9. Start the Web proxy server.

## B.10 Using the Developer Version of the Microsoft Excel Integration License File

If you are developing or testing Microsoft Excel templates for Agile PLM Declaration classes, you can use the developer version of the Microsoft Excel integration license file that is installed with the Agile PLM server. The developer license for the Agile PLM ActiveX Control provides the same functionality as the production license. However, when you install it, a warning message appears: "An UNTRUSTED web site is trying to use Agile PLM ActiveX Control to control your desktop." Click Yes in the warning dialog box to continue installing the control.

## B.11 Digitally Signing the Agile PLM ActiveX Control

The first time you choose one of the commands that launch the Microsoft Excel-based client (such as Actions > Open In Excel) in Agile Web Client, the Agile PLM ActiveX Control is automatically downloaded and installed on your computer. For security reasons, Internet Explorer requires that software it downloads must have a digital signature. A digital signature lets you verify the contents of a file and ensures that it comes from a trusted source.

When you install Agile PLM, the Agile PLM ActiveX Control is already digitally signed from Agile Software. You can choose to use your company's own digital signature for the control instead. If you use your company's digital signature, each time a user of your Agile PLM system downloads the Agile PLM ActiveX Control it will be recognized as coming from your company and not from Agile Software.

You provide a digital signature by purchasing a certificate from a certificate authority. A certificate authority is an entity that issues digital certificates for use by other parties. Examples of certificate authorities are Verisign (`http://www.verisign.com/``http://www.verisign.com/`) and CAcert (`http://www.cacert.org/``http://www.cacert.org/`).

For more information about digital signatures, go to the MSDN site (`http://msdn.microsoft.com/``http://msdn.microsoft.com/`) and search for "Digitally Signing ActiveX Components".

To digitally sign the Agile PLM ActiveX Control:

1. Stop the Web proxy server.

2. Stop the Agile application server.

3. Windows: On the application server computer, open a command prompt window.

   UNIX: On the application server computer, open a terminal window and log on as the user who installed the Agile application server.

4. Expand the Agile application.ear file

   Windows: \AGILE_HOME\install\bin\ExtractArchive.cmd

   UNIX: /AGILE_HOME/install/bin/ExtractArchive.sh

5. Digitally Sign the agileambassador.cab file found in the following location:

   \AGILE_HOME\agileDomain\applications\ExpandedEar\ExpandedWar\ambassador

6. Repack the Agile application.ear file

   Windows: \AGILE_HOME\install\bin\RepackArchive.cmd

   UNIX: /AGILE_HOME/install/bin/RepackArchive.sh

7. Undeploy the Agile application, and then redeploy it.

   <windows>:

   \AGILE_HOME\agileDomain\bin\UnDeployAgilePLM.cmd

   \AGILE_HOME\agileDomain\bin\DeployAgilePLM.cmd

   UNIX:

   /AGILE_HOME/agileDomain/bin/UnDeployAgilePLM.sh

   /AGILE_HOME/agileDomain/bin/DeployAgilePLM.sh

8. Start the Agile application server.

9. Start the Web proxy server.

## B.12 Enabling Downloading of Productivity Components

The Agile PLM ActiveX Control is a plugin for Microsoft Internet Explorer that users can download to their client machines. To enable downloading of the Agile PLM ActiveX Control from the server, the Agile PLM administrator must log into the Agile Java Client and make sure the Agile PLM preference named Allow Download of Productivity Components is set to Yes. Otherwise, users won't be able to download the ActiveX control and use the Microsoft Excel-based client.

Note The Agile PLM ActiveX Control is supported only on the Microsoft Internet Explorer browser. You cannot use it with other browsers, such as Firefox.

To enable downloading of the Agile PLM ActiveX Control:

1. Log into Agile Java Client as a user with Administrator privileges.

2. Click the Admin tab.

3. Choose Server Settings > Preferences.

4. For the Allow Download of Productivity Components preference, select Yes.

5. Click Save.

For more information about setting Agile PLM preferences, see the Agile PLM Administrator Guide.

## B.13 Installing the Agile PLM ActiveX Control

If you enable downloading of the Agile PLM ActiveX Control (see the previous section), the plugin is installed automatically on the client computer when you choose a command (such as Actions > Open In Excel) that launches the Microsoft Excel-based client. Separate installation of the plugin is unnecessary.

## B.14 Modifying Excel-based Process Extensions for Japanese Versions

This section describes how to modify process extensions for the Japanese templates. Recall that Agile Web Client launches the Microsoft Excel-based client through process extensions, which are programs that extend the functionality of the client interface.

### B.14.1 Supporting the Japanese Version of the JGPSSI Template

In Java Client, modify the URL for the Open In Excel process extension to append the mapfile request argument:

mapfile=ExcelApplications_JP.xml

For example:

`http://pgctest.agile.agilesoft.com/Agile/AmbassadorServlet?action=open&internalurl=true&height=220&width=365&mapfile=ExcelApplications_JP.xml`

`http://myserver.agile.agilesoft.com:8888/web/AmbassadorServlet?action=open&internalurl=true&height=220&width=365&mapfile=ExcelApplications_JP.xml`

Note You can create a new process extension with a different caption for the Japanese version of the JGPSSI template. In this case, both English and Japanese templates are supported. If you want to use Japanese JGPSSI, you must log in to the Agile system as a Japanese user to perform Actions > Open In Excel. This is required both for users at your company and any supplier users on the Excel client.

### B.14.2 Supporting the Japanese Version of Substances and Weights Rollups

In Java Client, modify the URL for the Rollup in Excel process extension (which opens the Substances and Weights template) to append the mapfile request argument:

mapfile=ExcelApplications_JP.xml

For example:

http://pgctest.agile.agilesoft.com/Agile/default/Rollup.jsp?actiion=open&internalurl=true&height=220&witdth=365&mapfile=ExcelApplications_JP.xml

http://myserver.agile.agilesoft.com:8888/web/default/Rollup.jsp?action=open&internalurl=true&height=220&width=365&mapfile=ExcelApplications_JP.xml

### B.14.3 Supporting Other Languages in Substances and Weights Rollups

Agile PLM supports localized versions of the Rollup in Excel process extension (which opens the Substances and Weights template) in Simplified Chinese, Traditional Chinese, French, and German.

Note: The localized template does not work for these languages out-of-the-box, the template must be adjusted by Agile Solutions Delivery.

1. Add the language version of Rollup template to

   ambassador\templates as rollup_<language>.xls

   For example, Simplified Chinese is rollup_zh.xls.

   Important Herein, the expression "ambassador" is intended to designate the "Ambassador" folder provided in the Agile PLM build. It is under the standard Agile PLM Install folder, where an ear file - application.ear - is deployed to the application server.

2. Under ambassador\scripts\resources, create a copy of the rollup_en.properties and name it rollup_<language>.properties. For example, Simplified Chinese is rollup_zh.properties.

   Edit rollup_<language>.properties to change the translation after each equal sign (=) in this language translation.

   Under ambassador\xml, create a copy of the rollup.xml and name it rollup_<language>.xml. For example, Simplified Chinese is rollup_zh.xml. Edit rollup_zh.xml as follows:

   a. Replace all rollup_en.properties with the language property file rollup_zh.properties

   b. Modify the "source" attribute value of the <form> element under the Open Assembly button item.

   Add the new URL parameter mapfile=ExcelApplications_ZH.xml. Use this language's map file.

   <form source="@VIRTUALPATH@/default/RollupData.jsp?classID=@FLEXFIELD3@&amp;mapfile=ExcelApplications_ZH.xml" height="350" width="580"/>

3. Create a copy of the ExcelApplications.xml under ambassador\config. Name the copy as ExcelApplications_ <language>.xml. For example, Simplified Chinese is like ExcelApplications_ZH.xml.

   Edit it to specify the attributes for the language version of the Substances and Weights template. For example, for Simplified Chinese:

   <?xml version="1.0" encoding="UTF-8"?>

   <ExcelApplications>

   <ExcelApplication name="JGPSSI" baseClass="Declaration"

   subclassName="JGP Declaration"

   classId="2000002423" subclassID="2000002421" titleblockNameAttrId="agile.2000002615"

   initXMLTemplate="JGPSSI.xml" excelTemplate="JGPSSI.xls" exportXSL="aXMLToJGPSSI.xsl"

   submitXMLTemplate="jgpssi_submit.xml" attachXlsOnSubmit="true" />

   <ExcelApplication name="Rollup" baseClass="Item" subclassName="Part"

   classId="10000" subclassID="2000002365"

   titleblockNameAttrId="agile.1001" initXMLTemplate="rollup_zh.xml" excelTemplate="rollup_zh.xls" />

   </ExcelApplications>

4. In Java Client, modify the URL for the Rollup in Excel process extension to append the mapfile request argument:

   mapfile=ExcelApplications_<language>.xml

   For any localized template ("ZH" specifies Simplified Chinese):

   `http://pgctest.agile.agilesoft.com/Agile/default/Rollup.jsp?action=open&internalurl=true&height=220&width=365&mapfile=ExcelApplications_ZH.xml`

   `http://myserver.agile.agilesoft.com:8888/web/default/Rollup.jsp?action=open&internalurl=true&height=220&width=365&mapfile=ExcelApplications_ZH.xml`

   Note: You can create a new process extension with a different caption for the localized version of the Substances and Weights template. In this case, both English and the localized language's templates are supported. If you want to use localized Substances and Weights Rollup, you must log in to the Agile system as a user in the localized language to perform Actions > Rollup in Excel. This is required both for users at your company and any supplier users on the Excel client.

## B.15 Troubleshooting

This section provides solutions to problems you may encounter in configuring the Microsoft Excel-based client for Agile PG&C.

Import and Error Logs

Import and error logs for the Microsoft Excel-based client can be found in the server's Temp folder.

On Windows 2000/2003 servers, the Temp folder is usually found at

C:\Documents and Settings\<current_logged_in_user>\Local Settings\Temp\AgileEITemp

or

C:\Winnt\Temp\AgileEITemp

If you are unsure where to find the Temp folder, open a Command Prompt window and type the following command:

    cd %temp%\AgileEITemp

On UNIX servers, the Temp directory is usually found at

/var/tmp/AgileEITemp

The most recent folder under AgileEITemp contains data and import or error logs of the last submission done in Excel

Runtime error

When you choose any command that launches the Microsoft Excel-based client (such as Actions > Open In Excel) in Agile Web Client, a Runtime Error window appears.

Solution:

The license files for the Agile PLM ActiveX Control, which are located on the Agile Application Server, are invalid. Please contact Agile Support to request new license files. Once you receive the files, you must deploy them on the application server. See Deploying License Files for the Agile PLM ActiveX Control.

This feature has not been enabled by the application administrator

When you choose an Action that launches the Microsoft Excel-based client in Agile Web Client, the popup window reads, "This feature has not been enabled by the application administrator." Consequently, the Agile PLM ActiveX Control could not be downloaded.

Solution:

In the Agile Java Client, set the Agile PLM preference Allow Downloading of Productivity Components to Yes. See "Enabling Downloading of Productivity Components".

The page cannot be displayed

When you choose an Action that launches the Microsoft Excel-based client in Agile Web Client, the popup window reads, "The page cannot be displayed."

Solution:

Make sure the Web proxy server is running.

Instead of opening a Microsoft Excel file, Agile Web Client login page appears in another window

When you choose an Action that launches the Microsoft Excel-based client in Agile WebClient, the Microsoft Excel file doesn't appear and instead a new browser window opens with Agile Web Client login page.

Solution:

- Make sure Agile Web Client login page you're using has the fully qualified domain name for the server in the URL. For example, if the fully qualified domain name of the server is "plm.mycompany.com", Agile Web Client login page URL should look like this:

`http://plm.mycompany.com/Agile/PLMServlet`

- Make sure the Agile PLM ActiveX Control license file (license.xml) uses a fully qualified domain name for the Agile Application Server.

The Open In Excel pop-up window appears and then closes, but Microsoft Excel doesn't launch

When you choose an Action that launches the Microsoft Excel-based client in Agile Web Client, the Open In Excel pop-up window appears for a few seconds, and then it closes without launching Microsoft Excel.

Solution:

The Declaration you're trying to open has a very long name. Choose Actions > Save As to save the Declaration with a name that is 50 characters or less.

To avoid this problem, restrict Declaration names to 50 characters. See "Restricting the Length of Declaration Names".

The Actions menu does not include commands to launch the Microsoft Excel-based client

When you open an Item in Agile Web Client, the Rollup in Excel command isn't available on the Actions menu. When you open a JGPSSI Declaration in Agile Web Client, the Open In Excel, Import JGPSSI, and Export JGPSSI commands aren't available on the Actions menu.

Solution:

The Agile PG&C process extensions have not been assigned to Agile PLM classes. The Agile PG&C process extensions are assigned automatically to classes when Agile PLM is installed, but perhaps the Administrator modified the classes and inadvertently unassigned the Agile PG&C process extensions.

Here is how the Agile PG&C process extensions should be assigned:

- The Rollup In Excel process extension must be manually assigned to the Items classes, that is, Parts and Documents.

- The Open In Excel, Import JGPSSI, and Export JGPSSI process extensions should be automatically assigned to the JGPSSI Declarations class. Please verify that this was accomplished; if they did not load, it needs to be done manually.

For information on how to assign process extensions to classes, see the Agile PLM Administrator Guide.

The cell or chart you are trying to change is protected and therefore read-only

When you open a JGPSSI Declaration in Microsoft Excel and try to edit one of the cells, you see the following error message: "The cell or chart you are trying to change is protected and therefore read-only. To modify a protected cell or chart, first remove protection using the Unprotect Sheet command (Tools menu, Protection submenu). You may be prompted for a password."

Solution:

The colored cells of the JGPSSI template (such as headings) are protected and cannot be edited. You should edit only unshaded (white) cells.

Microsoft VBScript runtime error 1B6: Object doesn't support this property or method

When you choose any command that launches the Microsoft Excel-based client (such as Actions > Open in Excel) in Agile Web Client, an error message appears: "Microsoft VBScript runtime error 1B6: Object doesn't support this property or method."

Solution:

Internet Explorer had problems downloading the digital certificate for the Agile PLM ActiveX Control. Click OK in the error message box to continue.

The problem may be due to a comma in the Company field of the digital certificate. If there isn't a comma in the Company field, you may need to update your Internet Explorer browser with the latest patch from Microsoft.

You must restart your computer before the new settings will take effect

When you choose any command that launches the Microsoft Excel-based client (such as Actions > Open in Excel) in Agile Web Client, a message box appears: "You must restart your computer before the new settings will take effect. Do you want to restart your computer now?"

Solution:

You have a previous version of the Agile PLM ActiveX Control installed, and Microsoft Excel is currently open, so the control cannot be updated. To install the new control, close Excel, and then click No in the message box (to not restart the computer). Choose Actions > Open in Excel again.

## B.16 Testing the Microsoft Excel-based Client for Agile PG&C

This section describes how to test whether the Microsoft Excel-based client works properly.

To test JGPSSI Declarations:

1. In Agile Web Client, choose Create > Declarations > JGPSSI Declarations.

2. Specify a supplier. Also, make sure the Continue Creation in Wizard box is checked. Click Continue.

3. In the Compliance Manager field, select a user who is a compliance manager.

4. In the Workflow field, select Default Declarations. Click Next.

5. On the Add Specifications page, click Next.

6. On the Add Items page, click Add to add an item. Type an existing item number and click Ok.

7. Click Finish.

8. Choose Actions > Open in Excel. After a moment, a Security Warning dialog box appears.

9. Make sure the Always trust content from Agile Software Corporation box is checked. Click Yes to install and run the Agile PLM > ActiveX Control (also called Agile Ambassador).

10. After a moment, Microsoft Excel is launched and a file with the name declaration_number.xls is opened. You are prompted to save the file to a folder on your desktop called Agile Spreadsheet Files. Click Save.

11. Close Microsoft Excel and return to Agile Web Client.

12. For the new JGPSSI Declaration you created, click Next Status to open it to the supplier.

13. Select users to notify, and click ok.

14. Click the Exit button to log out.

15. Click Login. Log in as a contact user for the supplier associated with the JGPSSI Declaration.

16. Click the link to the JGPSSI Declaration to open it.

17. In the Navigation pane, click Open In Excel.

18. After a moment, Microsoft Excel is again launched and the same file as earlier is opened. You are prompted to save the file to a folder on your desktop called Agile Spreadsheet Files. You already saved it earlier, so click Cancel.

19. Fill in a one or more fields on the sheet. For example, change the value of the Parts Mass field.

20. Save the Microsoft Excel file.

21. Choose Agile > Submit Response. You need to log in at this point. The Submit Response window appears.

22. Type your approval password, and click Submit.

23. After your response is uploaded, a message box appears: "The declaration has been submitted for processing. Updates may not be immediately visible in the Agile system." Click Ok.

To test Substances and Weights Rollups:

1. In Agile Web Client, open a part that is a top-level assembly with multiple substances.

2. Choose Actions > Rollup in Excel.

3. Select the specification that is used for the composition, and click Ok. The Excel file with the same filename as the part number appears.

4. In the Excel file, choose Agile > Run Scenario. The rolled-up amounts for materials and substances used in the assembly are displayed.