Overview

 

Actions are a platform for automating workflows and extending the functionality of InFocus.

Actions can be launched explicitly by the user or called by an in-applet event type or other process (e.g. another Action, InFocus Job, etc.). When run, Actions can include wizard-driven user prompts for input or simply run in the background.

 

Below are some examples of how you could utilize Actions.

 

•Interact with a third-party system. For example, trigger an export to a project information management system whenever a project is created, or pull in information from a web-based time-tracking app.
•Simplify multi-step processes. For example, InFocus comes with a “Refund Retainer” action. Run it, specify who and how much and you’re done. Use one of the many built-in Actions or create your own and then put it on your Dashboard for quick access.
•Add warning prompts for specific business rules. For example, “this time sheet isn’t over 40 hours, are you sure you want to submit it with overtime?”

 

 

Setup

 

Actions are managed via Custom Report (UT>Custom Reports) where you can create, copy, edit and deploy as appropriate.

 

TIP Clearview makes several custom Actions available to you though the InFocus Marketplace .

 

Permissions

 

To begin, you’ll need the following permissions to manage Actions. Permissions are configured through AD>Permissions.

 

Module

Applet

View

Edit

Add

Delete

Utilities

Custom Reports

x

x

x

x

 

 

Managing Actions

 

As stated above, Actions are managed through the Custom Reports applet (UT>Custom Reports). Similar to Reports, Actions can be of type System or Custom.

 

•System - Actions created by Clearview and shipped with InFocus
•Custom - Actions created/installed by your firm

 

Whether system or custom, all Actions are managed by determining who has permission to use them and how the Action should be deployed.

 

Note! As mentioned earlier, Actions (or other processes) can call other Actions. In this case, the called Action does not require permissions or deployment configuration.

 

Permission to Use

 

Access permissions govern which users have the right to run an Action and are granted from the Permissions tab in Custom Reports (UT>Custom Reports>Permissions tab). Whether launched by the user or run in the background, the logged in user must have permission to the Action in order for it to fire.

 

Permissions to an Action can be granted using the steps below:

 

1.Browse to UT>Custom Reports
2.Double-click the Action you wish to manage
3.Select the Permissions tab
4.Grant permissions to the appropriate users/groups
5.Click Save

 

Note! While User Permissions govern who can run the Action, Actions can contain scripting that executes at a level outside access permissions and therefore may not necessarily inherit those access restraints (e.g. the Action may perform commands your user could not otherwise perform). Deploy wisely

 

Deploying Actions

 

Actions can be placed throughout InFocus in any of the following locations:

 

•Module - Listed in the main menu under a specified Module
•Applet - Listed in-applet from the toolbar or called by an event type from the Applet
oToolbar - Listed in-applet on the toolbar
oEvent Type - Automated using an in-applet event (e.g. Action launches when a new Project is created)

 

To deploy an Action,

 

1.Browse to UT>Custom Reports
2.Double-click the Action you wish to manage
3.Select the Modules/Applets tab
4.Deploy the Action as appropriate
oModule (only) - Check to list in the main menu under the selected Module
oApplet - Check to list on the toolbar or to call the Action from the selected Applet using an event type. More on Action Types.
5.Check Reload if the applet should reload after running the Action
6.Optionally re-title the Action for deployment
7.Click Save

 

 

Using Actions

 

Once Actions have been setup, users will simply work with them like any other applet or report in InFocus, in that they will be accessible to launch from their deployed location and/or run when called by the defined event type (etc.).

 

If the Action includes user prompts, they will display when launched in a wizard interface. If the Action includes an output message, the user will see those messages once the Action has completed.

 

Next up: Actions- Developing Actions