Action Manager Fields

The following fields display on the Template Details panel for an Activity Update under Action Manager:

  • Source: The source selected when the template was created. This cannot be changed.
  • Action: The action selected when the template was created. This cannot be changed.
  • Description: The description entered when the template was created. You may change this if desired.
  • Activity Field: Select the field from the drop-down list that the activity update will populate.

NOTE: The Activity Field drop-down list will differ depending on the source you have chosen for the activity update.

  • Asset Type: Select the Asset Type to determine which GIS asset attributes will populate the field. The Asset Type selected must be a polygon layer.
  • Asset Field: Select the Asset Field to determine which GIS asset attributes will populate the field.

NOTE: The Asset Field drop-down list is filtered by the Activity Field chosen.

  • Exact Value: Enter the Exact Value if desired instead of selecting an Asset Type and Asset Field.
  • Events: The events section displays any events associated with the action template.

The following fields display on the Event Details panel for an Activity Update under Action Manager:

  • Event: The event selected when the event was created. This cannot be changed.
  • Description: The description entered when the template was created. You may change this if desired.
  • Trigger Field: Select a field that will trigger the activity update.
  • Trigger Type: Select the type of trigger. This defines how often the activity update is triggered, or how the Trigger Field relates to the Trigger Value if those fields are populated.
  • Trigger Value: Define the value in relation to the Trigger Field and Trigger Type.
  • Action Templates: Select the Action Template to associate the Action Event to.
  • Apply to All Templates: Select to apply the event to all the work activity templates.
  • [Request, Work Order, Inspection, or Case] Templates: Select specific work activity templates to apply the event to.

The following fields display on the Template Details panel for a Web Hook under Action Manager on the Simple tab:

  • Source: The source selected when the template was created. This cannot be changed.
  • Action: The action selected when the template was created. This cannot be changed.
  • Description: The description entered when the template was created. You may change this if desired.
  • Url: Enter the Url the information will be sent to. Web hooks allow keywords in the destination URL.
  • Method: Select the protocol that is used to make the call to the URL defined.
  • Urgent: Select the check box to send the web hook as soon as the event is triggered. Do not select Urgent unless the web hook is time-sensitive. Typically, web hooks are sent to the message queue service where they are processed at a preset interval.
  • Credential User: Enter the Credential User if the URL the webhook is being sent to uses basic authentication.
  • Credential Password: Enter the Credential Password if the URL the webhook is being sent to uses basic authentication.

NOTE: Cityworks, ArcGIS, and other APIs often use securely generated tokens instead of basic authentication for client connections.

  • Parameter Name: Enter a Parameter Name. The default parameter name is data.
  • Sample Data: The Sample Data box shows a sample of the information that will be sent.
  • Events: The Events section displays any events associated with the action template.

The following fields display on the Template Details panel for a Web Hook under Action Manager on the Custom tab:

  • Enabled: Select the check box to use the Custom tab. If this is not selected, the web hook will default to the Simple tab.
  • Epoch Dates: Select if you'd like the date expressed in milliseconds since January 1, 1970. Epoch Dates are use to work specifically with Esri's epoch date model.
  • Referer: A referer can be used to pass the location that a user is coming from. This field is optional and could be used with integrations to other systems, if needed.
  • Header: Enter a header for the custom web hook.
  • Template: Enter the custom web hook. The Template field is what will contain the body of the HTTP request sent by a web hook.
  • Events: The Events section displays any events associated with the action template.

The following fields display on the Event Details panel for a Web Hook under Action Manager:

  • Event: The event selected when the event was created. This cannot be changed.
  • Description: The description entered when the event was created. You may change this if desired.
  • Trigger Field: Select a field that will trigger the web hook.
  • Trigger Type: Select the type of trigger. This defines how often the web hook is triggered, or how the Trigger Field relates to the Trigger Value if those fields are populated.
  • Trigger Value: Define the value, in relation to the Trigger Field and Trigger Type.
  • Action Templates: Select the Action Template to associate the Action Event to.
  • Apply to All Templates: Select to apply the event to all the work activity template.
  • [Request, Work Order, Inspection, or Case] Templates: Select specific work activity templates to apply the event to.