Relevant for: API testing only
The addin file provides the references for the activity you are defining. The file is in XML format and contains information such as activity names, dependencies, and runtime DLLs.
The addin file should be located in the installation directory under the addins\CustomerAddins\<addin_name> folder, together with the signature file. The addin file must have an .addin extension.
This topic describes the sections that must be included in each addin file.
The basic details about the section, including any of the following attributes:
Details about the location of the activity, including any of the following attributes:
|Activity (sub-element of the Path attribute)||
Additional information about the activity, including any of the following attributes:
Basic details about the addin, including any of the following attributes:
The activity on which the current activity is dependent, including any of the following attributes:
An assembly to import when running the activity.
You can use the assembly, which is the name of an assembly. Use the DLL name without the DLL extension.
To import an addin from another activity, precede the addin name with a colon.For example, :HP.ST.Fwk.DesignerModel imports the DesignerModel addin.
The following example shows the ReportMessageActivitySample.addin file. For multiple activities, use unique Addin files.
<?xml version="1.0" encoding="utf-8"?> <AddIn name = "HP Report Message Activity Sample" author = "John Doe" copyright = "C:\Copyrights\copyright.txt" description = "Extensibility Sample - Report Message Activity" version="1.0"> <Manifest> <!--<Must be unique --> <Identity name = "ReportMessageActivitySample"/> </Manifest> <Runtime> <Import assembly=":HP.ST.Fwk.DesignerModel"/> </Runtime> <Path name = "/ST/Activities"> <!--Misc Activities --> <Activity id = "ReportMessageActivitySample" displayName = "ReportMessageSample" signatureFile = "ReportMessageActivitySample.xml" assembly="ReportMessageActivitySample.dll"/> </Path> </AddIn>