Step 7: Define Messages and Colors for the Action Entry Form

The last page of the Actions Wizard is used to define the success and failure messages to be displayed when the action is executed, as well as the colors to use on the action entry form, if applicable.

1.     The Success Message defaults to “Action Completed” and is disabled by default.

      If you want to have a message displayed when the action is completed successfully, edit the message if you wish and place a mark in the Show the Success Message checkbox.

2.  The Failure Message defaults to “Action Failed.” This message is displayed to the end user if the action fails for any reason.

3.  If the end user will not be prompted for any information when the action is executed, proceed to the next step. Otherwise, you have the option to define the background color to be used on the action entry form presented to the user.

      If you want to use the default color, you may skip this step.

      If you want to specify a particular background color, go to the Background Color for Entry Form and:

Click the icon to choose a color from a color palette

Type the hexadecimal code for the desired color in the entry box

In either case, the resulting color will be shown in the sample block to the right.

4.  You can also specify the font color to use on the action entry form, using the same options as are available for the background color.

      A few field rendering controls that may be used on the action entry form are managed by SharePoint. The color you identify here will not be utilized on those controls.

5.  When you are finished, select Finish. You are returned to the Actions Wizard’s Action Selection page. The action is now available for use in a Grid Display or a Calendar Display. If no values are copied from an item, the action can also be executed from the Action Launcher.

NOTE: For all action types, it is important to note that performance may be impacted by the use of lookup columns in action definitions. Each time an action is executed, it has to go out and retrieve all of the possible values, which can take time; the data retrieval occurs when the action is executed. This could have an effect on performance, since it relies on another system’s or product’s ability to provide the data.

As a result, you may want to limit both the number of items returned by a lookup and the number of lookup columns referenced in a single action. CorasWorks recommends that your lookups return no more than 500 items.