06-17-2016 12:01 PM
09-21-2016 02:45 PM
This is in "config/alfresco/messages/notification-service.properties" in a property called "assigned-task". You can override it with your own property value.
The best way to do that is to create an AMP using the Alfresco Maven SDK. You don't need an "all in one" AMP for this, a "repository" tier AMP will do.
Once you create the AMP, create a new folder called "messages" under src/main/amp/config/alfresco/module/[your amp name].
In the messages folder create a new properties file. I'd name it something similar to your domain, like if your domain is www.someco.com you could name it someco.properties.
In it, add this:
assigned-task=Whatever You Want
Now make a copy of the file for every locale you need to support. If that's just English, call it someco_en.properties.
Now go into src/main/amp/config/alfresco/module/[your amp name]/context and edit service-context.xml. Add this:
<bean id="${project.artifactId}-dictionaryBootstrap" parent="dictionaryModelBootstrap" depends-on="dictionaryBootstrap">
<property name="labels">
<list>
<value>alfresco/module/${project.artifactId}/messages/someco</value>
</list>
</property>
</bean>
Where "someco" matches the name you gave your properties file, without the ".properties" extension.
Now go back to the root of your directory and do ./run.sh to make sure the test install of Alfresco starts up with your change.
If it does, do a mvn clean install and you should have an AMP sitting in your ./target directory that you can deploy to your server.
09-21-2016 02:45 PM
This is in "config/alfresco/messages/notification-service.properties" in a property called "assigned-task". You can override it with your own property value.
The best way to do that is to create an AMP using the Alfresco Maven SDK. You don't need an "all in one" AMP for this, a "repository" tier AMP will do.
Once you create the AMP, create a new folder called "messages" under src/main/amp/config/alfresco/module/[your amp name].
In the messages folder create a new properties file. I'd name it something similar to your domain, like if your domain is www.someco.com you could name it someco.properties.
In it, add this:
assigned-task=Whatever You Want
Now make a copy of the file for every locale you need to support. If that's just English, call it someco_en.properties.
Now go into src/main/amp/config/alfresco/module/[your amp name]/context and edit service-context.xml. Add this:
<bean id="${project.artifactId}-dictionaryBootstrap" parent="dictionaryModelBootstrap" depends-on="dictionaryBootstrap">
<property name="labels">
<list>
<value>alfresco/module/${project.artifactId}/messages/someco</value>
</list>
</property>
</bean>
Where "someco" matches the name you gave your properties file, without the ".properties" extension.
Now go back to the root of your directory and do ./run.sh to make sure the test install of Alfresco starts up with your change.
If it does, do a mvn clean install and you should have an AMP sitting in your ./target directory that you can deploy to your server.
11-04-2016 05:56 PM
I just did it on that version and it works great. Check it out.
Maybe you could share exactly what you did and I can spot what you did wrong.
11-17-2016 05:09 PM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.