Test if a file exists in the Constants.LOCATION_COMMON_FILES directory

Hello Christian,

Since getFile returns an array of bytes the most simple way is to check its lenght. If length equals 0, then file doesn't exist.

var testFile = Context.getFile("test.xml", Constants.LOCATION_COMMON_FILES)
if (testFile.length>0) {
    ...
}

---

BR, Nikita

I just spoke with one of the devs and he confirmed that testing for a zero-length byte array is indeed the correct way to do this. The exception that was thrown in older releases was actually not supposed to happen.

Thank you both for your answer and your confirmation !!!

But I'm not sure this will be the answer in some cases. A zero length file can exists and may be lock by an other user than me....

Anyway, this is the Aris answer for the moment and for my purpose, i will first the "zero length" technic, but be carefull with the write rigth...

Meilleures salutations,
Christian

You can use the ScriptAdmin report component to explore the Common Files directory.

Example:

var nLocale = Context.getSelectedLanguage();
var scriptAdminComponent = Context.getComponent("ScriptAdmin");

function getCommmonCategoryComponentID() {
    var allScriptComponentInfos = scriptAdminComponent.getScriptComponents();
    
    for each(var scriptComponentInfo in allScriptComponentInfos) {
        if(scriptComponentInfo.getComponentName() == "common") {
            return scriptComponentInfo.getComponentID();
        }
    }
    
    throw new Packages.java.lang.IllegalStateException("Common script category not found");
}

function getCommonFileNames() {
    var commonScriptComponentID = getCommmonCategoryComponentID();
    
    var allScriptInfos = scriptAdminComponent.getScriptInfos(commonScriptComponentID, null, nLocale);
    
    function mapScriptInfoToName(someScriptInfo) {
        return someScriptInfo.getName();
    }
    
    return allScriptInfos.map(mapScriptInfoToName).sort();
}

var result = getCommonFileNames();

This creates a result array of file names from the Common Files directory.

You can find out more about this by taking a look at "Methods for reports and semantic checks" > "Global Objects" > "Report component interfaces" > "ScriptAdmin" in the ARIS Script documentation.