Below is an overview of the specific properties of the action object (JSON). There are many more specific properties configurable for almost all types of actions, that is described further on in the documentation.

This action can be used to open an (external) URL. If the button belongs to a grid, a separate URL is opened for each selected row.

You can set the following properties here:

• url: Indicates which URL should be opened.
  You can use in the URL all fields of the linked item as variables (i.e. by using {fieldName}) as well as following default variables:
  {itemTitle}: The title/name of the linked item.
  {itemId}: The ID of the linked item.
  {entityType}: The entity type of the linked item.
  {environment}: The published environment of the linked item (invisible, dev, test, acceptance or live).
  An example url would be: https://domain.com/{itemId}/?color={itemColor}
• openIn: Controls how the URL should be opened. By default, window.open is used, which in most cases opens a new tab in the browser. If this option is set to kendoWindow, a popup from Kendo will be opened containing an iframe that loads the appropriate URL.
• windowWidth: Allows the width of the popup to be set. This should be a string with for example 600px or 90%.
• windowHeight: Allows you to set the height of the popup. This should be a string with, for example, 600px or 90%.

This is intended for grids. This opens only 1 URL for all selected items at once. All selected values are then passed comma separated to the URL, when variables are filled in for it, such as {selected_subaccountId}.

Furthermore, the same options are available as with the openUrl action.

Allows you to execute a query in the database to which Wiser is linked. In that query, you can use all the fields of the linked item as variables. You do this by using the field name in the query encapsulated by brackets, for example {fieldname}. In addition, the following fixed variables can also be used:

• {itemTitle}: The title/name of the linked item.
• {itemId}: The ID of the linked item.
• {entityType}: The entity type of the linked item.
• {environment}: The published environment of the linked item (invisible, dev, test, acceptance or live).
• For a grid which shows links between items you can also use: {selected_link_Id}

You insert the query to be executed in the wiser_query table. You specify its ID in the action object as parameter 'queryId'. Alternatively, you can fill in the query in the wiser_entityproperty table in the column action_query.

If you make sure that the last query returns a result with a column called itemId, then you can use the action openWindow to open that item in a popup afterward. For example, you can then enter a query that retrieves the id of a particular item, or you can have a query that adds a new item and then run this query in the end to retrieve the newest id: SELECT LAST_INSERT_ID() AS itemId;

If fields from a link also need to be shown (from the table wiser_itemlinkdetail), then you should also make sure that your query returns the ID of that link last in a column linkId.

If you want to use the result of a query to open a specific URL in a follow-up action of type OpenUrl you must have a column called urlPart and use {urlPart} as a replacement in the URL.

It is also possible to show an error message to the user, which you return from the query. If you want to do this, make sure that your query returns the column success with value 0 and the column message containing the message to be shown to the user.

Example action object JSON and example query:

{
    "type": "executeQuery",
    "queryId": 8
}

Example Query:

SELECT 
    i.id AS itemId,
    il.id AS linkId,
    IF(il.id IS NULL,0,1) AS success,
    'This is an error message for item if nothing is found' AS message
FROM wiser_item i
LEFT JOIN wiser_itemlink il ON il.item_id=i.id AND il.type=100
WHERE i.title='{name_from_parameter}';

INSERT INTO custom_table (id,color) VALUES ({itemId},'{color_from_parameter}');

This can only be used for action buttons in grids. With normal executeQuery, the corresponding query is executed separately for each selected row in the grid. With executeQueryOnce, the query is executed only once for all selected rows at once. The selected values are given comma separated.

Allows you to open a popup within the module containing the details of a specific item. The item that should be opened can be specified with the property 'itemId' and the link information can be added with the property 'linkId'. These values (itemId and linkId) can also be determined using a query provided it is executed using an 'executeQuery' action just before the 'openWindow' action.

Example JSON:

{
    "type": "openWindow",
    "itemId": 25,
    "linkId": 10
}

Allows you to generate a text file based on a query. For example, to generate an XML or CSV file from a stored procedure which is then offered for download.

The following options are available:

queryId: the query from wiser_query to be executed. Note that the result set from this query must always contain 1 row containing 2 columns. The first named 'result' and containing the text to be downloaded and the 2nd column named 'filename' and containing the file name for example generated.

Example JSON:

{
    "type": "generateTextFile",
    "queryId": 8
}

Allows you to refresh the currently opened item, all data is retrieved and the user interface rebuilt in the process.

This action refreshes all opened windows (within the same module). This includes the treeview or main grid, depending on the type of module opened.

Note: This functionality only works for action buttons in a grid's toolbar!

Allows the user to move an item link so that it is linked to another item (also known as 'rebooking'). This only works if the ID of the current link is known in the grid. This ID must then be in the grid's data in a column named linkId or link_id. If this column cannot be found, the user will receive an error message. The ID of the new item must be entered by the user in a popup.

Allows calling an API. To do this enter an ID from the table wiser_api_connection in the property apiConnectionId. More information on populating that table can be found here: Connecting to external APIs TODO add link.

Allows to send a message to a logged-in user by pusher provided there is a subscription linked to this external tool. It is possible to set a channel and any additional information. By default, the channel 'agendering' is used. It is originally intended to send a notification to the user when a new agendering TODO (vertalen) is added.

There must always be a pusherUserId, this can be done by filling a fixed ID in the options, or by using a userParameter in which a user can be chosen.

