How useful did you find this document?: 
4
Average: 4 (1 vote)

Overview

The ProcessMaker Mobile application allows users to use out-of-the-box templates for processes, such as expense reports, purchase requests, IT requests, help desk requests, access requests, and leave requests; or, users can build their own custom process apps with the open source ProcessMaker process designer. Run workflows seamlessly in a mobile app on cellphones and tablets that use iOS, and the web application on desktop computers. ProcessMaker Mobile allows the user to:

  1. Build: Use your web browser on a desktop computer to log in to your installation of ProcessMaker and create custom process maps, responsive HTML5 forms, and other workflow components. The REST API can be used to design custom interfaces that connect remotely to the ProcessMaker server.
  2. Run: Execute your processes by creating new cases and managing your task inbox from the ProcessMaker mobile app or in the ProcessMaker web application on desktop computers. Fill out forms in both online and off-line mode. Mobile controls, such as Signatures, QR Bar Codes, Image, Audio, Cideo, and Geomap, can be used in the forms.
  3. Report: In the ProcessMaker web application, build custom dashboards and reports for managers and employees to help them better manage their workload.
  4. Optimize: Study performance metrics and use the information to improve your processes on the desktop app.

Minimum Requirements

To install the ProcessMaker mobile app on your iOS device, check whether your device meets the minimum requirements shown in the table below. The ProcessMaker application supports the following configurations on smartphones:

Operating System Screen size
iOS 7.0 or later * (Including the following devices) Any screen size
Iphone v.4 or later
Ipad
Iphone touch

Getting ProcessMaker Mobile from the App Store

Use your iPhone device and go to the main screen. Once there look for the App Store app and open it by tapping on it.

Go to the Search option to look for the ProcessMaker application.

Start typing "ProcessMaker", and the first option that appears is the mobile application, which must be tapped to proceed with the installation. Observe the image below:

Now, it is possible to download the ProcessMaker app by tapping on the GET button.

When the GET button is tapped, a new button will appear on its place: the INSTALL button. Tap on it to start downloading the application onto your device.

The installation may take a few moments (depending on the space left on your device).

Once ready the button will change to an OPEN button. Open the application from here to use it immediately.

ProcessMaker Mobile can also be opened by tapping on the icon that was created on the main screen.

Entering ProcessMaker Mobile

Enter the ProcessMaker Mobile application by tapping the icon that was created the moment the application was installed.

The moment the application is opened, a summary of the application's features will appear. Each of the screens show a brief description of what ProcessMaker can do, like the image below:

The last screen will be a login screen. The screens summarizing ProcessMaker's features will not appear after starting the app for the first time; the login screen will simply appear instead. If you have a ProcessMaker account, then tap on the Login button, otherwise, tap on the Register button.

Note: When updating the ProcessMaker Mobile app, remember that the application depends on the release of the new version of ProcessMaker. Many of the functionalities of the application change with the update of the ProcessMaker Web Edition. Meaning that the mobile app must be used with the latest version of ProcessMaker. We recommend disabling automatic updates to avoid any inconvenience.

If the Register button was clicked, a new window appears where a new account can be created by entering the first name, last name, and business email into the fields displayed. Tap on Continue after filling in the information.

Tap on Login if you already have an account.

Accesing ProcessMaker with a Google Account

Available Version: ProcessMaker Mobile 1.0.3

Users of the ProcessMaker Enterprise Mobile version have the option to sign in with a Google+ account.

The ProcessMaker mobile application can be accessed by using a Google account registered in the device. Take into consideration that this feature is available exclusively for the ProcessMaker Enterprise edition. The user must be registered in ProcessMaker with their Google accounts (in the email of the profile) and that account must also be registered in the device. Create a user in ProcessMaker by going to Admin > Users > New.

Now, access ProcessMaker with a Google account by tapping on the Sign in button as seen in the image below.

When there is an account already configured on the device, then it will go directly to a screen asking the user to allow or deny the Processmaker app certain permissions as seen in the image below. To add another account, tap on the account name and a new screen will appear to add a new account.

This new screen will allow the user to sign in by adding a new account to work with ProcessMaker Mobile.

Enter your email account and tap on the Next button.

Enter your Google account password as seen in the image below and then tap on the Sign in button.

A new smaller screen will pop-up asking if the user wants to save the password, never save it or not save it at the moment. If the account will be always used then it is advisable to tap on the Save Password option.

Once the account is authenticated it will need permissions to access ProcessMaker; tap on the Allow button to give access to ProcessMaker Mobile.

Once the user grants ProcessMaker Mobile the necessary permissions, the application will start synchronizing the app with the account. This might take a few minutes.

Once synchronized, the name of the user will appear in the Case List menu as seen in the image below.

Configuring ProcessMaker Mobile

Configure ProcessMaker Mobile by following the next steps. On the main screen, there is a Settings button to configure the app.

This configuration should be done on each mobile device where the ProcessMaker app will run or will be used. It can be configured to use a workspace in any ProcessMaker 3 server.

To try out the app without installing a ProcessMaker server, the initial screen provides a button to create a new account in the Enterprise Trial Server, and the mobile app will automatically be configured to use that new account.

The same workspace on the Enterprise Trial Server can be used on multiple mobile devices, so it is only necessary to register once.

To create users, modify the process, or create new workspaces, open a web browser on a desktop computer and log in to the ProcessMaker server as an administrator user.

Before starting, the mobile app must be configured to either use a workspace on the ProcessMaker Enterprise Trial Server or a workspace on your own ProcessMaker server. The following screen will appear where the user can configure the settings to use ProcessMaker Mobile.

Tap on the Configure url field to enter the URL of the ProcessMaker server.

For example, the URL will look like http://192.168.1.110:301x or http://pm.example.com.

In the Workspace field, enter the name of the workspace where the user will work.

If using a personal ProcessMaker server, enter the name of the personal workspace; however, the workspace name is usually "workflow".

Finally configure the language (English, Spanish, Portuguese or French). The default language of the app is English.

A language other than English may be chosen depending on the user's location and country.

If a language other than English is chosen, then a message will appear telling the user that the application must be restarted for the changes to take effect. Click on the Restart button to restart ProcessMaker Mobile and change the language.

Also, there is the Clean Cache option where the user can delete the app's cached data.

Note: The Clean Cache option is only available when the user is logged into ProcessMaker Mobile.

After tapping Clean Cache, the app will automatically delete all stored information. A message will be displayed saying that the app's data will be deleted, including stored Dynaforms, files, databases queries, preferences among others. Finish the configuration by clicking on the Save button.

After configuring the application, the login screen will be shown to start a session with the credentials given.

The Case List

This section will explain how end users can interact and use the case list, as well as several other options when running a case on a mobile device. As soon as the user is logged in, the Inbox screen will be shown where all cases that have reached the inbox are shown.

Slide the screen to the right to display a menu where all available options for the app can be found as seen in the image below.

Using the Case List

The user can work with cases directly from the mobile app. The Case List button can be found in the upper left side of the screen; it is the icon that has three horizontal lines.

When this button is tapped a new screen appears on the left side of the screen. Here, the user can see everything happening with their processes. The options in the Case List are the following:

Each of these will be explained in the following sections.

Inbox

The Inbox screen includes the list of all the cases assigned to the user in the desktop version of ProcessMaker. The cases are initially ordered first by their case number and then by the name of the case. Choose a case in the inbox and tap on it.

If the first case was tapped on, it will open so the user can start working on it as in ProcessMaker web edition.

The case statuses are "On time", "At risk" or "Overdue", as seen on the image below.

Unassigned

The Unassigned panel includes all cases that can be claimed by a pool of users assigned to the task. The user will have the power to assign himself/herself to the task. When there are cases in the Unassigned inbox, then anyone can claim the case to work on it. Work on an unassigned case by tapping on it. Once opened, details about the unassigned case, like the status, date, description and more, are shown.

Tap on the Claim this case button to assign the case to yourself and start working on it.

Draft

The Draft inbox includes cases that are being edited or advanced by the user, but have not yet been submitted. Cases are considered to be a draft after the user edits case data by submitting a Dynaform or uploading an input document, or after moving to a subsequent step in the current task.

