Applies to version 8.3.x; Author: Paweł Snoch
This article describes how Web Parts are displayed on WEBCON BPS 2015 mobile apps. We will focus on tools used for starting workflows and for those used for displaying elements of a workflow. There are certain differences in behavior between the SharePoint and Mobile forms which will also be addressed here.
First on foremost, in order to access processes through the mobile app, the Available via mobile box must be checked in the General tab of the process configuration (bottom right corner). More information about the mobile app can be found here: WEBCON BPS 2015.
Fig. 1 – Making a process available via mobile app.
Once a process has been made available, you will be able to see a collection of active tasks on the mobile app. If you have tasks from multiple processes (or even multiple groups of processes) they will be sorted like so:
Fig. 2 – Tasks sorted by groups and processes
Selecting a process will bring up a screen with your Active tasks in that process. But what if we want to see completed tasks, archived tasks or tasks which we can only monitor via CC? To customize your task preview, you can use the functionality known as Views.
Views on the mobile app
A big advantage of using views is that it also enables a user to start new workflow elements. In addition to this, they can be used to personalize the way existing tasks are displayed.
What we see in a view depends on the contents of the process’ Linked site. There are two ways to go about creating such a site:
In Designer Studio, right clicking a process om the processes tree will display the context menu, one of the options on there is Generate process site. This option is also available from the Tasks menu in the top-left of Designer Studio. Clicking either option will launch the Process site generation wizard, from this wizard we can select the parts that interest us, we can also choose to set this site as the process linked site through the checkbox in the bottom-left.
Fig. 3 – Generating a linked process site.
After the site is generated, its address will be set in the Linked site section.
When creating a site directly in SharePoint, i can be manually connected with a process in studio by going to the linked site settings in the bottom left of the process configuration, and clicking: Change. This will bring up a window containing a tree with all the sites that have WEBCON BPS Config enabled. Select the desired address and confirm the changes.
Fig. 4 – Manually linking a process to a site.
Note: If the process isn’t linked to a site, the mobile app will use the default address found in the Configuration settings (fig 5)
Fig. 5 – Default site address.
Once a process has been made available, we can access its view on the mobile app. When you open the applications tab, you will see a list of process groups, regardless of whether you have any active tasks in any of the processes. Select one of the processes from any of the group.
Fig. 6 – “Applications” tab preview
Fig. 7 – Process interface.
 This panel contains a breakdown of all your active tasks within the process
[1a] All active elements on which you were marked to be notified via CC.
Fig. 8 – CC tasks
[1b] All active elements in which you are are assigned to a task
[1c] The third option will take you to a page containing a list of your subordinates (Company structure is set either globally in System settings -> Global parameters or locally for a process under its Settings tab). Selecting a valid subordinate will display a list of elements to which they are assigned or have some task to fulfill.
Fig. 9 – List of subordinates
 This section contains buttons for starting new tasks.
These buttons correspond to Web Part tiles from the main site and they must be configured to show up here – that procedure has been covered in a previous article, mentioned above. Whether or not tiles are visible here also depends on which page they were added on:
I. First, the site linked with the process is searched for tiles that start workflows.
II. Next, the same search is performed on the subpages of the main site.
III. After these subpages have been searched, other subsites are checked, but only those that have the linked site set as their parent site
Here is a sample scenario:
Fig. 10 – Site hierarchy
(a) The site linked to the process is main_process
(b) The only Web Part that was made available via mobile is Sample element from main page
(c) No Web Parts were found on any of the sub-pages of main_process
(d) Next the subsite: d_prs is searched, starting from the main page then onto the sub-pages; the following tiles are found: Report task, New suggestion, Report important task
(e) Since there was only one sub-page to search, the procedure ends here. The Archive site isn’t a direct child of the main linked.
 The bottom section is dedicated to views of SWE reports.
With the release of the newest version this part of the app is divided into two parts. As for which SWE are included in this the view, the selection procedure is similar to that described in point #2 – most importantly, the Web Part must be made available for the mobile app in its configuration settings.
[3a] The Main section contains Web Parts on the main page of the site that is linked with the process.
[3b] The Additional section contains SWE Web Parts from the sub-pages of the main site, as well as subsites who are children of the site that is linked with the process.
Selecting an individual SWE Web Part will display its mobile version.
It is extremely beneficial to have configured views for the mobile application, and having neatly organized processes improves their transparency on a mobile device – the positioning of SWE Web Parts and tiles for starting workflows on the mobile app depends on the process configuration.