As already suggested, please verify that the file manager is already running.  If you do not have access to check if file manager is running, check to see if you are able to download existing files already attached to other objects. Or, check with other users if they are able to download/upload files. If you have already verified that you are file manager is running, and if the pane to even select the file does not appear, it is likely that there are javascript errors or there are some corrupt cookies. Logoff (not close the window) from Agile, clear your browser cache and cookies, log back in and try again.

It will help to understand the use case if you provide additional details on what you are looking for. Maybe provide some references to subclasses you have, which attributes are configured on what subclasses, how the objects of the subclasses are related and what you are looking for in your search results.

The advanced search should be setup in the following way:

Changes -> <source subclass>  “Relationship Search”  Changes -> <related change subclass>
Criteria: Relationships.<related change subclass>.Cover Page. Released Date <date criteria>

What is your use case? If what you are trying to do is repetitive, one option is the export the criteria from the java client into an “agl” file. The “agl” file is just a zip file with the criteria in XML format. You can then write a script/program to modify the XML files are you please. Then, you can re-pack and re-import the criteria.

If all the necessary data for the import is in the file and the format of the file is pre-defined, I agree with Karthik’s idea. Use an object in Agile where the users can upload the file and then trigger the import PX from the Action menu of the object. The PX can use AIS to trigger the import by using pre-defined import mapping file. This PX can be configured to be a Post Async event to submit job in the background while allowing the user to continue.

To take this further – to allow auditing and status reporting after the import, I suggest using a change request object (maybe a different subclass or categorized specifically). The user can create the change request, attach the import file and submit. The PX runs on submit to import the file and then moves the change to either Review or Released status depending on errors/success of the request.