As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
No, not yet. Spring Surf does have everything baked into it to handle it … but it is not yet implemented in our webapps.
<br> <userTask id="handleVacationRequest" activiti:formKey="/vacationRequest/approval"<br> name="Handle Vacation Request"><br> <documentation>approveVacation.description</documentation><br> <potentialOwner><br> <resourceAssignmentExpression><br> <formalExpression>management</formalExpression><br> </resourceAssignmentExpression><br> </potentialOwner><br> </userTask><br>
Hi Lim, internatibnalization is not supported at this moment. Are you using your own forms technology? If so, you could probably look up the key before it is displayed.
<br><userTask id="initiateVacationRequest" activiti:formKey="/vacationRequest/create" name="Initiate Vacation Request"><br> <documentation>Vacation request by ${username}</documentation><br>………<br>
Mmm.. if you do a task.getDescription, doesnt it resolve the variables automatically?Internationalisation is not directly on our roadmap (ie first 4-6 months), since we first want to stabilize and build out the engine features before going full speed ahead with the UI's.
<br>approveVacation.description=Vacation request by ${username}<br>
Ah, now I understand your question…. but no, it won't resolve it.It will resolve everything before returning the value from task.getDescription.However, you can use the ExpressionManager class to create an Expression from the value you get back from your messages.properties. That expressio n then needs the execution from your task to be evaluated. The ExpressionManager is normally available on the configuration (but maybe you need to cast).
