Support for parameters in script actions

Description

It's possible to create javascript actions using spring config e.g.

<bean id="runScript" parent="script">
<property name="scriptLocation">
<bean class="org.alfresco.repo.jscript.ClasspathScriptLocation">
<constructor-arg>
<value>alfresco/extension/script/runscript.js</value>
</constructor-arg>
</bean>
</property>
<property name="publicAction">
<value>true</value>
</property>
</bean>

These script actions can be exposed to the user via share-config and action forms. However, unlike Java actions, it’s not possible declare and pass in additional parameters that can be used by the script. This means you have to create a unique script for every variation of the script behaviour and also limits the use to simple actions (you can’t pass in parameters from the action form).

This task is to add the ability to (optionally) pass in parameters as args to script actions via the share action config (share-config-custom.xml) and/or as parameters exposed and captured from the action forms UI. Note, Java actions already support support this.

Environment

None

Testcase ID

None

Activity

Show:
All Replies
April 8, 2015, 2:26 PM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was dhaval.patel_10@yahoo.com] We are not able to pass parameters to Javascript called by Bean.

Is there any provision or chances to do that ?

All Replies
July 30, 2016, 6:39 AM

[This comment has been reassigned to allreplies@alfresco.com as part of the Alfresco cloud migration project. The author of this comment was resplin] This issue was reported against a version of Alfresco Enterprise Edition that is in Limited Support. Alfresco Software will not implement further enhancements or improvements for products or versions in this support state. If this issue is impacting your deployment of Alfresco One Enterprise Edition, please contact support so that we can assist you. Customers with a support contract can request a bug fix in certain cases.

Current releases of Alfresco contain many improvements that address old problems. We are closing old issues so that we can better prioritize our efforts.

If you verify that the issue still exists in the latest release of Alfresco Community Edition, please reopen the issue. If you have any trouble reopening the issue, then leave a comment or email us at community@alfresco.com so that we can assist.

Thank you for collaborating with us on improving Alfresco.

Won't Fix

Assignee

All Replies

Reporter

Mike Farman

Labels

None

Security Severity

None

Sprint Number

None

Documentation required

None

Documentation Impact

None

Resource

None

Triage

None

Release Train

None

Delivery Team

None

Components

Affects versions

Priority

Major