Hardcoded Event (ACS)

Hardcoded Event SOAP Templates holds the Simple Object Access Protocol (SOAP) templates for device event notifications. A template can use the placeholders ${deviceId}, ${serialNumber}, and ${event}. One template is active.

Where to find parameter descriptions: Open Create Template or Edit. Each field has a hint under the input. The Fields section below also explains each field.

When to use it

Use Hardcoded Event to manage the SOAP templates for hardcoded event generation in ACS. Each template has a unique key, a header flag, and XML content. The page sorts templates by key in alphabetical order. The XML editor uses syntax highlighting.

Before you start

  • Open the ACS dashboard and select Hardcoded Event.

  • If you have a read-only role, you can run a dry-run and export.

  • A read-only role cannot apply an import or change templates.

Fields

Field Type Required Validation

Template Key

String

Yes

Must be unique across all templates

Has SOAP Header

Boolean

No

Marks if the SOAP template has a header section

Template XML

String (XML)

Yes

Must be well-formed XML. The page checks it before save.

Find a template

  1. Enter text in the search field.

The search checks the key and the XML content. Each template shows its Template Key.

View a template

  1. Click a template row.

  2. Read the key and the full XML content in the view dialog.

The dialog shows the XML with syntax highlighting.

Add a template

  1. Select Create Template.

  2. Enter the Template Key. The key must be unique.

  3. Enter the Template XML. The XML must be valid.

  4. Select Create.

The page checks the basic structure of the XML.

Change a template

  1. Open the template view dialog.

  2. Select Edit.

  3. Change the template key, the header flag, or the XML.

  4. Save the template.

Use the view dialog to check the XML format before you edit.

Delete a template

  1. Open the template view dialog, or use the delete button on the row.

  2. Confirm the deletion in the dialog.

You cannot restore a deleted template.

Export templates

  1. Select Export.

Expected result: The browser downloads a .zip archive with all template definitions. Export all templates before bulk changes to keep a backup.

Import with dry-run

  1. Select Import.

  2. Upload a .zip file.

  3. Read the dry-run summary and the change list.

  4. If the dry-run shows warnings, select Allow import with warnings.

  5. Apply the import.

Expected result: The list refreshes.

A dry-run is required before you apply an import. The import replaces existing templates with the same keys and adds new templates.

Troubleshooting

XML validation fails

The XML is not well-formed. Fix the XML to follow the expected schema.

Duplicate template key

The key already exists. Enter a new key.

Import blocked by errors

The file has errors. Fix the reported errors in the XML file and import again.

Related pages