Custom actions (Category: Enterprise actions) enable the Axeda® Platform to do whatever action has been defined in a custom object or in a Java class. When a rule associated with this action type evaluates to true, the Platform calls the custom object or Java class, and, if appropriate, passes in the method and/or defined parameters.
To configure a Custom action in the Configuration application, you first need to create a custom object or a Java class for that action. As long as you have the appropriate license, you can use the Custom Object wizard of the Axeda Configuration application, or you can write a Java class using the Axeda® Connected Product Management Applications SDK. The Custom action class must implement the interface defined in the SDK's ActionContext class (Action interface, com.axeda.drm.sdk.rules). For more information, contact customer support at Axeda Corporation.
Notes:
If you are migrating to a shared environment (that is, the Axeda
hosted environment), each existing custom action can be cut and pasted
into a custom object (with the interface declarations removed). Since
the scripting language is a super-set of Java, all existing Java code
will work as is. The custom actions would then need to be re-configured
manually through the New Action pages.
If you are editing an existing custom action from an earlier version of
Axeda Applications, you will see the old fields in this page. For any
custom action created with version 5.3.1 or later, you will see the lists
from which to select rather than the text fields.
From this page, you can configure custom actions.
1. From the Action list, select the custom object or Java class to use for this custom action. For a new custom action, this is the only selection, so continue to step 3.
Notes:
The Action list contains the names of any custom objects of type Action
that have been created using the Axeda Configuration application. It also
contains the names of any custom actions implemented at your site and
listed in the special configuration file, custom-actions.xml.
In creating a custom action using the
Axeda® Connected Product Management Applications
SDK, programmers at your site need to implement the action interface for
the action type. The action interfaces are included in com.axeda.drm.sdk.rules.Action.
Once the custom actions have been created, programmers need to add them
to the custom-actions.xml configuration file on the Platform. Programmers
should refer to the Axeda® Connected Product Management Applications
SDK documentation for more information.
2. For an existing custom action created with the Axeda® Connected Product Management Applications SDK, type the method name for the Java class and the parameters to pass to the method when the action is executed.
3. When
ready, click Next to configure
the parameters for the custom object or the Java class selected for
this action. For an existing custom action created prior to version 5.3.1,
you can modify the setup
page for the action.
If you click Finish, the action
confirmation page appears. If you click Cancel
and continue canceling, all information configured in this wizard is removed.
o In the Rules module on the Asset dashboard (Axeda® Service application), you can view and enable or disable the rules configured for a specific asset.
o The Audit log module on the Asset dashboard shows a log of activity for the selected asset, including registration, actions run, alarms acknowledged, statuses, usage value setting, and more. Also, if you have privileges to the Administration application, you can search the Audit log for asset, Platform, and user activity.