View and manage custom objects

The Filters area appears above the columns of the table, allowing you to search by the Names of custom objects, Type of custom objects, and words in the Description of custom objects.

1.       If the Filters area is not currently displayed, click the down arrow next to Filters.

2.       Enter the information to use for filtering the list:

a.       In the field above the Name column, type all or part of the name of a custom object you want to find. If you know only part of the name, use the wildcard character, * (asterisk). For example, to find custom objects whose names contain the word "Alarm", type *Alarm*.

b.       From the Type list, select the Type of custom object to find: Alarm Rule, Data Rule, Event Rule, Registration Rule, Action, Shoulder Tap, Extended UI Module. To search for custom objects of any type, leave the empty selection. If you are planning to use this custom object in an Expression Rule, you MUST select Action as the Type.

c.       In the Description field, type words or characters that appear in the descriptions of the custom objects you want to see. Again, you can use the wildcard character, * (asterisk) with the characters you type.

3.       After entering the filter criteria, click Filter. The table displays only those custom objects whose Name, Type, and/or Description match your Filter selections.

At any time, if you want to start over, click Clear and enter new Filter criteria.

 

In the Name column of the table, click the name of the custom object you want to see.

The Axeda® Platform locates the information for the custom object and shows the results in the Custom object wizard pages. Use the wizard to add or change the information shown for the selected custom object.

 

Click Create custom object.

The Custom object wizard starts.

 

If a custom object is currently used in a rule or action, the Platform prevents you from deleting it. You must first remove it from the rule or action.

Important: If this custom object is configured in one or more Extended UI Modules, any Extended UI Module defined with that object is not shown in the related Asset dashboards.

1.       Select the right-most check box(es) for the custom object(s) you want to remove. To remove all custom objects shown in this page (not the entire table), select the check box in the table heading.

2.       Click Delete selected custom objects. A message appears prompting you to confirm that you want to permanently remove these objects.

3.       Click OK. The custom objects are removed from the table and the Platform.

 

1.       In the row of buttons below the table, click Logs. The browser prompt for downloading files appears, asking if you want to open or save the file.

2.       If you want to view the log files, select Open. If you want to save them to your computer, select Save and then navigate to the directory where you want to store the log files and save the log archive.

Note: If the customobjects.log file or the Audit log show exceptions caused by security policy violations ("Groovy Sandbox"), refer to Security Policy for Custom Objects.

The log files are stored in an archive (zip), so you need a utility on your computer that can open such a file. For example, if you have WinZip on your computer, the log archive opens. Use the WinZip tools to extract and view the log files.

 

In the row of buttons below the table, click Purge Logs.

All OLD rolling log files (for example, customobjects.log1) are deleted from the Platform. The log file currently in use (customobjects.log) is NOT deleted.

 

In the following example scripts , the lines that differ are highlighted.

Script that uses the "DataValue" interface:

import com.axeda.drm.sdk.data.DataValue

dataItemList?.each(DataValue dv->

    logger.info "Value of $(dv.dataItem.name) => $(dv.asString()?"

}

 

Script that used the deprecated "XmlInfoDataValue" interface

import com.axeda.drm.sdk.data.XmlInfoDataValue

values?.each(XmlInfoDataValue dv->

    logger.info "Value of $(dv.dataItem.name) => $(dv.asString()?"

}