nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

How to add binding to Script task

elygre

We are considering embedding Activiti into an application, where we want to enable the use of the application-specific APIs in Activiti script tasks:

// This is a groovy task
// The object "applicationSpecificApi" is injected into the script binding by us, similar to the object "execution"
def approvedAmount = execution.getVariable("amount");
def approvedBy  = execution.getVariable("user_id");
applicationSpecificApi.authorizeSpending (approvedAmount, approvedBy);
‍‍‍‍‍‍

How do we add such a binding (a reference to either documentation or sample code should suffice)?

Thanks,
Eirik

Find more posts tagged with

Comments

jbarrez

You would have to check how the ScriptTask is implemented. Somewhere in classes below, the task or execution is simply injected in a hashmap of objects that are available.

elygre

For reference, in case other people have the same question. It looks like there are two mechanisms that are more or less accessible.

First, the engine configuration has a list of "ResolverFactory", as shown in the code below (from ProcessEngineConfigurationImpl). By setting your own ResolverFactories, you can inject your own resolver:

protected void initScriptingEngines() {<br>&nbsp;&nbsp; if (resolverFactories==null) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; resolverFactories = new ArrayList<ResolverFactory>();<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; resolverFactories.add(new VariableScopeResolverFactory());<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; resolverFactories.add(new BeansResolverFactory());<br>&nbsp;&nbsp; }<br>&nbsp;&nbsp; if (scriptingEngines==null) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; scriptingEngines = new ScriptingEngines(new ScriptBindingsFactory(resolverFactories));<br>&nbsp;&nbsp; }<br>}

Second, the "BeansResolverFactory" which is inserted by default in the code above, uses "Map<Object, Object> ProcessEngineConfigurationImpl.getBeans()" to look for beans to inject (presumably the same beans that are available in expressions), so you can just set beans to be injected here:

// While creating the engine<br>Map<Object, Object> beans = new HashMap<Object, Object>();<br>beans.put("myservice", new MyService());<br>((ProcessEngineConfigurationImpl)config).setBeans(beans);<br><br>// In a script task<br>myservice.callMyFunction()

We ended up with the second solution, for now; it looks easy enough to change later, if required.