Difference between revisions of "Extend automation 6.0"
From OpenKM Documentation
| Line 17: | Line 17: | ||
* Values set at validator form are stored to String params[]. | * Values set at validator form are stored to String params[]. | ||
| − | {{Note|Refer to AutomationUtils class to get variables | + | {{Note|Refer to AutomationUtils class to get variables. Take a look at the latest doxygen class reference at [[Developer_Guide]].}} |
<source lang="java"> | <source lang="java"> | ||
Revision as of 20:13, 1 November 2012
Refer to Enable automation section to know how enable automation. By default automation is not enabled.
Refer to Automation section to configure automation rules in your OpenKM and get full explanation of available validators and actions.
Create a new validator
Any validator should implements interface Validation:
public interface Validation {
public static final String METHOD = "isValid";
boolean isValid(HashMap<String, Object> env, Object... params);
}
- At HashMap<String, Object> env are stored element values map.
- Values set at validator form are stored to String params[].
 |
Refer to AutomationUtils class to get variables. Take a look at the latest doxygen class reference at Developer_Guide. |
public class PathContains implements Validation {
private static Logger log = LoggerFactory.getLogger(PathContains.class);
@Override
public boolean isValid(HashMap<String, Object> env, Object... params) {
String path = AutomationUtils.getString(0, params);
String parentPath = AutomationUtils.getParentPath(env);
try {
if (parentPath.startsWith(path)) {
return true;
} else {
return false;
}
} catch (Exception e) {
log.error(e.getMessage(), e);
}
return false;
}
}