Continue workinf on a case draft by tapping on it. The Dynaform of that case will immediately appear for the user to continue to work on it.

Participated

The Participated panel includes all the cases that the user has sent or participated in. Click on a case and its information will be displayed on the screen.

When any "Participated" case is tapped on, the information about the case will be displayed, including, the creation date, the last date updated, the owner, the name of the process and more.

New Case

The mobile app allows users to create a new case of a process previously created in the ProcessMaker Web Edition. The New Case list displays all the cases that the user has been designated to work on but has not yet begun. To start a case, tap on the plus sign button located at the top of the screen marked with a red circle.

All available processes for that particular user will be listed, and any of them can be started by tapping on the process.

When a case is tapped, the process will start with the first task or the task that the process is in, as in standard version of ProcessMaker.

Search for a Process

The mobile app allows users to search a process for a process in the list of processes. Search for a process by tapping on the search box located at the top of the screen.

Type the name of a process and the processes list will be filtered based on the search input.

Additional Options

Beside the case list, there are also a few more options to consider. which include:

Logout

Go to the main menu by sliding the screen to the right. Locate the Logout button.

The Logout option will ask the user if they want to logout of the application and eerase all associated information. Tap on OK to quit the ProcessMaker Mobile app or tap on Cancel to go back to the main screen.

Case Notes

Add a case note to a case by tapping on the clock-pencil icon in the bottom right corner of any case.

A window of options will pop-up. From there, select Case notes or tap on Cancel to exit.

When the Cases Notes option is selected, a new window will open where notes can be added.

in the Add a new note section, add any note that applies to the case. Slide the Send Mailbutton to the right to send the mail or not. Finally, click on the Save Note button to store the note added.

History

Observe the history of a case by tapping on the square with a pencil icon in the bottom right corner of any case.

A new window wih the history of the case will be displayed. This includes the name, the person assigned, the status and the date and time of the tasks.

Dynaform Controls on Mobile

When running cases, end users only interact with Dynaforms when inputting data into the form, viewing information sent from other users or viewing information that has been automatically generated by the execution of triggers or JavaScript in the project. To create Dynaforms, ProcessMaker has created an interface that allows users to define the fields of the form, the variables related to the fields, the behavior of the controls, etc. Designers have an extra section in the Enterprise Web Edition of ProcessMaker, where additional controls supported by the mobile application are rendered. When using these controls in both editions while runnign the case, the user has the ability to input data into the form fields in the mobile application and only has the ability to view them in the web edition. Remember that the application uses webkit tooks exclusively for iOS to display the form fields. These forms are not rendered the same way in the web edition (in the preview of the designer or when running cases).

This section lists the web controls supported and unsupported by the application, as well as the controls used exclusively by ProcessMaker mobile. This section will also briefly describe the use of each mobile control.

Supported Dynaform Controls on Mobile

The following elements are supported by the BPMN Designer and the ProcessMaker engine for execution when running cases:

Mobile Controls

The following mobile controls can be created in the web edition and can be used in the mobile application:

GeoMap Control

The Geomap control gives the location of the user. For this field to work correctly, the mobile device must have a Wi-Fi or mobile data connection. Geomap provides real-time directions, interaction with a map and satellite imagery from many countries. When opened, the first pinned location is the user's locale, so when Send Location is tapped, that is the location that will be stored in the field. Create a Variable for this mobile control.

Add a Geomap control by dragging and dropping it into the Dynaform from the Mobile Controls menu.

As soon as the control is added, the Create/Select Variable window will pop up where a variable for the control should be added. After creating the variable, click on the Save button or click on the Cancel button to discard all changes.

Click on the empty space of the control to display its properties on the right side of the screen. As seen in the image below, the first property is Type, which only shows the name of the field, in this case "location". The next property is Variable, which will show the name of the variable created.

Click on the checkbox of the "protected value" property to avoid security issues with the AppData.

The ID and Name properties are filled in by default. The ID property of all the controls is automatically filled in with "ControlTypexxxxxxxxxx", where "xxxxxxxxxx" represents the correlative number of the control inside the designer. The Name property also has the value set by default. When the ID property is changed by the user, the name does not change and keeps its original configuration.

The Label property will help the user change the name of the field; instead of having a random named it can be changed to "Location:" or any other name.

Then, the Hint property shows a small blank box that can be used to provide a fuller explanation of the field or to indicate what values are acceptable for the field.

The last property is Required, which is a checkbox that can be clicked if the field must be filled. A red asterisk will be displayed at the right side of the label to indicate that it is required.

The application uses webkit tools exclusively for iOS to display the form fields, thus the controls are not rendered the same way in the web edition as in the mobile app. This is the rendered control in ProcessMaker Web Edition:

And this is the rendered control in ProcessMaker Mobile:

Finally, the table below shows the property specifications mentioned before.

Property Description
Type location (read only)
Variable

Click on the ... option to select the variable from the list of available variables. Check this section to learn more of how to relate a variable to a control.

The variable used for GeoMap is going to be Float.

Protected value

Click on the checkbox to enable the value protection of the AppData from security issues such as Javascript or HTML injections.

ID

[Required]

Control unique identifier

Name Control name, set by default (but can be edited)
Label The label of the control, which can also be changed.
Hint Used to show help when the field is rendered. It is shown when the pointer of the mouse is hovered over the ? icon.
Required By checking this option, a red asterisk is added in the label to indicate that the field is required. If this field is not filled in, te user will not be able to cubmit the form.

QR Code Control

The ProcessMaker Mobile application has a control called QR Code, which is the name of a kind of matrix code or dimensional code. Create a variable for the QR Code control so it can be stored in the database.

Add a QR Code control by dragging and dropping it into the Dynaform from the Mobile Controls menu.

Immediately after the control is added, the Create/Select Variable window will pop up where a variable for the control should be added. After creating the variable, click on the Save button.

Click on the empty space of the control to display its properties on the right side of the screen. As seen in the image below, the first property is Type, which only shows the name of the field, in this case "location". The next property is Variable, which will show the name of the variable created for the control.

Click on the checkbox of the protected value property to avoid security issues with the AppData.

The ID and Name properties are filled in by default; the ID property of all the controls is and don't need to be changed unless programming code is going to be used.

The Label property allows the user to change the name of the field that appears on the screen. In this case the label was changed to "Scanner Code," but this field can have any other name the user prefers.

Then, the Hint property shows a small blank box that can be used to provide an explanation of the field or to indicate what values are acceptable for the field.

The last property of this control is Required, which is a checkbox that can be clicked if the field must be filled. A red asterisk will be displayed at the right side of the label to indicate that it is required.

When rendered, the control will look like the image below on the web edition.

And this is the rendered control in ProcessMaker Mobile:

The table below shows the property specifications mentioned before:

Property Description
Type location (read only)
Variable

Click on the ... option to select the variable from the list of available variables. Check this section to learn more about how to relate a variable to a control.

The variable type used for the QR Code control is going to be String.

Protected value

Click on the checkbox to enable the value protection of the AppData from security issues such as Javascript or HTML injections.

ID

[Required]

HTML unique identifier.

Name HTML unique identifier, set by default.
Label The name of the control, can be changed.
Hint Used to show help when the dropdown is rendered. It is shown when the pointer of the mouse is hovered over the ? icon.
Required By checking this option, a red asterisk is added to the label to indicate that the field is required. If this field is not filled in by the user, they will not be able to submit the form.

Signature Control

The Signature control captures a signature using a finger touch, which is an e-signature that can be saved and stored. This control might work if a signature authentication is required. ProcessMaker's Signature field has three options: Cancel, Clear and Save.

Click on the empty space of the control to display its properties under the Mobile Controls menu in the left panel as seen in the image below.

The first property is Type, which only shows the name of the field and is not editable. In this case, the type is "signature". the ID property is filled in by default with "ControlTypexxxxxxxxxx" property, where "xxxxxxxxxx" represents the correlative number of the control inside the designer.

The Name property is also set by default. When the value of the Name property is changed, the name of the control field shown in the Dynaform is not changed. When the value of the Label property is changed, the label of the control field shown in the Dynaform is changed.

The label of the field shown on the Dynaform can be changed from the default value in the Label property.

The Hint property shows a small blank box that can be used to provide an explanation of the field or to indicate what values are acceptable for the field.

The last property is Required, which is a checkbox that can be clicked if the field has to be filled.

When rendered, the control will look like the image below on the web edition.

And this is the rendered control in ProcessMaker Mobile:

The table below shows the property specifications mentioned before:

Property Description
Type signature (read only)
ID

[Required]

Control unique identifier

Name Control name, set by default (but can be edited)
Label The label of the control displayed on the Dynaform, can be changed.
Hint Used to show help when the field is rendered. It is shown when the pointer of the mouse is hovered over the ? icon.
Required By checking this option, a red asterisk is added to the label to indicate that the field is required. If this field is not filled in by the user, they will not be able to submit the form.

Image Control

ProcessMaker Mobile possesses an Image control that lets the user take a new picture from the camera of the mobile device and save it for a process. It also allows the a picture to be uploaded from the gallery of the device. Use the control by simply dragging and dropping the control into the form.

Click on any empty space of the control to display its properties under the Mobile Controls tab on the left side of the form.

The first property is Type, which only shows the name of the control, in this case "imageMobile".the ID property is filled in by default with "ControlTypexxxxxxxxxx", where xxxxxxxxxx represents the correlative number of the control inside the designer.

The Name property is also set by default. When the value of the Name property is changed, the name of the control field shown in the Dynaform is not changed.

The label of the field shown on the Dynaform can be changed from the default value in the Label property. In this case, the label was changed to "Image", but it can have any other name when running a real case.

The Hint property shows a small blank box where a description can be written to explain to the user what the control does.

The last property is the Required property, which, if checked, requires the user to fill out the field before continuing the process.

The application uses webkit tools exclusively for iOS to display the form fields. Thus, forms are not rendered in the same way as in the web edition.

And this is the rendered control in ProcessMaker Mobile:

The table below shows the property specifications mentioned before:

Property Description
Type imageMobile (read only)
ID

[Required]

Control unique identifier

Name Control name, set by default (but can be edited)
Label The label of the control displayed on the Dynaform, can be changed.
Hint Used to show help when the field is rendered. It is shown when the pointer of the mouse is hovered over the ? icon.
Required By checking this option, a red asterisk is added to the label to indicate that the field is required. If this field is not filled in by the user, they will not be able to submit the form.

Audio Control

The mobile app has a control called Audio, which can record sound or upload an already recorded sound. Use the control by dragging and dropping it from the Mobile Controls menu to the Dynaform.

Click on the blank space of the control to display its properties, which are shown on the left side of the Dynaform.

The Type property shows the name of the field, which is "audioMobile" in this case, and it is not editable. The "id" property is set by default with "ControlTypexxxxxxxxxx", where "xxxxxxxxx" represents the correlative number of the control inside the designer.

The Name property is also set by default. When the value of the Name is changed, the name of the control field shown in the Dynaform is not changed.

Then, there is the Label property, which allows the user to customize the name of the control displayed on the Dynaform.

The Hint property shows a small blank box where a description can be written. This displays an explantion of what the field does or what to write in it when running a case.

The last property is the Required property, which, if checked, requires the user to fill out the field before continuing the process. Note that when this property is clicked, the process won't go to the next task unless the field is filled in by the user.

The result of the control when rendered in the web edition is shown in the image below:

And this is the rendered control in ProcessMaker Mobile:

The table below shows the property specifications mentioned before:

Property Description
Type audioMobile (read only)
ID

[Required]

Control unique identifier

Name Control name, set by default (but can be edited)
Label The label of the control displayed on the Dynaform, can be changed.
Hint Used to show help when the field is rendered. It is shown when the pointer of the mouse is hovered over the ? icon.
Required By checking this option, a red asterisk is added to the label to indicate that the field is required. If this field is not filled in by the user, they will not be able to submit the form.

Video Control

The ProcessMaker Mobile app has a control called video, which records live video footage. This control can also upload a video file from the gallery or record a new video that can be stored in the mobile application. Drag and drop the control into the form from the Mobile Controls menu, found under the Web Controls panel on the left side of the screen.

Click on the blank space of the control to display its properties on the left side of the screen as seen in the image below.

The type property is the first property displayed in the menu, and cannot be edited. The ID property is filled in by default, and does not need to be changed unless code will be used to further customize the form.

Next is the Name property, which is also filled in by default and should be changed only when programming is involved, as with the ID property.

Then, the Label property allows the user to change the name of the field displayed on the Dynaform.

The Hint property has a small blank box where text can be added to describe the purpose of the control. This will help the end user correctly fill in the control field.

The last property is the "required" property, which adds an asterisk next to the control label that indicates the field must be filled in before moving on into the next step.

When rendered, the control will look like the image below in the web edition.

And this is the rendered control in ProcessMaker Mobile:

The table below shows the property specifications mentioned before:

Property Description
Type videoMobile (read only)
ID

[Required]

HTML unique identifier.

Name HTML unique identifier, set by default.
Label The label of the control displayed on the Dynaform, can be changed.
Hint Used to show help when the field is rendered. It is shown when the pointer of the mouse is hovered over the ? icon.
Required By checking this option, a red asterisk is added to the label to indicate that the field is required. The user must fill in this field before they can submit the Dynaform and continue to the next task.

Using Mobile Controls

Use mobile controls by first creating an example Dynaform in the ProcessMaker Web Edition. This Dynaform will contain all of the available mobile controls to see how they work. Create a new Dynaform with the name "Mobile Controls" and add a description if desired. Then click on the Save and Open button.

When the Dynaform is first opened, it will be empty; therefore, start adding the mobile controls. To start adding mobile controls, go to the Mobile controls tab, under the Web controls tab in the left panel. Add the six controls available for the mobile version to this Dynaform, which are: GeoMap, QR Code, Signature, Image, Audio, and Video. Change the label of the controls to change the name of the field displayed on the Dynaform. The labels of the six controls can be seen on the Dynaform on the right.

Now, this Dynaform must be added as a step in one of the tasks.

Use your mobile device to enter the ProcessMaker Mobile application and login into it.

Inside the mobile application locate the plus sign in the right upper corner to create a case.

Tap on the case that has been created for this example which is "Mobile Example".

The first Dynaform will be rendered and the six mobile controls will be seen on the screen of the device.

Let's start testing the functionality of the controls. The first control is Geomap; tap on the Map button.

The Map Assistant screen will appear where the user's location. If the location is incorrect, tap on the My Position button to reveal the location of the user. If the location is correct, then tap on Send position to add it to the control.

When added the control will look like the image below:

The second control is QR Code. In this example, the QR code leads to ProcessMaker's wiki.

Tap on the Scanner Code button to add a QR code.

ProcessMaker will ask the user for permission to access the camera. Tap on the OK button to continue.

Once the QR code is taken by the camera, it will be recognized and automatically added to the "scannerCode_1" field, as seen in the image below.

Note: When scanning a QR Code make sure the code that is being scanned is legible. There can be cases where opacity and the blurriness of a QR Code can interrupt the process of capturing said code.

The third control in the Dynaform is Signature. Tap on the Signature button to open a new window.

In the new window that opens, create a signature for the case. Click the Cancel button to discard the signature. There are two other buttons at the bottom of the screen; the Reset and Save buttons. The Reset button will erase the previously stored signature and allow the user to create a new one. The Save button stores the signature in the control.

When added the control will look like the image below:

The next control is the Image control; tap on the picture to open the camera.

The user can either choose a picture from the gallery, or take a new one with the camera of the cellphone.

Take a picture with the camera of the device to add it to the control.

Once taken, the control will look like the image below:.

Next is the Audio control. This control allows the user to record sound.

The device will ask if ProcessMaker can have access to the microphone. Click on the OK button.

The user can either select an audio file from the gallery or record a new one. If new audio is recorded, the buttons Record, Stop, Play and Send will be available. Record audio and then play it until your are sure that is the audio wanted, then send the recorded audio.

When added the audio will look like the image below:

Finally, the last control in the form is the Video control. Tap on the video image to record a video.

Choose a video from the gallery or take a new video with the camera

Record the video of your choosing, and when stopped, it will automatically be saved in the "Video" field on the Dynaform.

Once added the video will look like the image below:

Note: Take into consideration that the mobile app is always being updated, and we are working on delivering the best experience. This being said, there might be occasions where the Video control might crash when a video is being saved. When/if the application crashes, report it so we can be notified about the crash.

Click on the Submit button to route the process correctly.

ProcessMaker Web Edition and Mobile Application

ProcessMaker Web Edition and ProcessMaker Mobile are designed to work together, especially when using mobile controls on a Dynaform. The mobile app controls (Geomap, QR Code, Signature, Image, Audio and Video) only input data through the application, and the web edition only renders them in View mode. Take into account that these controls are disabled when a Dynaform that contains them is rendered in the web edition if no data has been input using the application.

When a case is started with the ProcessMaker Mobile app, it can be continued in the web edition of ProcessMaker. For example, start a case from the mobile app.

When the same case is started on a smartphone, all controls will be available to be used.

Running a Case on ProcessMaker Mobile

In this section, an example process will be used to explain how running a case on both ProcessMaker Mobile and the web edition works. If you have run or made a case before, please read this guide.

Process Description: In the guide, a simple process will be used an example to see how the web controls from the ProcessMaker web edition work with the mobile controls for the app. The case will first be run on the mobile device, and then it will be viewed and completed in the web edition of ProcessMaker.

Assuming that ProcessMaker is already installed on your computer (if not, follow this guide in order to install it), log in using an administrator account. To create the following process, which will contain a start event, two tasks and an end event, use the image below as guidance:

Create a Dynaform for the first task with the following characteristics:

Control Type Variable Label Property
Title -None- User Information
Subtitle -None- Details
Text name Name:
Text address Address:
Text phone Phone Number:
Text email Email Address:
Location location Location:
Signature -None- Signature:
Submit -None- Sumbit Information

Create the second Dynaform for the second task with the following characteristics:

Control Type Variable Label Property
Title -None- Final Approval
Subform (Task 1) -None- -None-
Dropdown approval Approve Customer's Information:
Submit -None- Sumbit

After creating both Dynaforms, add them as a Step in the first task and second task correspondingly, also don't forget to add user(s) or group(s). Then, go into your mobile device and tap on the plus sign to create a case.

Look for the example process created in the web edition and tap on it to open it.

Fill in the customer information, and when the Location field reached, tap on it to open a new window.

When the Location field has been tapped, a new screen will appear where the mobile device will ask if ProcessMaker can be allowed to access the location by using the GPS. Tap on Allow to enable your location.

The Map Assistant will show the user's location by pin pointing it as seen in the image below. Once done, tap on the Send position button to store the location in the control.

The map will be shown in the control. Continue filling in the Dynaform by tapping on the Signature control.

Create a signature and then tap on the Save button to add it to the control.

After filling in all the information in the Dynaform, tap on the Submit Information button.

Once the button is tapped, the Assign Task screen will pop up showing the following task and the person assigned to it. Tap on the Continue button to move on.

When the Continue button is tapped, the case will be routed to the next task. Tap on "Ok" to end this procedure.

Now, go to the ProcessMaker web edition and locate the recently routed process. To do so, go to Home > Inbox and double click on the "Mobile Example" process to continue to work on it.

Once opened, the user will be able to use the web edition of ProcessMaker to see the mobile controls in View mode. Note that all the fields filled in the Mobile app have been saved correctly. Note that all the fields filled in from the mobile app have been saved correctly.

After the Dynaform is submitted, the process is over, along with this example.

Uninstalling ProcessMaker Mobile

Uninstall ProcessMaker Mobile from the device by tapping on its icon without letting it go for a few seconds. All applications available to be uninstalled will have a blue cross in the upper left part of their icon.

Tap on the "x" in the top left corner of the ProcessMaker icon and a confirmation screen will appear. Tap on the Delete button to erase ProcessMaker Mobile from your device.