Processing Templates via importing alfresco package

[chuck]

Hi,
I have just taken control of some alfresco code and am currently wondering as to the process of creating template spaces from ACP files and particularly what area of code reads this and interpretes the XML file within.

I have an ACP file containing XML that caters to a template space with over 3000 lines which I do not believe were written manually.

sample:

<act:definitionName>composite-action</act:definitionName>
                        <sys:store-protocol>workspace</sys:store-protocol>
                        <rule:ruleType>inbound</rule:ruleType>
                        <cm:name>b3b91r92-1115-11da-bbee-e7056d2bb746</cm:name>
                        <sys:store-identifier>SpacesStore</sys:store-identifier>
                      </view:properties>‍‍‍‍‍‍

The reason I am so interested is because I need to control when the following tag is visible:

                                    <act:parameterValue>
                                      <view:value view:datatype="d:text">Move to Green Zone</view:value>
                                    </act:parameterValue>
‍‍‍‍

Thanks,
C

[kevinr]

The code you want to look at is the following class in the repository project.

org.alfresco.repo.importer.ImporterComponent

[chuck]

Can I ask what would be used to generate such an XML file ? (over 3000 lines)
Is there some alfresco tool that would do this ?

Thanks,
C

[kevinr]

http://wiki.alfresco.com/wiki/Export_and_Import#Export_.26_Import_Command_Line_Tools

[chuck]

thanks for your response, am I right therefore in thinking that my whole ACP template that I import started life as a space which was customised with rules and workflow actions and then exported.

This might explain tags such as:

 <cm:modified>2006-04-03T12:09:37.174+01:00</cm:modified>
‍‍‍

Would my only way to modify the behaviour of certain custom menu option be to import the space, make changes then re-export it as an ACP file for someone else to use ?

I was wondering also if the following uuid tag was optional or whether there was some choice in this being generated:

<sys:node-uuid>dcaed2ab-7ed5-11db-af28-1967418ddf7a</sys:node-uuid>
‍‍‍

Thanks,
C.

[kevinr]

Yes all spaces etc. are just nodes of a certain type, assocations and properties - all of which get exported into the ACP.

I'm not sure what you mean about importing to change a custom menu option.

All of the exported sys: attributes will get regenerated (and effectively ignored) when you import the ACP. Values such as UUID are all generated by the server.

Thanks,

Kevin