![]() This method provide more flexibility than the earlier one as there are no restrictions for defining the variables in this method. ![]() The variables added to the map are directly accessible in the Theme. Setting the variables in request scope under attribute WebKeys.VM_VARIABLESĬreate a hook, either Service Pre action or Login Post Action hook and inside your extended pre or post Action class, create a Map object with the key and value of the vm variables you want to insert, and then set that into the attribute under the key WebKeys.VM_VARIABLES. In the above example we are reading the background-url value provided by the user, while configuring the themes.Ģ. #set($background_url = $theme_display.getThemeSetting('background-url')) This file allows you to override and define new Velocity variables. As a best practice, all the custom variables should be defined in the init_custom.vm file. Init.vm file, which is present in the liferay theme, contains all the liferay defined velocity variables. For elaborated list of those, below is the urlĪpart from those variables, if at all we end up needing a custom variable, which define a custom functionality/value as per the specific business need, we can define them in two places. There are number of predefined variables that can be accessed from with in the liferay theme. All you need to do is change the following properties to 1.6 This can be set in build.properties file present in the plugins SDK root directory. As we are building from ant, we have to set the compiler compliance level of ant. To solve this issue the compiler compliance level should be set to 1.6. Remove annotation and build the project using ant. If the implemented class has annotation "override", while building using the ant, it gives compilation error. When creating a model listener hook, you need to implement all of the methods present in the ModelListener interface. So while using liferay 6.1 plugins SDK, if you use annotations for implementing interface methods, though the server JDK is at 1.6, it still complains, resulting in not compiling the class with that annotation. You have classes implementing interface methods, which in Java 1.6 can be annotated with however, in Java 1.5, could only be applied to methods overriding a superclass method. Thus, task assignment and notifications are sent to the same set of users. If the notification does not have tag, then the notification uses the assignment tag specified at the task level. Scripted assignment is present at level.The only way to check whether the script executes perfectly or not is not copy the script and run that script in the Control Panel -> Server Administration -> Scripts console and debug there.When ever there is a script error, workflow engine does not give/throw the exception and swallows the exception silently.Things to be considered while developing the Kaleo workflows. In other words, tag in the does not have a provision for scripted assignment. There is no scripted assignment for notifications separately.Can not send notifications in the terminal state for the roles though it can send the notifications to users specified.Can not have multiple terminal (end) states.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |