Let's build a simple application in AngularJS to get a ProcessMaker user's case list, using the new ProcessMaker REST API. It is way easier than it sounds, I swear. First and foremost the requirements What you need: ProcessMaker version 2.8 or later A server running Apache or a similar web server. The proper file permissions to create/copy files inside the Apache public directory. What I am using: A centOS server with ProcessMaker 3.0 running. A local Wamp Server installed on Windows 8. All the necessary files are going to be created in the root of mywww Wamp directory. Registering our new application Let's start by registering the new application in our ProcessMaker server, in order to be provided with a OAuth Client ID and a Client Secret ID: Log into your ProcessMaker server: Open the following URL from your browser: Don't forget to use your own ProcessMaker server address and your workspace name. We are going to use this interface to register our external application: Click on "New" Define the following characteristics for your new application and click on "Register Application": - Name: caselister - Description: Example REST application to obtain the list of cases from a user's inbox. - Website: processmaker.com This operation will generate a Client ID Number and a Client Secret ID Number for your application, we are going to use both to access this ProcessMaker server externally. You can display your application details at any time, by selecting it from the list and clicking on "Detail": That's it. You may register as many applications as you need. Adding Some AngularJS Magic If this is your first time using AngularJS, you can check out this amazing free course in Code School, which practically cover all the basics about AngularJS. Creating the app.js file Inside your www root directory - in my case C:\wamp\www - create a new JavaScript file called app.js, with the following source code: This file contains all the necessary JavaScript code to establish the external connection to your ProcessMaker server. Now let me walk you through the code, so you know what it does exactly: Connection parameters In the following lines of code (8 to 17), we define the necessary authentication credentials, which include our ProcessMaker server URL, workspace name, client ID, and client secret. Enter YOUR ProcessMaker server URL and workspace name: YOUR client ID and client secret ID (from your registered application details): And save the file. If you're wondering "what about the username and password?", don't worry we're going to get them from a web form. POST request Here is where all the magic happens. Take a look at the login() function (lines 22 to 43): login() executes a POST request to our ProcessMaker Server, specifically to this address… using the recently defined credentials as parameters, in order to obtain an access token. In case of an error arising during the POST request execution, this function displays an alert box with the error description. Otherwise, executes a GET request to the following address... using the access token as bearer, in order to obtain the authenticated user's inbox cases. Notice we're using the "/cases" end point to obtain a user's list of inbox cases. Each REST endpoint is a web address which provides access to a specific ProcessMaker service, such as getting a list of cases or creating a user. Creating the application home page Create a new file called "index.html" in your Apache www root directory, with the following source code: This file contains all the HTML structure for our application home page. Notice the AngularJS directives and expressions used. Reviewing the code About the content of our <head> tags, you'll notice that all the necessary external and internal resources are loaded: The ProcessMaker favicon, Bootstrap CSS, Angular JS, and of course our app.js file. Additionally, our HTML structure includes: A panel to display all your ProcessMaker Server details: URL, workspace name, client ID, and client secret: A brief form to allow users to enter a valid username and password combination: And a table to display the received case list details: Believe it or not, your application is ready. Continue to the next step to see it in action. Your external application in action So you have your application ready? Great! Let's see how it works. Make sure your Apache server is running and open your application URL address in your favorite browser. In my case, I have my application in my local Apache www root directory, thus I'm just going to access my localhost. You should get something like... Take a look at your ProcessMaker server details: Cool, right? Enter a valid username and password combination, and click on "Get Case List". I'm going to use my admin user credentials. The complete case list of the authenticated user will be displayed in a cool looking table below: Now, what just happened? The application connected to your ProcessMaker server, using the entered user credentials to authenticate and get an access token. Then it used this token to request the complete case list for the authenticated user. Now that you have this application running, you can modify it to create a complete external user interface for your ProcessMaker server. Some extra resources for you Find more detailed information about the new ProcessMaker REST API, including: Available OAuth 2.0 authentication methods, the complete list of end points, and some cool examples; in our Official Documentation Page.
19 May 2026
SAP Master Data Governance is designed to improve data quality, but too often it introduces rigid workflows, slow change cycles, and heavy reliance on IT. The result is bottlenecks that limit agility and prevent business users from taking ownership.
