My Tools

Article last updated on the 25th of March 2020.


1. Introduction

The My Tools panel in WorkPoint is located in the top right section of a WorkPoint page (see the red box):

The My Tools panel can be outfitted with customized buttons to perform relevant actions on the current page. If working on e.g. a Projects business module which entities refer to individual projects which utilizes some stage model, a button for changing stage of the entity can be set up and put in the My Tools panel for easy access.

In the case from the image above, two buttons are located in the My Tools panel; the Edit, and the Delete buttons. The "All Actions" drop down menu displays all buttons from the My Tools panel, as well as other standard actions, such as creation actions for documents and events, as well as an option to upload documents.

2. Requirements

No license is required for using the My Tools panel in WorkPoint.

3. Configuration

Configuration of the My Tools panel is done from the WorkPoint Administration:

  1. On the WorkPoint solution, click the "Home" button.
  2. Click the cog icon in the bottom of the side panel to access the WorkPoint Administration.
  1. In the left side panel of the WorkPoint Administration, click "My Tools".

This opens the configuration page for the My Tools panel:

   3.1. Creating a button for the My Tools panel

Creating a button for the My Tools panel can be done in the following way:

  1. For "Select instance", select the business module who's entities should contain the button in the My Tools panel. In this case, we are going to add a button for changing the stage of a project. Projects are stored on the "Projects" business module, thus the "Projects" business module is selected.
  2. Select which group to place the button in. Buttons put in the "Actions" group are placed on the panel itself. Alternatively, a new group can be created by clicking the "Add group" button.
  1. Click the "Add button" to add the new button.
  2. The button is located in the selected group. In this case, the "Actions" group was selected.
  3. Provide a name for the button.
  4. Select an icon for the button. WorkPoint provides a set of default icons for you to use. Alternatively, a link to an image can be inserted and used.
  5. For "Type" select "Open wizard". Alternatives are:
    • New business module entity
    • Customized action
    • New item on the root site
    • New item on the parent site
    • New item on project sites
    • Current item action
    • Link (Link can be used simply to navigate to other locations based on the entered URL. The URL can include internal WorkPoint fields using brackets. This means that using the URL "https:\\[wpProjectID]" would navigate the user to another system, using the Project ID as a parameter to locate a specific site in the other system. Assuming the Project IDs for a project is the same in WorkPoint and the other system, this makes integration between the two systems quick and easy.
    • Manual Trigger (e.g. for executing an action from Action Management)
    • Toggle favorite
    • Toggle follow
  6. Select the name of the wizard to open. Wizards can be created using the Wizard configurator. Follow this link for more information.
  7. To save the button, click the "Save" button.

   3.2. Clearing the WorkPoint 365 browser cache

In order to use any buttons or groups created for the My Tools panel, the WorkPoint 365 browser cache needs to be cleared.

Clearing the WorkPoint 365 browser cache can be done in the following way:

  1. Click the "Home" button of the solution.
  1. In the bottom of the side panel, click "Need help?".
  2. Click "Clear WorkPoint 365 browser cache".

The button created in pt. 3.1 can now be used on sites containing the button:

   3.3. Using Customized Actions

It is possible, both in the Modern UI and Classic UI versions of WorkPoint, to use Customized Actions, which run custom JavaScripts.

Note that it is not possible to run JavaScripts for Classic UI in Modern UI due to elevated security measures.

The following is an example of a customized action using a JavaScript.

The following JavaScript is used for this example:

var apiPackage = arguments[0];

var entity = apiPackage.entity;
var sharePointContext = apiPackage.sharePointContext;
var workPointContext = apiPackage.workPointContext;

// The base Url to go to
var newFormUrl = workPointContext.solutionAbsoluteUrl + "/Lists/Opgaver/NewForm.aspx?selectedid=" +;

// Add the redirect Url
newFormUrl = newFormUrl + "&Source=" + encodeURIComponent(window.location.href);

// Go to the new form
window.location.href = newFormUrl;

Using the provided api package, which is accessible with the "var apiPackage = arguments[0];" line, the following data can be extracted from WorkPoint, using JavaScript:

  entity: { // Denne property eksisterer kun hvis man er på en entitets side
    id: 2, // Denne entitets id
    listId: "4c0799f5-8fec-4715-ae59-b15d5c4f40af", // This entity's business module list id
    title: "Honda", // This entity's title
    webRelativeUrl: "/sites/mgudevapp2/Company2", // This entity's relative URL, eg.: "/sites/Project1"
    effectiveBasePermissions: { // The current user's permissions on this entity
      High: "2147483647",
      Low: "4294967295"
    parentId: 2 // Same as "id" but for the parent entity, if one exists
    parentListId: "4c0799f5-8fec-4715-ae59-b15d5c4f40af" // Same as "listID" but for the parent for this entity if one exists
  sharePointContext: {
    web: {
      absoluteUrl: "",
      relativeUrl: "/sites/mgudevapp2/Company2"
    site: {
      absoluteUrl: "",
      relativeUrl: "/sites/mgudevapp2"
  workPointContext: {
    solutionAbsoluteUrl: "", // Absolute path to WorkPoint solution root, e.g.: "https://minlø",
    solutionRelativeUrl: "/sites/mgudevapp2", // Relative path to WorkPoint root, eg.: "/sites/workpoint"
    appLaunchUrl: "https://localhost:44300", // URL for starting Wizards
    appWebFullUrl: "" // The full app web URL for WorkPoint

Please note that

  • "webRelativeUrl" only exists if the entity has a site.
  • "parentId" only exists if the entity has a parent.
  • "parentListId" only exists if the entity has a parent.

4. End user guide

Click here to go to the end user guide article for My Tools.

Have more questions? Submit a request