Action types
The action type describes the type of event that is triggered (for example, a jump to another report or setting a parameter).
Select the action type from the Type list. Not all types are available for all action modes.
SeeAction modes.
See the 'Examples of Actions' section.
This table shows the available types of action:
Action Type | Description |
---|---|
Jump | Defines a jump to a target report.
See Defining actions. The target report can be the report in which the jump is defined. Such internal jumps can be used to force execution of a report On-load action. SeeOn-load . |
Recalculate report | Recalculates the report. This has the same effect as pressing <F9> when the calculation
of the report is set to Manual. If calculation of the report is set to Automatic,
the Recalculate Report option restores the initial expansion level of hyperblocks.
You can also to specify parameters to be passed. These are handed over immediately
and the report is recalculated.
When used with the Selection Changed action mode the Execution input becomes available. The input can have one of two values: Manual Selection Changes or All Selection Changes. If is selected, the action is executed only when a user selects a value from the list view. If is selected, the action can be executed when the report is printed or exported as part of a report book. Or, if the report is used in a dashboard, the action can be executed by a change of a parameter in another report on the dashboard. |
Select element | Opens the Find Element dialog. The dialog contains a server or client list from which you can select an
element.
You might define a Select element action on each slice dimension in a report. You could then use the Action Result object to pass the selected elements to a variable. In the Inputs field of the Define Action dialog, select the list from which to get the element. To pre-select an element, enter it in the Select Element input. Select the format in which the elements will be displayed in the Find Element dialog (for example, Caption, Unique Name). To display combinations of formats, such as unique name and caption, select . For example, specify U(C) to display unique name and caption, C(A) to display caption and attribute, or A1+A2 to display attributes 1 and 2. The Special Format String option supports the same formats as in hyperblocks. See Editing hyperblock output properties. By default, users can select only individual elements in the Find Element dialog. To enable users to select multiple elements, select the input. In the Find Element dialog, users can enable check boxes to select multiple or single elements, or they can use Ctrl + click or Shift + click to select multiple elements. If a user selects multiple elements are selected, the selection is stored in the variable as multiselect XML. If a users selects a single element, its unique name is stored in the variable. Parameters of the action are applied after the element is passed to the variable. The Select Element action supports the Action Result object. Actions.Result.Text contains the result of the current action. Click and select the variable to which to pass the selected element. Select Actions.Result.Text as the value of the parameter.See XML variables. Note: The select element action supports the optional Refresh input.
SeeSpecifying the refresh behavior of reports in Application Studio WebServices |
Set parameters | Sets the parameters that are assigned to the report. The parameters are passed at
once. This may cause recalculation of the report.
Note: The Set parameters action supports the optional Refresh input
See Specifying the refresh behavior of reports in Application Studio WebServices. Set parameter is also available as a report action. See Define action on a report. When used with the Selection Changed action mode the Execution input becomes available. The input can have one of two values: Manual Selection Changes or All Selection Changes. If is selected, the action is executed only when a user selects a value from the list view. If is selected, the action can be executed when the report is printed or exported as part of a report book. Or, if the report is used in a dashboard, the action can be executed by a change of a parameter in another report on the dashboard. |
Export report |
Exports the report in one of these formats:
See Export formats. When the action is triggered, you can open or save the exported file. |
Print report book | Prints a report book. It has one or two inputs, depending on whether you allow users
to choose which book prints when the action is executed.
To let users select a book to print, click the browse button in the Value field. In the Select Book dialog, click . To specify which book will print, click the browse button in the Value field. In the Select Book dialog, click and select the book to print. The Show print settings input is enabled. To allow users to select which reports to print, specify Yes as the value of the Show Print Settings input. If you select No, users can specify only the print settings when they execute the action. |
Deliver report book | This action is available only as a report action The Deliver report book action has
four default inputs. You can add further inputs to the action.
See Define action on a report. Note: Any further inputs are executed before the default inputs.
|
Open dialog | Opens a specified target report in a new window. It has six inputs:
See these topics: |
Close dialog | Closes a dialog which has been opened by an Open dialog action and, optionally, sets
parameters. Define Close dialog actions in the target report.
Close dialog has one input - Dialog Result. The value of the input can be OK or Cancel. See these topics: |
Application Engine Process | Runs a process created in the Infor BI Application Engine. A process might be designed, for example, to copy one area of an OLAP cube to another
cube, or to perform a mathematical function on two values. All processes that have
been published are available in the Name input of the action. Processes have a number
of parameters, which are inputs of the action. Specify a value for each parameter.
Currently, all processes run synchronously. You can specify that the report is recalculated after a process runs. You can specify an Application Engine Process action on these objects:
Application Engine processes can be complex and take several minutes to run. You can specify that a progress dialog is always displayed. Or you can specify that the dialog is only displayed if an error, warning, or an information event occurs while the process is running. To help you to debug processes, you can display all available messages. To display the progress dialog select Alwaysas the value of the input and select a level for the input. Otherwise the dialog is displayed only if an error occurs. If you select Debug as the level, the progress of the process and all available messages are displayed. For other levels, the dialog displays only the progress unless an event at the specified level occurs. You can specify a formula as the value of the Edit Action dialog. input, and of the input. This enables you to control these inputs from outside theFor the input, the formula must have one of these results:
For the input, the formula must have one of these results:
Note: Formulas for the and are case-insensitive but are not validated. If the formula contains an error the
Error level is applied automatically.
To change the title of the progress dialog, specify a user-defined string or a formula as the value of the input.Optionally, select
to display the time of each event.
Note: In these action modes, the progress dialog is displayed only in the Application Studio
client:
|
Drillback in Infor Ming.le | If Application Studio is running in Infor Ming.le, you can define an action which drills back to the application on which Application Studio is reporting. For example, if you are reporting on an ERP system, clicking a customer name in Application Studio would open a screen relating to that customer in the ERP system. |
Jump to dashboard | Enables jumps from one dashboard displayed in Infor BI Dashboards or Infor BI Dashboards to another. Use it, for example, to jump from a summary dashboard to a detail dashboard.
Specify the unique name of the target dashboard as the Input. Or, specify a variable which contains the unique name. You can create dashboard parameters to pass values from the source report or dashboard to the target dashboard. This can ensure, for example, that the dates, accounts, or currencies etc., selected in the source are automatically selected in the target dashboard when it is loaded. See Dashboard jumps. |
Q&A Query | Launches the Q&A Evolve Query Editor in which you can create or edit a query. The query is stored in a variable.
You specify an existing Q&A Evolve query in the Input query field, which pre populates the query editor with a query definition. The source of
the input query can be a variable, and that variable can be the same as the target
variable.
The Q&A Query action supports the Action Result object. Action Result.Text contains the result of the current action. See Creating a Q&A Query action.
Note: One of the parameters of the Q&A Query action is Alias. We recommend that you use
a variable to specify the database alias.
|
Upload attachment | Uploads an attachment, such as a text file or spreadsheet to the Repository. In OLAP databases you can assign multiple attachments to a single cell. The 'Additional Information' input is optional but you can use it, for example, to explain the purpose of the attached file. The 'Referenced By' input is reserved for future development. |
Delete attachment | Deletes an attachment from the Repository. Specify the unique name of the attachment to delete. You can view the unique name of an attachment in Repository Administration. |
Open attachment | Opens an attachment. |