Documentation

Introduction

This page will answer any questions you have about Developer Actions.  The Frequently Asked Questions about Developer Actions are displayed in the box below, click on the one that you want to know the answer to.
What Are Developer Actions?
Developer actions are pieces of functionality that are embeddable in a web page.  These are typically coded at the request of the client, but several are available depending on the environment that your site is run in. return to top
How Do I Add a Developer Action to a Page?

Step 1 - Code the Action

The action must first be coded by the developer, if it is not provided in your site package.  Check with your support representative for quotes.

 

Step 2 - Click Developer Actions

Edit the page you'd like the action to display on.  On the right-hand sidebar column, click on "Developer Actions."  This will add a new developer action group to the bottom of the page and display the form to add a developer action.

 

Finish - Select Your Dev Action

Fill in the details of the action.  Fill in a title, the FuseAction name (a short name that tells Hilltop which action to use; it will be in the form "Circuit.ActionName"), and any optional attributes and FAVs.  Attributes and FAVs are specially-encoded strings that can pass optional variables to the action.  These are URL-formatted; e.g., Key1=Value1&Key2=Value2.  Submit the form.

The developer action will now display on the page.

return to top
What Developer Actions Come Standard with a Site?

All Hilltop and Frontrunner sites comes with these developer actions:

  • Photo Gallery List.  This displays information on any child pages that have image groups attached, including a thumbnail of the most recently added image and a snippet of the first text block displayed on the page.
  • Subscribe Form.  A custom subscribe form.  This action is functional but obsolete; use FormBuilder instead.
  • Unsubscribe Form.  A custom unsubscribe form.  This action is functional but obsolete; use FormBuilder instead.
  • Custom Search Form.  This is a custom, database-driven search form.

Senate Hilltop sites come with these developer actions in addition to the ones mentioned above:

  • Google Search.  This is a GSA-powered, page-driven Google search form.  Contact your SAA representative if you'd like to have access to your GSA account to manage your Google index results.
  • Voting Record.  This is an SAA-maintained tag that provides a navigatable voting record for a senator.
  • THOMAS Sponsored/Co-sponsored Legislation.  This is an iframe that displays sponsored and/or co-sponsored legislation from the THOMAS website on a senator.
  • Federal Business Opportunities.  This is an SAA-maintained tag displaying government assistance programs for businesses.
  • Grants.  This is an SAA-maintained tag displaying grant information.
  • Financial Aid.  This is an SAA-maintained tag displaying financial aid information for students.
  • Flag Request Form.  This is a specially-coded form for handling constituent requests for flags from congress.
  • SRC Radio Files.  This displays an archive of sound files from SRC by a senator.  This action is functional but obsolete.
  • SRC Video Files.  This displays an archive of video files from SRC by a senator.This action is functional but obsolete.

FrontRunner sites come with the actions first listed as well as the one below:

  • Contribute Form.  This is a custom contribute form.  This action is functional but obsolete; use FormBuilder instead.
return to top
Can Developer Actions Be Used for Custom Forms?
Yes.  However, it is recommended that forms be built in FormBuilder, as any form information submitted in a FormBuilder form is stored in the site database and cannot be lost.  Use a custom form if the form you wish to build does not conform to the UniForm style, if it must be printable, or if the form redirects to an external vendor's website. return to top