Re: [rules-users] taskName does not allow special characters

Yes, this is intentional and reason is the task forms. Currently we use a naming convention for them which uses the taskName property ($taskName$-form.ftl). Because forms get persisted (In guvnor repository or your file system/classpath) it's really better if they don't include any spaces (or really special characters as well). HTH On 10/24/12 4:38 PM, eselis wrote: > Hi Tihomir, thanks for your help. I build a new version from GIT repo, and > it works with special characters. > (accents are allowed now) but /TaskName/ does not allow spaces, when I > write a taskName such as "Llamada Al Médico" it is saved as LlamadaAlMédico. > My solution is to replicate the name with spaces in comment field so I can > get it by the property description in TaskSummary. > > Is ok thar a taskname should not have spaces? > > Thanks > > > > -- > View this message in context: http://drools.46999.n3.nabble.com/taskName-does-not-allow-special-charact... > Sent from the Drools: User forum mailing list archive at Nabble.com. > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users