The following settings are available:

• channel: Optional: The channel the message should be sent to.
• pusherUserId: Optional: The ID of the user that should receive the message. This can also be done via a userParameter, which must then have pusherUserId as the name.
• EventData: Any extra data that should be sent with the message. This will only be used if programmed for the channel. At the time of writing, nothing has been created for this.

Example settings:

{
    "text": "pusher test",
    "icon": "notification",
    "style": "width: 400px",
    "actions": [
        {
            "type": "pusher",
            "channel": "calendar",
            "eventData": { "message": "This is a test" },
            "userParameters": [
                {
                    "name": "userId",
                    "question": "choose a receiver",
                    "fieldType": "combobox",
                    "dataSource": "wiserUsers"
                }
            ]
        }
    ]
}

If you want to run your own javascript, you can add an action of this type. This will prevent the user from getting the message that the button is not set up properly. You then have to make sure that you enter your own working javascript in the custom_script column of the table wiser_entityproprty.

When this option is used, the data selector functionality from the GCL is used to generate a file (HTML/PDF). The user is then first shown a preview of this, and then it can be sent by email. Variables {selected_link_id} and {selected_id} contain comma separated of the ids of the selected items when generateFile is used from a grid.

You can enter the following properties to set up the generation of the file:

After generating the file, you also have the option of sending an e-mail with the generated file as an attachment. You will then get a popup with all the fields for sending an e-mail, for example recipient and subject. These fields can also be prefilled automatically with a query. To do this, you can fill the option emailDataQueryId with an ID of a query in the table wiser_query. That query should then return a result with the columns below:

• senderName
• senderEmail
• receiverName
• receiverEmail
• cc
• bcc
• subject
• body
• attachmentFileName

In that query, you can also use variables. The variables you can use are all the values of the userParameters and the following fixed variables:

• itemId: The ID of the opened item.
• itemLinkId: The ID of a link. For example, if the item in question was opened via a sub-entities grid, that is the ID of that link.
• itemTitle: The title of the opened item.
• encryptedId: The encrypted ID of the opened item.
• environment: The published environment of the opened item.
• entityType: The name of the entity of the opened item.
• userId: The ID of the user logged into Wiser.
• username: The name of the logged-in user in Wiser.
• userEmailAddress: The email address of the logged-in user. This is the email address from the email address field of the corresponding WiserUser item.
• userType: The type of the logged-in user. This is the value from the usertype column of the easy_users table in Wiser's database.

The values the query then returns for these columns are populated in the corresponding fields for sending the email.

Sample query:

SELECT
    'Companyname' AS senderName,
    '[email protected]' AS senderEmail,
    'Bill Gates' AS receiverName,
    '[email protected]' AS receiverEmail,
    '[email protected]' AS cc,
    '[email protected]' AS bcc,
    'This is a test - {fieldname} - {itemId} - {itemTitle}' AS subject,
    '<p>Dear Mr/Mrs,</p><p>This is a test</p>' AS body,
    'Attachment_{itemId}.pdf' AS attachmentFileName;

This action opens a confirm dialog. If the user selects to continue the action will be continued. If the user selects to cancel the action will be aborted.

You can set the following properties here:

• title: The title of the confirm dialog. If none is entered the default "Doorgaan" will be used.
• text: The text of the confirm dialog. If none is entered the default "Wilt u doorgaan met de actie?" will be used.

Use this action to merge PDF files of various sources and offer the merged file as a single download.

You can use this function in a stand-alone button or in a grid and select lines of files you want to merge. If you use this in a grid, the columns encrypted_id and entity_type must be available in the grid.

Options you can set for this action:

The following describes which properties can be set for a UserParameter for an action. Multiple parameters can be set per action.

For number fields, you can also use all the options of that field type.

For parameters of type comboBox, dropDownList and multiSelect, you can use the following additional options:

For grid type parameters, you can use the following additional options:

For parameters of type fileUpload, you can use the following additional options:

{
    "text": "Test button",
    "icon": "sln",
    "actions": [
        {
            "type": "executeQuery",
            "queryId": 2,
            "userParameters": [
                {
                    "name": "invoicenumber",
                    "question": "What invoicedate do you want?",
                    "fieldType": "datetime",
                    "defaultValue": "NOW()"
                },
                {
                    "name": "user",
                    "question": "CHoose a user",
                    "fieldType": "combobox",
                    "dataSource": "wiserUsers",
                    "userTypes": ["FinanceUser"]
                },
                {
                    "name": "selected_id",
                    "question": "Select an item from the grid",
                    "fieldType": "grid",
                    "customQuery": true,
                    "queryId": 54,
                    "countQueryId": 55 
                }
            ]
        },
        {
            "type": "openWindow",
            "itemId": "{itemId}"
        },
        {
            "type": "openUrl",
            "url": "https://url.com/?id={itemId}&title={itemTitle}&entityType={entityType}"
        },
        {
            "type": "generateFile",
            "dataSelectorId": 17,
            "contentPropertyName": "html_template",
            "contentItemId": 959335,
            "itemId": "{itemId}",
            "userParameters": [
                {
                    "name": "client",
                    "question": "Select client",
                    "fieldType": "combobox",
                    "dataTextField": "text",
                    "dataValueField": "id",
                    "queryId": 12,
                    "value": 5561
                }
            ]
        }
    ]
}