The current implementation of the ActivatePortalXML Script from the Bosch Portal module (fs_portal.fsm) allows the use of either Store Element IDs or Store Element Reference Names as input for the "portalEntryPoints" variable:
![activateXMLVariable.PNG activateXMLVariable.PNG](/t5/image/serverpage/image-id/4156i477B819D99BC98E9/image-size/large?v=v2&px=999)
But the Script fails everytime the reference name of a Root element is used, see following snippet from the log of a test run:
ActivatePortalXml' - schedule entry 'Fulldeployment wcms_c NIGHTLY' (id=3055066)
INFO 05.02.2013 18:08:25.760 {seID=3055066} (de.espirit.firstspirit.impl.access.ScriptContextImpl): === GeneratePortalXml v4.2.476 ===
INFO 05.02.2013 18:08:25.761 {seID=3055066} (de.espirit.firstspirit.store.access.AccessStoreBuilder): SITESTORE loaded in 0ms
ERROR 05.02.2013 18:08:29.506 {seID=3055066} (de.espirit.firstspirit.impl.access.ScriptContextImpl): start-node not found: root
INFO 05.02.2013 18:08:29.513 {seID=3055066} (de.espirit.firstspirit.impl.access.ScriptContextImpl): generate xml for portal entry point: Bosch GlobalNet
In this case the reference name "root" corresponding to the SiteStore Root Element was used as the value, the script runs successfully if the ID of the SiteStore Root Element ("2912717") is used instead of its reference name ("root").
Our assumption is that maybe a deprecated API, accessing only Child elements, is used in the Portal module source code, since the "Store.getStoreElement()" method documentation apparently shows that this method (new since 4.0.17) fetches store elements regardless of its position in the hierarchy .