Hi Mala,

   what happens if you generate docx file instead of Excel? Are Images, colors, etc preserved?

If you want more proper Excel generation, I would use the POI library, xdocore for me works best if I create PDFs, Docx and html.

Best regards,
   Dennis

Hi,

    you got already the object retrieved in your code where you use IDataObject atoObj = info.getDataObject();. Agile PLM is throwing an exception because the roles and privileges which are used to EXECUTE the PX are insufficient. As an example it is like a agile user that has no right to read or modify a object. Providing your PX with the necessary privileges should solve this issue. Let me know if this solved your issue.

regards,
  Dennis

Hi,

   Oracle Agile PLM already provides a tool for importing files into Agile. An just as you explain, you use a index file for that. You can find all information in the oracle documentation, http://docs.oracle.com/cd/E69230_02/otn/pdf/user/html_agaau/output/chapter_13.htm#sthref350

A sample file for your cad files to be uploaded can look like this in the index file:

FILEFOLDER,DESIGN00011,1,D:/docs/Design.doc,FILE,Design Document

If you have to convert CAD files or to migrate, please let me know as I should be able to helo you with that too.

Best regards,
   Dennis

Hi MG,

  array index out of bound ocurrs when you try to access an element at a certain position that does not exist. As you have not provided the code I interpret that you are trying to create a new row, this is what causes the exception to ocurr.

  You may

a) not retrieve the table properly

b) not have a editable table

c) the index you indicate does not exist (yet)

Let me know if this solved your issue, otherwise please provide your code.

Hi Divkar,

  if you go to the workflow settings/configurations in admin client and check the criteria for this state you should see this field as required. Depending on the business case you may add/modify the criteria.
<br /

Hi,

   we did this a few years ago for a customer in France. Those changes need to be done on database level and require good preparation if documents have been released previously. Preliminary documents you consider a batch “save-as” process to your part class.

1. You need a environment were you can safely do first tests, don’t start with prod. Make DB backup to rollback easily.

2. Verify each attribute you want to be brought over into your part class. if you switch from documents to parts and miss attributes you get averify errors and data corruption will ocurr

3. Make sure you understand all item/Page2/Page3 tables in Agile database, start with one item you know, so you easily find the exact rows to modify. (I’m sorry i don’t have them by hand right now)

4. The procedure should be like:
4.1 Run averify to ensure you have a consistent db
4.2 Make and run your SQL script. You may see some triggers/lockers popup you will have to disable.
4.3 run “create indexes” so the new parts get published
4.4 Run averify again to check no data inconsistency has been created
4.5 start agile and verify data (Structures, class type, related changes)

Let me know if this information was helpful.

Best regards,
   Dennis

Have you moved your Jaxp Jar file? Any changes to the classpath? Looks like the class can’t be picked up. Restoring/Copying the class into the classpath should solve this issue.

Sound as design, what is wrong with this behaviour? Do you want to prevent the superuser from doing this?

Your questions does not seem clear to me. Can you explain more? This info may help you:

a) You can send Agile emails to your email account (in Outlook)

b) There exists a plugin to load/save files from and to MsWord/MsExcel/msOutlook into Agile PLM.

Best regards,
   Dennis

Hi Divkar,

   several options depending on the business case you have. Would a notification of that error to the users inbox and/or email be a solution? You can use the sendnotification function for that. Or you write to a text field you enable for warning messages. Third option, you can try trigger javaPX from event, should allow a action result of type warning(see Agile Developer guide for code example).

Regards,
  Dennis