Capriza FAQs

To begin the Zapp building process, visit the Capriza Dashboard and click "New Zapp."

Capriza proxy

Capriza will then prompt you tochoose from one of our Zapp Templates or begin with aBasic Zapp (either with a Sign in page or an entirely blank Zapp).

Once you make your selection, Capriza will prompt you to enter details about your Zapp.

Required information includes:

Title: This is what you will use to identify the Zapp on your device as well as in the Capriza Dashboard.

Description: Provide a description of the workflow that this Zapp represents (e.g. Purchase Order Approvals).

Web Address: Point the Capriza Designer to your target application by providing the web address.

The advanced section includes several settings you may enable if required:

Multiple languages : For use cases where the source application may appear in several languages.

Capriza Proxy:For rare cases where the default setup causes connectivity issues.

User Agent:Allows you to choose an alternative user agent for applications that may have difficulty running in Firefox.

Click "Go" to launch the Capriza Designer and begin building your Zapp.

Capriza version 23 is now available with the following features, fixes and enhancements:

Dashboard Enhancement: Folders

Folders are a new feature of WorkSimple.

Capriza Support defines zapp folders for orgs. (To create a app folder, contact Capriza Support).

Once a folder or folders exist in an org, zappers assign their own zapps to folders by editing the zapp details.

start.capriza.com

An org can have a folder to which every new zap will be assigned by default. Contact Capriza Support to create this folder.

The order of the zapps in the default folder is based on the order in which the zapps entered the folder. However, the zapps in the folder can be reordered.

The folder will be displayed among all the zapps and folders according to the highest zapp order of the zapps assigned to it. Contact Capriza Support to change the order.

Dashboard Defect Fixes: None in this version.

Designer and Mobile:No enhancements or fixes in this version.

WorkSimple App Enhancements

Organizing zapps in folders

Makes locating a zapp easier for end user.

Only the zapper can assign a zapp to a folder.

2.Search for zapps has been added:

The zapp search helps end users find the required zapp.

The zapps assigned to folders are displayed in the search results without reference to their zapp folder assignments.

A zapp can be started by clicking on its icon in the search results.

3. Support for iOS Face-ID has been added.

WorkSimple App Defect Fixes: None in this version.

WorkSimple App: Migration and Known Issues:End of support for up to and including version 16.

Capriza Worksimple versions up to and including version 16 are no longer officially supported. Zapps built using these older versions of the Capriza Designer should continue to run normally, but it is highly recommended that these zapps be updated to the latest Capriza Worksimple version to take full advantage of the latest performance and user experience improvements.

To check the version of your zapp:1. Navigate to your dashboards zapp page2. Click on the version row to expand it. The zapp version number is next to the zapp URL as "Capriza version: ##".

In general, Capriza officially supports versions for up to 18 months.Please contact your Capriza Customer Success Manager for further details and assistance.

When updating your zapp to a new release version, best practice is to run through a full test cycle with several user login types and roles.

WorkSimple Studio is now available!

The WorkSimple Designer and Dashboard are now available in the new WorkSimple Studio.

With WorkSimple Studio, zappers and org admins no longer need to install Firefox on their workstation.

WorkSimple Studio, available for Windows and MAC OS, can be downloaded from start.capriza.com.

Note: Users of WorkSimple Studio Beta version should uninstall the beta application before installing the production WorkSimple Studio from .

- Capriza Product Team

To get started with creating a Zapp, install the WorkSimple Studio:

1. Download WorkSimple Studio from the following link:

https://start.capriza.com/

For Beta users, before installing WorkSimple Studio, uninstall Capriza Studio Beta.

2. If Windows Defender is enabled you may encounter an warning message:

How to Create a Zapp

3. Click Run anyway to proceed with the installation

4. Follow installation prompts to complete installation.

Upon launching WorkSimple Studio, you will be prompted with a login screen. Enter the Capriza credentials provided by your Admin.

Once logged in, you may begin creating Zapps. add additional users to your organization's account. Please refer to for more information.

Capriza version 22 is now available with the following features and enhancements.

Dashboard Enhancements

1. New actions on Zapps Feedback

1.1 Create a ticket to Capriza is an option that opens a Capriza support ticket request. The form encourages Zappers to provide useful support request details and their support expectations. These details, together with the feedback data, should help Capriza Support better understand the support request. Detailed, accurate problem descriptions provided by Zappers enhance Capriza Supports ability to provide the support they require.

1.2 Feedback Inspector (beta) is a new tool assisting in the analysis of feedback logs. It uploads the feedback runtime log file and provides initial analysis of the mobile last action, mobile page(s) score and the identifications ranking of the web controls on the web page. In addition, it presents a snapshot of the web page as displayed in the runtime agent. When relevant, it provides suggestions for fixes. The runtime log file is also available for review in the Feedback Inspector.

1.3 Add Note is an option for creating internal notes regarding the feedback items. When reviewing feedback logs, the Zapper can add internal notes regarding analysis, the debug process and other issues. When creating a ticket for Capriza, the zapper can optionally add the note by selecting the Include Feedback Note checkbox.

The ID that is included with each file associated with the feedback is also the ID of the feedback note. Note: There is only one note for each feedback, but it can be edited (including added to) at any time.

1.4 Archive/Unarchive now allows better management of feedback lists. In addition, Show Archived displays archived items in greyed-out format. Feedbacks are displayed as Unread (bold) until interacted with in any way.

2. Dashboard defect fixes are included in the release.

Designer and Mobile

Defect fixes.

WorkSimple Enhancements

Show Zapp version in WorkSimple - For all non-production zapps, the Zapp version number is displayed in the top left corner of the tile. (The version number continues to be displayed in tile details.)

Side Menu icon orientation can be changed to vertical/horizontal - please ask Capriza support to configure that as desired.

Defect fixes.

Migration and Known issues

End of support for up to and including version 15

Capriza Worksimple versions up to and including version 15 are no longer officially supported. Zapps built using these older versions of the Capriza Designer should continue to run normally, but it is highly recommended that these Zapps be updated to the latest Capriza Worksimple version to take full advantage of the latest performance and user experience improvements.

To check the version of your Zapp, navigate to the Zapp page in your Dashboard and click on the version row to expand it. The Zapp version number is next to the Zapp URL as "Capriza version: ##".

In general, Capriza officially supports versions for up to 18 months.

Please contact your Capriza Customer Success Manager for further details and assistance.

As always, it is a good practice to run through a full test cycle with several user login types and roles when updating your Zapp to a new release version.

- Capriza Product Team

Rather than creating a separate mobile application, the Capriza platform functions similarly to Google's crawlers, integrating with the UI of the source application and translating each control and page into a corresponding mobile control or mobile page. As a result, the business logic, access controls, and even design elements will be carried over from the source application.

Building Blocks

When a user interacts with the zapp, she is interfacing with the business application itself via this transformed version. All interactions within the zapp are, in turn, translated back to the web application in real time.

Capriza is able to accomplish this translation by recognizing, partially based on user input, the web elements included on each page and the relationships between them- called Facts, Anchors, and XPaths. The stronger the relationship between the web and mobile versions, the better the Zapp will function.

Facts, Anchors, and XPaths

To understand Facts, Anchors, and XPaths, it is best to use an analogy. When locating a house, people often describe three things - the house itself, its surroundings, and the house's address. As an example, to locate the house in the middle, one could say, Its a blue house with a red door (facts) next to a pine tree and between a green and a red house (anchors). Its address is 400 Hamilton Ave. Facts describe the element itself (blue house, red door), whereas anchors are unique references around the element (pine tree, between the red and yellow houses). The XPath indicates the house's exact location (400 Hamilton Ave).

Capriza works similarly. While creating a Zapp, users can provide Facts, Anchors, and XPaths for each web element that will enable Capriza to successfully find it. Facts, Anchors, and XPaths for web element can be accessed via the Strengthen Tab in the Inline Editor (ILE) for each corresponding mobile element.

While Capriza uses many other elements and heuristics to remotely navigate the application, this provides a high level overview of how the platform functions. Please refer to the sectionfor more information.

After you have successfully finished testing your Zapp, it is time to move it into Production. This article provides the key steps you should follow when publishing your Zapp.

1. Publish your Zapp in the Designer

In order to proceed with moving your Zapp to Production, you will first need to Publish via the Designer. Follow the steps in this article to complete the process.

2. Update the Source Application URL

As a best practice, Capriza recommends building your Zapp in a test environment that, while similar, is separate from the production environment and contains test data. Once Zapp development and testing are complete, you need to point your Zapp to the production environment your end users will be accessing. To do so, you simply need to change the source application URL within the Capriza Dashboard. Step-by-step instructions can be found in this article.

An additional round of testing is recommended using test accounts in the production environment to account for any discrepancies between the two environments.

3. Provide Your Customer Success Manager with Monitoring Information

The Capriza NOC team will proactively monitor your Production-version Zapp to ensure runtime and end-to-end service availability. Prior to Go Live, please provide your Customer Success Manager with the information detailed in this article so that the correct people may be contacted in case an outage or other service disruption is detected.

4. Define Distribution Groups

Published Zapps are distributed to users within your organization based on membership in a Group. Prior to pushing your Zapp to Production, you should define the group or groups to which it should be available. In general, we recommend specifying a smaller "Pilot" group of users for initial rollout as well as the overall group or groups. Please see Managing Groups and Managing Users f o r a d d i t i o n a l d e t a i l s.

5. Change the Environment

If your organization has multiple Capriza runtime environments configured (e.g. dev, test, prod), make sure the Zapp is pointed to the correct environment.Please refer to this article for detailed instructions.

6. Distribute Your Zapp

Use the distribution dialog to distribute your Zapp. See this article for details.

The Dashboard allows for a top-level overview of all existing Zapps. It keeps track of your Zapps' number of users, numbers of runs, and dates of creation.

Navigate through each of the tabs in order to see everything from your usage data to your Zapp theme options.

There are five tabs within the Dashboard: Home, Zapps, Users, Brand, and Account.

Home Tab: Within the Home tab, you can view representations of the statistics associated with all of your Zapps. Read more about the Home Tab here. here

Zapps Tab: Within the Zapps tab, you can view a list of all of your Zapps. Information regarding each Zapp's publication and logistics is displayed. Read more about the Zapps tab here.

Users Tab: The Users tab is for administrators only. Here, all the groups of the organization as well as the the number of members and Zapps within each group are listed. Read more about the Users tab here.

Notify Tab: The Notify tab enables you to configure time-based notifications to help drive Zapp adoption and remind your users of key tasks and events. More information can be found here.

Brand Tab:The Brand tab allows you toselect a Primary Brand to be reflected throughout your WorkSimple App and in the Zapps. Your Primary Brand determines which specific color and images will be predominant in your Zapp layout. Read more about the Brand Tab here.

Profile Tab: The Profile tab displays your account information. Here is where you can update both personal and corporate information within the Dashboard. Read more about the Profile Tab .

Lost access to the Dashboard?

Go to https://static.capriza.com/dashboard/reset-password.html and request to reset your Dashboard password. You will receive an email with a link to set a new password to the Capriza Dashboard.

NOTE: This feature is available only for organizations configured for Password access to the Dashboard. If your org is configured for SAML-based access to the Dashboard, please contact your Identity team if you have any issues.

ApproveSimple Documentation can be found in this link.

The following OS are officially supported for WorkSimple and for running Zapps in a mobile device browser**:

Device / OS:

iPhone 6 or newer running iOS 11* or newer

iPad Pro or newer running iOS 11* or newer

Any Android 6* or newer

*Note: Generally, we support the two latest OS versions.

- iOS 10 users mayhave access to WorkSimple up to v21.0.

-Android 5 users may have access to WorkSimple up to v19.0

Users trying to install WorkSimple on older iOS versions may see the following message. Users will see this message ifthey already have WorkSimple installedon the current device or on another iOS device using the same Apple account.

For example, say you have two devices, one is an iPhone with iOS 10 installed and another is an older iPad with iOS 9. You can first installthe latest version of WorkSimple on your iPhone and when you try to install WorkSimple on your iPad, using the same Apple account, you will be prompted to download the older WorkSimple version, if it exists.

Since the app is already installed on one device in your personal collection, it is considered to be part of your library and should be available to any devices under your Apple account.

**Note: When running Zapps as a stand-alone app in a browser, the following browsers are supported for running Zapps:

The most recent version of:

Safari (iOS)

Chrome

Android Browser

Firefox

Edge (Microsoft browser)

In general, Zapps can berun on any modern browser that supportsHTML5 (such asWindows phone browser orBlackberry phones with HTML5 compatible browser). However, these are not officially supported, and performance, therefore, may not be guaranteed.

Capriza offers multiple authentication methods for organizations to provide a safe, secure, and seamless login experience for their users.

There are five different authentication options for WorkSimple that customers can choose from to deliver the best experience for their users:

Corporate Credentials: Capriza provides SSO integration with your existing corporate credentials via SAML 2.0. We integrate with leading identity providers like Okta, Ping Identity, and more.

EMM ( Enterprise Mobility Management ): Capriza integrates with top EMM providers such as Airwatch and MobileIron. Customers can use WorkSimple for AirWatch or simply list WorkSimple and individual Zapps within their EMM store.

Quick Login : Provides an added layer of security while eliminating the need for users to remember another password. The user simply enters his email address and then clicks an email confirmation link.

Username and Password : Capriza invokes this option on your behalf. Your Customer Success Manager will pre-set a username and password and then send an email with the necessary login information to the individual user.

Instant Login : For publicly accessible, cloud-based apps, users can simply enter their work email address and be instantly authenticated with no password or verification required. Access is gated based on your company's email domain or if the user's email is associated with your Organization.

Touch ID: Anoptional layer of security that leverage your device's native fingerprint-reading capabilities.

Passcode Login :An alternative second layer of authentication for users without TouchID-enabled device. This option requires users to provide a pre-chosen four-digit passcode upon opening WorkSimple.

Benefits of Using WorkSimple

Imagine your company where employees, partners, and customers are unrestricted by the complexity of technology systems. Where they are able to complete a needed task in a minutes time, wherever they are, on any device. People are truly empowered, mobilized, agile, and able to self-serve. Its where these powerful minutes of productivity become the competitive advantage. When this is how your business runs, you will have transformed to a One-Minute EnterpriseTM.

Each WorkSimple app is personalized to each user, presenting only the Zapps that matter to that individual. The result allows users to work productively without even considering which applicationthey'reusing.

For this reason, WorkSimple is the recommended method for access Zapps. It can be downloaded from Google Play and the App Store. Key benefits include:

Branding : Add your company logo and color palette to WorkSimples main Zapp container to give your users a look and feel that aligns with your company branding.

Native Phone Features : WorkSimple also serves as a gateway for Zapps to be able to use native features. These include barcode scanning, advanced location services, calendar and contacts integration for sending emails or SMSs, and more.

Push Notifications : Push Notifications allow your business applications to actively work for your users, providing each person with alerts about updates to key information or attention to vital tasks. Ensuring your users receive just-in-time information and tasks helps them focus on the most important items to drive business efficiency.

User Interface Optimization

In addition, WorkSimple automatically optimizes the user interface based on the number of Zapps your organization has distributed to a particular user. For a user with more than four Zapps in WorkSimple, Zapps are displayed as tiles. For users with four Zapps or fewer, Zapps are displayed as an entire row.

If a user does not currently have any Zapps in WorkSimple (likely due to entering the incorrect email address), appropriate messaging is provided.

Capriza provides a set of API calls that allow Admins to export certain types of information. In this article we will cover how to export usage data. Usage data includes details about Zapp runs by users in your organization for one or more Zapps and may be fed into third party analytics platforms and other tools for further analysis.

The API call to the Capriza database is:

https://napi.capriza.com/api/adoption/runs/master-app-id/[<zapp ids>]?rawdata=true&from=<epoch time>&until=<epoch time>&source=all--cookie "auth_token=<authentication token>"

The input parameter authentication token is required and should be passed in a cookie. To get the required token, please contact your Capriza Customer Success Manager.

Note:The authentication token is unique to your user account and should be treated as highly sensitive. Never share your authentication token.

The other input parameters are:

zapp-ids: Comma separated list of Zapp IDs. You may either use the Master Zapp ID (which corresponds to all Production versions) or the Zapp ID for a specific version of the Zapp. Note that if you select the latter option, you must change "master-app-id" to "app-id" in the API call. To get the list of Zapp IDs, please contact your Capriza Customer Success Manager.

from: The beginning of the time period from which to get the usage data. The timestamp should be given in UNIX milliseconds notation (see conversion details in http://www.epochconverter.com/ )

until: The end of the time period until which to get the usage data. The timestamp should be given in UNIX milliseconds notation.

The output would be a JSON response with a list of all the runs performed using the requested Zapps during the date range given. Each run will include information about who ran the specific Zapp, when and some additional performance information.

The fields in the output JSON response are:

Date - the date the Zapp was run

Time - the time the Zapp was run

Identity - the Capriza ID of the user who ran the Zapp

Email - the email address of the user who ran the Zapp

User name - the first and last name of the user who ran the Zapp

First Visible Page (ms) - time in milliseconds it took to show the first page of the Zapp

Application (ms) - time in milliseconds it took the backend application to be ready

Network (ms) - time in milliseconds it took the Zapp to connect to the backend application

The following is an example of this API's usage:

curl -v "https://napi.capriza.com/api/adoption/runs/master-app-id/[<zapp-ids>]?rawdata=true &from=<epoch time>&until=<epoch time>&source=all" --cookie "auth_token=_access_key_xxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx"

In addition to the graphs available in the Adoption tab of the Capriza Dashboard, you may also download the raw data of each Zapp session for additional analysis. The files can be downloaded by clicking thearrow next to the Runs and Events graphs.

Tracking Events via Scripting

A generating report message will display in the lower lefthand corner of the screen while your report is created. For large quantities of data (e.g. 100K+ runs), this may take up to five minutes.

You will receive an alert in browser when your report is ready.

Zapp Runs

The Zapp Runs CSV file will be named Runs_actvity_yyyymmdd-yyyymmdd, with the date fields corresponding to your selected date range for the data (e.g. Runs_activity_20170216-20170317). The following columns are included in the file:

Master App name:The Zapp name.

Date: Date of the Zapp run in the following format: M/D/YYYY.

Time: Time of the Zapp run. Timezone is GMT.

Identity: A unique identifier for the end user generated by Capriza. Please see Organization-Level Statistics for more information on how Capriza tracks unique users.

Email: The user's email address. This field will only be populated if the user's email is used to signinto WorkSimple or the source application.

Username: The user's username for the source application on which the Zapp is build.

WorkSimple:The version of WorkSimple the user was on.

OS type:Android, iOS, etc.

Device model:iPhone, Nexus, etc.

Device vendor:Apple, LG, Samsung, etc.

Location- City:The nearest city per the device's location services.

Location- Region:The region the device is located.

Location- Country:The country in which the device is located.

First Visible page: The time it takes to get to the First Page of the Zapp in milliseconds. Please see Zapp-Level Statistics for more information.

Application: The time it takes the virtual browser on the Capriza Runtime to load the source application in milliseconds. Please see Zapp-Level Statistics for more information.

Network: The time it takes the mobile device to connect with the virtual browser in milliseconds. Please see Zapp-Level Statistics for more information.

Number of Events: The number of Events carried out during the Zapp run.

Session ID:A unique string relating to that particular session.

Event Data

The Event Report is a csv filed with the name format Events_activity_date-date with the date fields corresponding to your selected date range for the data (e.g. Events_activity_20170216-2017-0317).The following fields are included:

Date: Date of the Zapp run in the following format: M/D/YYYY.

Time: Time of the Zapp run. Timezone is GMT.

Identity: A unique identifier for the end user generated by Capriza. Please see Organization-Level Statistics for more information on how Capriza tracks unique users.

Email: The user's email address. This field will only be populated if the user's email is used to log into WorkSimple or the source application.

Username: The user's username for the source application.

Event: The name of the event as defined in the Designer during the Zapp Building process. Please see Implementing Event Tracking for more information.

Conversion:Indicates if a particular event represents a conversion (i.e. indicates successful completion of the Zapp workflow). If an event is a Conversion Event, TRUE will appear in the cell. If not, the cell will be blank.

Data: This column contains additional information about the Event, such as value of the action (i.e. text input into a textbox, selection made from a dropdown, etc.), name (if the control is a button or link), or value passed via custom script (please see ).

Support Channels Template Deck: Leverage this Powerpoint to detail each point of contact for Support and Change Management.

Supporting Your WorkSimple End Users: This document details out our best practices for Support.

Help Desk Knowledge Base Articles Example: Articles on key topics for customers that wish to incorporate Capriza content directly into existing help desk wikis.

Structured Questionnaire Template: A sample template for help desk teams to triage issues.

This document covers our change management best practices and provides a template for you to detail key aspects of each Zapp.

Ensuring availability and an error-free experience are key to Zapp adoption. To help customers in this endeavor, Capriza provides 24/7 monitoring of Production Zapps for all customers. If we detect an issue with your Zapp, an email alert will be sent to your designated Emergency Support contact.

[email protected]

When we detect that the issue has been resolved, a resolution alert will also be sent.

The following catalogues the different types of alerts Capriza may send your team.

Zapp Alerts

Title

Description

Source App Down

We have noticed that your source application for your Zapp is not accessible and your Capriza users are currently not able to use the Zapp.

Heartbeat Failure

We have noticed that your production Zapp is experiencing Heartbeat failures. Heartbeats are runs invoked periodically by our monitoring system, running the zapp up-to the login page of your source application. This means that the zapp is completely (or partially) not working now.

As Heartbeat runs verify end to end connection from an end device, via the Runtime Server and to the source application server,

Heartbeat failure, could mean an issue on this path, e.g. connectivity issue from the Runtime to the source application server.

It is recommended to review and analyse the reasons and strive for a fix.

High Error Rate

We have noticed that your production Zapp has a high error rate.

These errors can be caused by changes in the source application or by temporary availability issues of the source application, or a networking issues.

It is recommended that your mobility / zapp development team review and analyze the errors and work towards fixing them

Infrastructure Alerts

Title

Deployment Type

Description

VPN Down

Cloud

We have identified that the VPN tunnels between our network and your source application are down.

No Sessions Available- Server Down

On Prem

We have noticed that there are currently no web browsers available to serve your Zapp users. This means that new Zapp sessions cannot be started and users will receive an error message. We believe the current situation is due to the runtime servers not running.

No Sessions Available- All Used

On Prem

We have noticed that there are currently no web browsers available to serve your zapp users. This means that new Zapp sessions cannot be started and uers will receive an error message. We believe the current situation is due to the number of active sessions having surpassed available resources.

50% Runtime Utilization

On Prem

We have noticed that your runtime environment has high utilization, currently over 50% of the Runtime Agents (virtual Firefox instances) are in use for running zapp-sessions. This status varies over time per users activity, but if this continues, it may be advisable to deploy additional Runtime Servers.

Runtime server installation requirements are provided in our Help Center.

For the setup and installation of additional runtime servers, please contact your CS contact or [email protected].

Node Out of Sync

On Prem

We have identified that one of your nodes requires a non-urgent maintenance procedure, that you can perform on your end.

Service is operational and will not be impacted during this procedure.

Capriza Configuration Agent on one of your nodes {Node ID}, is not in sync with Capriza Central Configuration Management Service. This means we cannot fully monitor its configuration and health.

This is not an emergency but a maintenance procedure is required, as described here:

Please log in to the server as root and run the following commands.

Please send a screenshot of the results:

outpost agnet stop

outpost agent start

outpost sync

Here is an example of a 100% successful and expected result

[root@My-Example-Server]# outpost agent stop

agent stopped

[root@My-Example-Server]# outpost agent start

agent started

[root@My-Example-Server]# outpost sync

[2018-01-18T23:36:55.037Z] DEBUG [outpost] processing command: {"type":"sync"}

[2018-01-18T23:36:55.446Z] DEBUG [outpost:command:sync] sync is complete

[2018-01-18T23:36:55.650Z] DEBUG [outpost] command sync finished with success

Premium Monitoring

Premium monitoring is also offered. This package includes proactive triage by a Capriza engineer of issues like high error rates, connectivity issues, etc. Please reach out to your Customer Success Manager if you are interested in this package.

Touch ID is an available secondary authentication method for iOS and Android users on WorkSimple version 18 and later. When used, a user with an already active session will need to verify his fingerprint when re-opening the WorkSimple application. This feature enables an additional layer of security for accessing Zapps while still maintaining a low friction user experience.

When enabled, the user experience is as follows. During the first run of WorkSimple, theuser logs in with the organization's primary authentication method (e.g. Quick Login, SAML, etc.). If the user ison a device with TouchID he will then be prompted with the option for enabling it for secondary authentication toWorkSimple. Once the user clicks "Enable Touch ID," he will need to confirm his fingerprint.

passcode

Once enabled, the user will be prompted to verify his fingerprinteach time he opens WorkSimple (as long as his session is still active).

Note: This feature is a companion to our passcode feature. Users without a TouchID compatible device will instead be prompted to create a passcode, and users not wishing to enable TouchID can instead opt for passcode by tapping the link "Not now, set a instead" at the bottom of the page.

In addition, the user may change his TouchID preferences at any time by navigating to Settings (located in the side menu bar) and selecting "Touch ID & Passcode."

From here, the user may toggle TouchID on/off and, if passcode has instead been selected, reset their passcode.

What are Notifications?

Capriza provides push notifications within WorkSimple to help you drive adoption across your user base. Push Notifications are one of the main drivers for return usage of apps and maximize the value of mobility by delivering key information/reminders to users the moment they need it.

Configuring Notifications via API

Available types of notifications include:

Time-Based: Help drive workflows on schedule by notifying the users at regular times or intervals.

Email-Based: Convert the transactional emails already sent by your source applications into mobile notifications.

API-Based: Leverage an API call to alert users when new items are pending approval, when key metrics change, etc.

Example Use Cases

Push Notifications

Sales

New Opportunity

Lead Upgraded to Opportunity

Opportunity Closed

Quote Approved

Deal Approved and Processed

Review Opportunities (Weekly)

Reached your quota for this quarter

Reached your quota for the year

Field Delivery & Fulfillment

New Delivery Request

Delivery Due

Completed your Weekly Delivery Goals

Managers

New Approval Request

Approval Request Past 3 Days

HR

New Paystub

Submit Timesheet for the Week

Company Holiday

Update Benefits

Temp Employee Extension

Company Announcement

Field Support & Maintenance

New Service Request

Service Request Due

Completed your Weekly Work Goal

Implementing Notifications

Please see the following articles for information on implementing Push Notifications and Cards:

Time-Based Notifications

Email-Triggered Notifications

The contents of this article is also covered in the below video.

The Capriza Designer includes several settings in Test mode designed to enable you to more fully evaluate your Zapp's login and caching settings and the associated end user experience. It is highly recommended that you test your Zapp with various combinations of these settings enabled.

Test Settings can be accessed in Test mode via an icon above the mobile preview.

interactive

Four options are included in the resulting dialog:

Login to the Zapp using login cookie

Login to the Zapp using the saved credentials

Test cached page

Simulate disconnected cached page (only available when Test cached page is enabled)

Each option can be checked/unchecked to test your Zapp in various scenarios.

Click "Save" to save any changes. Select "Save & Start Over" to save your changes and immediately restart the Zapp in Test mode.

Login to the Zapp using login cookie

This setting allows you to test any login cookies you may have configured during Zapp building. To test, enable the setting and run the Zapp once. Select "Start Over" and log in again. This second Zapp run will use any login cookies that were automatically detected by Capriza or configured during the Zapp building process. By selecting the correct login cookies, you can improve the user experience of your Zapp by bypassing the login page and automatically authenticating the user.

Login to the Zapp using the saved credentials

This setting will demonstrate the end user experience upon subsequent logins when the user has chosen to save credentials. When enabled, the previously saved username and password are already included on the login page. To authenticate, all the user must do is click the login button.

Test Cached Page

When toggled on, this setting will enable you to preview the end user experience created by your first page caching settings. Detailed in this article, first page caching enables you to improve perceived performance and the overall end user experience by caching the first page of your Zapp and even allowing user interaction with it while the source application loads.

Simulate disconnected cached page

This setting simulates the end user experience when the backend application is out of sync with the cached first page, such as what would occur while the Zapp is open but the source application is still loading. You can leverage this setting to evaluate if the controls you have chosen to make on the cached page create an optimal experience on the mobile device.

When testing with this setting enabled, your cached first page will appear in the mobile preview and a message noting that the source application is disconnected will appear in place of the source application. Click the "Connect" button underneath this message at any time to reconnect the source application.

The Capriza platform can be divided into four main parts: Dashboard, Designer, WorkSimple and Runtime.

DashboardThe web-based Capriza Dashboard enables you to manage all aspects of your Capriza implementation, including:

Configuring internal user accounts;

Creating zapps;

Publishing zapps;

Managing user groups and distribution lists.

Architecture Overview

The dashboard also includes both global and zapp-specific statistics around users, zapp runs, events, and other key metrics to help you evaluate adoption.

DesignerThe Capriza Designer enables you to transform enterprise applications into simple, mobile workflows with no coding or access to APIs. Once installed, you can simply navigate through the web application as normal, guiding the Capriza Designer along the way. Capriza understands the your inputs and translates the controls and content you interact with into a mobile workflow in real-time.

Using the designer, you can also style, test, and ultimately publish your zapp.

WorkSimple

WorkSimple is a hybrid app available on iOS and Android that enables end users to access the Zapps that are published to them. WorkSimple also makes it possible to extend additional native mobile functionality, such as push notifications, to Zapps and integrates with existing enterprise investments such as Mobile Device Management (MDM) solutions and Single Sign On (SSO) platforms (e.g. SAML, etc.). WorkSimple can also house non-Capriza apps, allowing your end users to access all work-related applications and workflows from a single location.

Runtime

The Runtime is the core architectural component of Capriza's backend via which Zapps execute. The Runtime consist of secure headless browsers that access your business applications via a desktop browser. When a Zapp launches, Capriza leverages the inputs provided via the Designer to translate the desktop application accessed by the headless browser into a mobile-first experience for the end user.

The Runtime also optimizes performance globally, handles SSO including Kerberos, and ensures all application and data security is inherited and contained. It may reside in the Capriza Cloud or behind your corporate firewall. (See for a breakdown of available configuration options.)

The following article provides an overview of the layout and functionality of the Capriza WorkSimple application.

WorkSimple Interface

WorkSimple is divided into two main tabs:Zapps, and Notifications.

Zapps

The Zapps tab displays tiles foryour organization's various Zapps. To ensure a tailored experience for the end user, only the Zapps that have been distributed to that particular user are displayed.

Org Admins

Notifications Tab

Notifications are housed in a separate tab for increased visibility. When you have pending notifications, a red badge will appear on the home screen of your device as well as on the bell icon on the WorkSimple navigation bar. (Note:If your primary brand color makes it difficult to see the red badge on the bell icon, it can be changed to white. Please contact your Customer Success Manager to enable this setting.)

Tapping on any of the notifications will deep link into the item in the Zapp requiring the user's attention.

Swipe right to dismiss a notification.

Header Image

The header image is located in the upper third of the WorkSimple screen and is pulled into the background of the remainder of the screen for brand-consistency. You can specify the default banner image via the Brand page in the Capriza Dashboard, and you can also include different banner images per user using Organizational Policies.

End users can also personalize the banner image. To do so, tap the image and select an upload action.

Choosing the "Company Image" option will restore the user's WorkSimple display to your Organization's defaulting branding.

WorkSimple Zapp Actions

You can learn about your Zapps and perform actions by tapping the () icon. From this menu, you can view version details and add a shortcut to your devices homescreen.

The Details option displays a Description of the Zapp as well as notes on that particular version. You can run the Zapp using the "Run" button at the bottom of the dialog.

Shortcut enables you to bookmark the Zapp on your phone's Homescreen. Please refer to this article for more information.

You can also long press on any tile to reorder your Zapps.

WorkSimple Side Menu

From the WorkSimple Side Menu, you can request a Zapp, change your notification settings, send WorkSimple feedback, and sign out of your account. To access the Side Menu, tap the menu icon in the top left of WorkSimple.

The following actions are available:

Profile Image: To change, tap on the image.

Request Zapp: Have an idea? From here you can submit a request to your IT department for a new Zapp. The request will be received by all .

Settings: Settings allows you to control which Zapp notifications you are following. From here you can turn Zapp-specific business alerts on or off.

Send Feedback: Send feedback to your IT department relating to your experience with WorkSimple.

Sign Out: To log out of WorkSimple. Re-authentication is required upon logging back in.

When logged into a Zapp, the side menu options change slightly:

Home:Tapping Home will take you back to the main WorkSimple interface with your Zapp catalogue.

Settings: In Zapp Settings, you can clear your cache (history) as well as saved field values.

Send Feedback: Send feedback to your IT department relating to the experience youre currently having with the Zapp.

Sign Out: To log out of that particular Zapp.

WorkSimpleTM is your personal mobile workspace. Micro apps called ZappsTM along with Notifications from all business applications are centralized in one place with one look and feel. You can download WorkSimple from the App Store and Google Play.

Offline Access

Capriza provides offline access to Zapps so that you and your employees can access your most valuable data even in situations with limited connectivity. Currently, this functionality consists of the ability to access the Most Valuable Page (MVP) while offline. The MVP is the first page that loads upon opening a Zapp, following login and any Automations.

When accessed in offline mode, the MVP will load and an alert stating, "It looks like you're offline," will display.

MVP must be cached

This alert can be dismissed and you can view and interact with content on the page.

Please note that the on the mobile at least once in order to allow for offline usage. This is accomplished by running the Zapp at least once and logging into the Zapp.

If youre building a Time Entry Zapp using the universal micro app and you source application is SAP, there are several enhancements in the micro app that are specific to SAP. In addition, there are a few nuances in how you should attach the micro app that are also specific to SAP.

The following article describes the differences you should be aware of and the steps you should follow when attaching the Time Entry micro app.The article relies on the general flow of attaching a Time Entry micro app described in this article and only emphasizes the differences.

Attaching the date picker

In SAP, when selecting a date from the calendar to change the time period, you must click the Apply button for the weekly view to actually change.Therefore, after you attached the Date Picker control to the one on the web, you then need to grab the Apply button as well and add an automation for it.

Select the Button type from the Controls toolbar and grab the Apply button.

this article

Open the button ILE and turn off the Display option so the button will not be visible to the user.

Now add the automation to click on the button after selecting a different date.

Open the page Automation dialog.

Click the + button in the top right corner to add a new automation.

Select the Internal connections option for the automation trigger.

Then select the Date Picker button as the trigger.

For the New automation step, select the newly grabbed Apply button.

And click the blue checkmark button to confirm.

Finally, click on the checkmark button on the top right corner of the Automation dialog to confirm the new automation.

A new automation is created so when a user selects a date from the calendar, the Apply button will be clicked automatically.

Attaching the Total Hours text

In SAP, the total hours of the week are usually inside the table and are represented as a disabled text field on the web.

To attach the Total Hours, change the control type in the Controls toolbar to a text field.

Then click on the total hours field in the timesheet table on the web.

If the rank of the total hours control is low, you can strengthen it by adding the "Total" column header as an anchor.

Attaching the + button to add a new project to the timesheet

When building a Time Entry Zapp on SAP, the + button does not need to be attached to any control on the web. The button is virtual and contains a short script to identify the first empty row in the timesheet table on the web.

Simply click the + button to connect it to the next page, the Add Project page.

In the Add Project page, youll note that the Cancel button is also virtual and does not require attaching. Since there is no option to delete a row in the SAP table, the Cancel button simply clears the selections the user has made in case the button is tapped (this is done through an extension).

Learn more about the Add Project button and page in .

Adding a Project when there are no empty rows

In SAP empty rows are added to the table only when the current timesheet is saved. There could be a situation where the user is left with only one empty row in the table, adds a new project that takes that empty row, does not save the timesheet yet and then tries to add another new project row. In that case, since there are no available empty rows in the timesheet table on the web, we will not be able to add this new project until the user saves the timesheet and new empty rows are added automatically by SAP.

One option to address this scenario is to add a message to the user to first save the timesheet before attempting to add another project.

First add a new page with a message to the user. Click on the + button and add a new page, insert a virtual text and a virtual button and style it as a modal. See an example below.

Now you need to set the condition to show this page in the connection conflict resolution dialog.

Go to the Timesheet page connections and open the Outgoing tab.

Expand the + button connection and click on RESOLVE.

Select to show the Add Project page and add a condition if the page is applicable. Since all controls on this page are mandatory, the page will be applicable if an empty row is found in the timesheet table on the web page.

Else, show the error message page.

Now if there are no empty rows in the timesheet table on the web, the user will be asked to save the timesheet first before adding the next project.

Known issues and limitations

The following are a few known issues and limitations of the SAP platform.

- If a user adds a new project and saves the timesheet without adding any time to that project in any of the days of the week, SAP does not save that row. The project details are cleared.

- If a user adds a new project to the timesheet, it cannot be deleted using the Delete button in the swipe action. The button is attached to the column with the trash can button but that button is not yet available if the row is not filled with time information and saved first. A possible workaround is to add a script that clears those input fields from the row before it is saved.

In order to obtain access to the Update URL function and other configurations required to move your Zapp to Production, you must first Publish it in the Designer. You can do this by clicking the Publish button in the upper right hand corner of the Designer.

new version

If any tasks in the Task Manager are still pending, a dialog asking if you wish to Publish with Issues or View Tasks will appear. Please refer to the Overview of the Task Manager article for more information.

If you still choose to publish your Zapp, a dialog will appear. Here, you may enter internal notes for the version you are about to publish. These notes will only be available to users who have access to the Zapp via the Dashboard (other designers and admins). The purpose of these notes is to communicate to other Zapp builders what was done in this version of the Zapp. Once ready, click Publish.

Note: Once you have published a Zapp version, you can no longer edit it. To make changes a must be created.

Table of Contents

Introduction

Attaching the date picker

View timesheet by Calendar Period

Attaching the + button to add a new project to the timesheet

Attaching and interacting with the Cancel button on the Add Project page

Introduction

If youre building a Time Entry Zapp using the universal micro app and your source application is PeopleSoft, there are several enhancements in the micro app that are specific to PeopleSoft. In addition, there are a few nuances in how you should attach the micro app that are also specific to PeopleSoft.

The following article describes the differences you should be aware of and the steps you should follow when attaching the Time Entry micro app.The article relies on the general flow of attaching a Time Entry micro app described in this article and only emphasizes the differences.

Attaching the date picker

In PeopleSoft, when selecting a date from the calendar to change the time period, you must click the Refresh button for the weekly view to actually change.Therefore, after you attached the Date Picker control to the one on the web, you then need to grab the Refresh button next to it as well and add an automation for it.

Select the Button type from the Controls toolbar and grab the Refresh button.

Open the button ILE and turn off the Display option so the button will not be visible to the user.

Now add the automation to click on the button after selecting a different date.

Open the page Automations dialog.

Click the + button in the top right corner to add a new automation.

Select the Internal connections option for the automation trigger.

Then select the Date Picker button as the trigger.

For the New automation step, select the Refresh button.

And click the blue checkmark button to confirm.

Finally, click on the checkmark button on the top right corner of the Automations dialog to confirm the new automation.

A new automation is created so when a user selects a date from the calendar, the Apply button will be clicked automatically.

View timesheet by Calendar Period

PeopleSoft provides the user with multiple ways to view a timesheet.

By default, View By Week is selected, which means, that by default, the weekly view of the timesheet will start from the date the user selected.For example, if the user selected Wednesday, 08/23/2017, the weekly view will be Wednesday to Tuesday.

If you wish to make sure that the weekly view will always be Monday to Sunday, for example, you will need to create an automation to select View By Calendar Period when the user first enters the timesheet page. When View By Calendar Period is selected, the weekly view will always show the week of the selected date, regardless of the selected day of the week.

For example, if the user selected Wednesday, 08/23/2017, the weekly view will show Monday to Sunday of that week.

To create the automation, first grab the View By dropdown, then hide it (turn off Display) in the ILE.

Add a new automation.

Since this only needs to be done once, the automation trigger can be "Page loads from some connection" and select the Sign In page.

Add an automation step to select Calendar Period from the View By dropdown.

And add another automation step to click on the Refresh button (see previous section about attaching the date picker for reference to the Refresh button).

Dont forget to click on the blue checkmark buttons to confirm the automation steps and add the new automation.

Attaching the + button to add a new project to the timesheet

When building a Time Entry Zapp on PeopleSoft, the + button on the mobile page needs to be attached to the + button in any one of the rows in the table (its not important which button is attached, any one of them is good).

The button itself also contains a short script to identify the first empty row in the timesheet table on the web.

Heres the full script:

Now simply click the + button to connect it to the next page, the Add Project page.

Attaching and interacting with the Cancel button on the Add Project page

In the Add Project page, youll note that the Cancel button requires to be attached to the delete column in the timesheet table. Similarly to the fields representing the project details, the column with the - icon should be attached as well and will be connected to the Cancel button.

Before attaching the ghost table:

After attaching the ghost table:

Note that the Cancel button is now attached to the Delete column.

Clicking Cancel in the Add Project page

When you click on the Cancel button in the Add Project page, since youre clicking on the rows - button on the web application, PeopleSoft will prompt you to confirm you wish to delete the row.

Since the user does not know the project row is already added, we recommend to automate through this delete confirmation.

Click on the Cancel button in the Add Project page, and when prompted, select a new page.

Grab the Yes - Delete button and click it.

A click automation will be created for this page.

When prompted, connect back to the timesheet page.

Alternatively, if you wish to be extra careful and allow the user to be sure before canceling adding a new project, you can grab this dialog and style it as a modal.

For example:

Overview

When building a Time Entry Zapp, the user may need to add a new project to the timesheet. In most typical web applications where the timesheet is a table, adding a new project requires adding a new row and filling in the project details, such as the name, description, ID, etc.

Some tables may already have a few empty rows and all the user needs to do is fill in the project details and in some cases, there may be a need to first add the empty row and only then fill it in.

Attaching and connecting the Add Project '+' button

On the timesheet page of the Zapp, attach the + button to the relevant button on the web application that adds another empty row to the table. The button to add an empty row may be in a column as part of the timesheet table or a button outside the table.

Click the + button and connect the "Add Project to Timesheet" page.

+ button script to mark the empty row

The + button to add a new project to the timesheet may include a short script to be able to identify the index of the first row that is empty in the timesheet table on the web.

The reason weneed to know the index of the first empty row is so that we would know which row to fill out with the new project details (see additional details in the following section).

To view, edit or add the script, open the web properties dialog by clicking the wrench icon in the control toolbar when hovering over the control.

Navigate to the PROPERTIES tab, scroll down and expand the Override actions section.

To add a new script, enable the Click override and add your script.

In some systems, such as SAP and PeopleSoft, this script is provided out of the box.

Here is a sample code for saving the first empty row index:

//Get Time Sheet table controlvar timeSheetTbl = context.getControl("TimeSheet");

//Save the last row index of the table + 1shared.emptyRowIndex = timeSheetTbl.rowCount + 1;

console.log("Empty Row index " + shared.emptyRowIndex);

mouse.click(element).then(resolve);

How to attach the Add Project page to an empty table row

In the Add Project page there are two areas. The top part of the page includes the fields that the user will need to fill out to define a new project. The bottom page of the page below the Table to Attach separator includes the actual table where a new project row is added. Well call this table a ghost table since it is not actually visible to the user on the mobile device.

The purpose of the ghost table is to allow the user to fill out an empty row in the timesheet table on the web with the new project details. We only display to the user the fields of the relevant columns representing the project details, but those fields are connected the first empty row of the table (we filter out the non-empty rows).

Once the ghost table is attached, the project fields displayed to the user will be automatically connected and there's no need to attach them as well.

In order to show to the user the relevant fields to fill out to add a new project, you will need to attach the relevant columns from the web. Once you attach each column, the associated fields in the top part of the page will become enabled.

Click on Get Started to start the Attach Wizard and follow the instructions to attach the table from the web.You will need to attach the table normally but when modifying the type of the control to apply, a lookup type or dropdown type, for example, you can grab that type from any row in this table. The last step of attaching the ghost table will ask you to connect to the first empty row. We will automatically detect the first empty row and connect that to the controls in the Add Project dialog.

Note that the last column in the table to attach is a Delete button to delete that empty row. This delete column will be automatically attached to the Cancel button at the bottom of this page.

If the timesheet table contains a specific column with a Delete button per row, attach that column. If the timesheet includes a different way to delete a row, you may need to modify this page to attach the Cancel button differently.

Modifying the control types of the project fields

By default, the Add Project page contains two fields that describe the project. One field is a dropdown and another is a lookup.

The timesheet table in the web application may include different types of fields that describe the project. For example, instead of a dropdown, you may need another lookup.

To change the type of project field on the mobile page, simply select a different type of control that matches the type on the web application.

First, attach the relevant column from the web.

When prompted to attach the type of control for that column, you can select a different type of control from the toolbar on top that matches the actual type of control of the column on the web.

If you select any of the visible control types, the control on the mobile page will remain as a dropdown. If you select any of the types available under the Other menu, the mobile control type will change accordingly.

Adding another project detail field

By default, the Add Project page contains two fields that describe the project, but you may want to add additional fields that are required in your web application.

First you need to grab the relevant column, apply the relevant control type, and add it to the ghost table, then open the ghost table ILE and go to the ITEMS tab. Note that the new column you just added is now in the Unassigned section of the table items.

Drag the column to the Top Level section of the table items.

Click on the + button next to the column you just added to add this control to the top section of the page visible to the user.

You should now be able to see this new control on the page.

Removing a project detail field

By default, the Add Project page contains two fields that describe the project, but you may want to remove a field that is not required or one that you added and no longer need.

To remove an unneeded field, first delete the control from the top part of the page visible to the user.

You can then remove the unneeded column from the ghost table by going to the table ILE and navigating to the ITEMS tab. There, drag the unneeded column from the Top Level section to the Unassigned section or simple click on the - icon next to the control you wish to remove.

Once the column is in the Unassigned section you can simply click on the - icon to remove it completely from the ghost table.

Creating a New Time Entry Zapp from a Universal Micro App Start creating a new Zapp by clicking the New Zapp button at the top of the Dashboard. You will be directed to a page with available Universal Micro App categories. Select either the HR or Field Services category to find the Time Entry micro app.

this article

The name and description of your Zapp are already filled and you can always edit those fields. Enter the URL of your web application and click Go.

The Zapp is ready to be attached to the web application. You will be encouraged to view a quick video tutorial about working with the Time Entry micro app, which is also available in this article.

Once you watch the video and dismiss the introduction screen, you can start attaching your Zapp and also check out all the available pages in Style mode at any time.

Attaching the Time Entry Universal Micro App to a Web Application

Now that your micro app is selected, you need to attach each mobile control to a corresponding web control on the web application. The following video describes the process of attaching the Time Entry micro app to a web application. Detailed instructions are below.

To begin attaching the Time Entry template using the wizard, click on the Get Started button in each one of the pages above the mobile page view in Simplify mode.

Learn more about working with micro apps in general and how to attach mobile controls to the web application in this article.

Attaching the Time Entry table

Once you reach the timesheet page click on Get Started to start attaching the timesheet elements.It is recommended that the timesheet table on the web contains at least one or two rows of information, both project details and hours, but the row can be empty of hours information.

You will first be asked to attach the Calendar or Date Picker.

Select the calendar from the web page that allows you to select the relevant time period.

Once the calendar button is attached, you are now attaching the timesheet table itself. You will first attach the project details columns (name, description, ID, etc.) and then you will attach the columns representing the days of the week.

Note that each project column is attached as text. If you need to later convert the columns to dropdowns, lookups or other types of controls, you can do that at the end of the table attachment flow. Learn how to convert text columns to non-text types in the Data > Table article, under the Activating a Non-Text Table Item section.

Once you attached the project details columns, you are now attaching each individual day column. You will first be requested to attach the day column and then convert it to text field.

Attach day column:

Convert to text field:

Note that you are starting from attaching the Monday column but if your timesheet table starts on Sunday or Tuesday or any other day, feel free to grab that column first. The actual content on the web will override the sample content in the micro app.

Continue attaching the remaining days columns. First attach the column and then convert to text field.As you grab the days columns, the weekly view header changes to reflect the actual day and date in the web application.

You can choose to change the style of this weekly view or customize the displayed text or selected day. This article describes how to configure and style the weekly view header.

Once you attach all days of the week in the timesheet table, you are taken to the project details page (row drill page) to attach the total hours of that project as well as the delete button that deletes a project row.

Note that similar to the day columns you attached previously, attaching the delete button is also a two step flow. First you are prompted to attach the column with the button used to delete a row.

Then you convert the column to a button type:

Once you finish attaching the timesheet table, you are prompted to hide or filter the empty row is the table, so that the timesheet on the mobile view is lot cluttered with empty project row.

If the all timesheet rows are empty, the table will show that no projects are available.

You can customize the empty state message in the table ILE.

Learn more about attaching and configuring the Delete Project button in this article.

The last four steps in the attachment wizard are related to attaching the bottom floating elements on the page.

Attach the text indicating the total hours of the week, the button to add a new project to the timesheet and the two buttons to save and submit the timesheet.

Note that the text representing the Total Hours is attached as a text pair so you will need to grab both the label and the number of hours.

If the type of control on the web application representing the total hours is different than a text or a text pair, make sure to first change the type in the control toolbar before attaching it.

To learn more about how to attach and configure the flow to add a new project to the timesheet associated with the + button, read .

Attaching the remaining pages in the Zapp

Once all the controls on the timesheet page are attached, you can finish attaching the remaining pages.Click on each one of the buttons on the page and select the relevant page offered by the micro app and attach it to the corresponding page on the web.For example, click on Save Progress and select the Save Confirmation page and attach the OK button to a corresponding button on the web or keep it virtual, in case the web does not offer a dedicated confirmation dialog.

Introduction

Time Entry is a very common use-case among hourly workers or any employee that must report the amount of time spent on a specific project or task during the work day. Time reporting is used for accounting purposes, to know the correct salary to pay hourly employees, for future project effort estimations and more.The importance of tracking time is significant but using existing, desktop oriented applications usually requires somewhat of an effort from the user which leads to unfilled time sheets, delays in recognizing project efforts, billing customers, paying employees and can impact the bottom line of the company.

Time Entry Universal Micro App

Entering time using is a mobile device is a much faster and easier process that can be done on a daily basis and completed in few seconds. To assist in building this mobile experience, Capriza provides a Time Entry universal micro app that pre-defines the mobile user experience.

What is included in the Time Entry Micro App?

Time Entry micro app contains 7 pages where the main page is the timesheet itself and other pages are supplementary to add a project and handle success and error events.

The first page is the Sign In page that includes the title of the Zapp, two text fields for username and password and a Sign In button.

Attaching the Time Entry Micro App to SAP

The next page is the main time entry page. It includes a weekly view of the timesheet, a list of project per day, a calendar to select the week to view, the total hours entered for the week, an option to add a new project to the timesheet, an option to save the timesheet and an option to submit it for approval.Each project row contains the project name and description, but this is simply the recommended information that may be in the table but can be easily changed based on actual content in the web application.Note that although the mobile view appears to be several individual tables for each day where the days of the week are arranged as tabs, the assumption is that in the source application, the entire timesheet is contained in one single table.

Note that you can either tap a specific day in the weekly header or swipe left or right to navigate between the days of the week.

When tapping a project row in any day, you can navigate to a details page of the selected project.

The detail page contains details about the project (based on the selected columns), a full weekly view of the project and the option to delete the project from the timesheet.

The next page is the Add Project page. It contains the project details that need to be entered in order to add a new project row to the table.As in the timesheet page, the information on the page is simply a recommendation and can be easily edited, removed or added to, in case you need to add or remove details about a project.

To learn more about how to edit the micro app and add or remove a project detail, see the Adding a New Project to The Timesheet article.

The next page is associated with the lookup field that is available in the Add Project page. The page represents the lookup page that allows the user to select the proper project.

The last few pages are related to confirming user actions or providing feedback about the success or failure of an action.

Delete a project row confirmation page, associated with the Delete Project from Row button in the row swipe action.

Timesheet was saved confirmation page, associated with the Save Progress button in the timesheet page.

Timesheet was submitted confirmation page,, associated with the Submit button in the timesheet page.

Note: The data in each page of this universal micro app is simply a suggestion to provide inspiration to the Zapp builder and can be replaced with actual content from the web application once the mobile control is attached to the web.

For more information on working with Time Entry template, see the following articles:

Building a new Time Entry Zapp using the Micro App

Customizing the Weekly View Header of a Time Entry table

Adding a new project to the timesheet

Deleting a project - new page vs. mobile only confirmation

Attaching the Time Entry Micro App to PeopleSoft

To remove a micro app from Production, open the Zapp Versions menu by clicking the three dots on the righthand side of the Zapp version.

Select "Remove from Prod."

A dialog will surface, asking you to confirm your selection.

Choosing "Remove" will undistribute the micro app. It will be tagged as "Past Production" in the Zapp Versions page.

Capriza is a SaaS solution that mobile-enables the most critical workflows from any enterprise application, including SAP, Oracle, PeopleSoft, and custom-built systems. In today's mobile-dominated world, Capriza makes it possible to deliver simple workflows that employees, customers, and partners can access from anywhere. Traditional systems that have developers create apps for users, often lead to lengthy and costly implementations. In contrast Capriza empowers users to create tailored app experiences based on existing workflows and business tasks for their specific needs. This delivers an unmatched user experience where apps become an extension of how people work, leading to higher engagement, and increased productivity.

Modernize Legacy Applications

Capriza is application agnostic, allowing you to mobilize any HTML-based application. Zapps can be accessed on any device mobile, tablet, and desktopto power a truly mobile workforce.

No Business Disruption

Zapps are created using the browser-based Capriza Designer with no coding, APIs, or upgrades required. This approach makes it possible to quickly build mobile workflows without first needing to hire mobile developers or UX experts. Business flows and logic are automatically inherited from the source application, enabling you to leverage existing customizations.

The Most Secure Way to Go Mobile

With no end user data stored on the mobile device and end-to-end encryption, Capriza is the most secure way to make enterprise software applications mobile. Integration with leading Mobile Device Management platforms is also supported, and Capriza is ISO 27001-certified.

In addition to the Organization-level statistics found on the Home page of the Capriza Dashboard, Capriza also provides Zapp-specific statistics. This article provides an overview of each of the metrics available. It is divided into the following sections:

Zapps Page

Zapp Versions Tab

Adoption Tab

Diagnostics Tab

Zapps Page

The Zapps page of the Capriza Dashboard displays a list of all of your Organization's Zapps or (if you are an Org Admin) all of your Organization's Zapps. For each Zapp, the title, icon, owner, number of users (all time), number of runs (all time), date created, and number of versions is displayed.

Configuring Custom Error Messages

Click on any Zapp to drill down to that specific Zapp's versions and metrics. You can search for a Zapp in the search bar at the top of the page and filter your Zapp view based on the Zapp's status (e.g. Production, Not Distributed, etc.), distribution group, or if you are the owner.

You can also sort Zapps by a variety of metrics, including Date Updated, Date Created, Creator, Name, Versions, Runs, etc.

The Grid View option at the top enables you to view your Zapps as a grid rather than a list.

Zapp Versions Tab

The Zapp Versions tab displays the Zapp's Master Details (i.e. title, icon, description, etc.) along with a list of each of its versions.

Each version's number, date created, last edited date, number of users (all time), number of runs (all time), date of last run, and release notes are displayed. A color icon to the left of each version number indicates the health of that particular Zapp version that week.

Zapp versions can also be filtered by their distribution status and particular distribution list.

Adoption Tab

The Adoption tab displays key metrics around users, runs, and events. At the top of the Adoption tab, you can set global filters for:

Zapp Version: All Versions, All Production Versions, or a specific version number.

Date Range:Several preset filters are available:

Last 7 days (previous 7 calendar days)

Last Week (previous full week Sunday to Saturday)

Last 30 days (calendar days)

Last 1 month (last full month 1st to 30th/31st)

Last 3 months (previous 3complete months)

Last 6 months (previous 6complete months)

Last 12 months (previous 12 months ending on the last day of the most recent full month, i.e. February 1st to January 31st)

From Zapp Creation

Custom Date Range (selected via the calendar picker)

View By:Show Daily, Weekly, or Monthly data. Note that data for period greater than 3 months is only available on the Weekly or Monthly level.

Any filters you set in the Adoption tab will be persisted as you migrate between different Zapp pages.

Statistics in the Adoption tab are divided into three sections:Runs, Unique Users, and Events.

Runs

Runscontains two column graphs:

Runs: The total and day-by-day count of runs for the selected time period. Mousing over each individual bar provides the number of runs for that day. Please see the Home page article for information on how Capriza calculates runs.

Average Converted Runs: The overall and day-by-day average percentage of runs that include at least one conversion event. Please refer to the Overview of Event Tracking article for more information on conversion events.

Yellow dots in the Runs graphindicate when a new Zapp version was released to Production.

Raw data is available for download by clicking the download icon in the upper right hand corner of theRuns graph.

Unique Users

The Unique Users section contains two column graphs:

Unique Users:The total and day-by-day count of unique users for the selected time period. Mousing over each individual bar provides the number of users for that day. Please see the Home page article for information on how Capriza calculates unique users.

Average Converting Users:The overall and day-by-day average percentage of unique users that perform at least one conversion event. Please refer to the Overview of Event Tracking article for more information on conversion events.

Yellow dots in the Unique Usersgraphindicate when a new Zapp version was released to Production.

Events

The Events section is divided into two column graphs:

Events: The total and day-by-day count of events for the selected time period. Multiple events are displayed as a stacked bar with color coding. Please see Overview of Event Tracking for more information.

Mousing over each individual bar provides a breakdown of the account of each event type per day.

You can click the "Edit View" button in the bottom right hand corner to select/deselect which events are included in the graph.

Conversion events are indicated in the dropdown and legend with a bullseye.

Average Conversion Events Per Converted Run:Total and day-by-day average number of conversion events that occurred in each run with at least one conversion event.

Raw data is available for download by clicking the download icon in the upper right hand corner of theEvents graph.

Please see Downloading Raw Usage Data for more information on the available data.

The Diagnostics Tab

The Diagnostics Tab consists of two sections: Zapp Performance and Zapp Errors.

Zapp Performance is represented in two graphs. The first, Performance, displays the overall average time to first page for the selected time period to the left of the graph.

The graph, in turn, provides the average Time to First Page, Application time, and Network time on a day-by-day basis. These three metrics are defined as follows:

Application - The time it takesthe virtual browser on the Capriza Runtime to load the source application, including automations, until it arrives on the first page included in the Zapp. In other words, the response timeof the source application.

Network -The time it takesthe mobile device to connectwith the virtual browser. This may vary depending on thequality of the network to which the user is connected.

Time to First Page -The time until the user seesthe updated MVP of the Zapp, the first page on the mobile device following login and any automations.

Hovering over a specific spot in the graph displays the breakdown of each metric for that specific day.

Note: Each of these processes happen in parallel, so the numbers should not be summed together.

The second graph, Distribution, includes, to the left, the percentage of Zapp runs for the selected time period where Time to First Page was under six seconds.

The line graph displays the percentage of Zapp runs where Time to First Page was equal to a particular value. Hovering over a point on the graph displays the percentage of runs for that value as well as the percentage of runs that were less than that value (represented by the shaded area of the graph).

Raw data is available for download by clicking the download icon in the upper right hand corner of the Zapp Performance section.

Errors

Please see the articles Monitoring Errors and foran overview of these metrics.

Prior to pushing your Zapp to Production, it is imperative that you first complete testing. Testing your Zapp will enable you to find misconfigurations and edge cases that would later cause errors as well as improvements that can be made to the user experience. This article covers our recommended best practices for testing.

Testing Your Zapp within the Capriza Designer

Before distributing your Zapp to a test group of users, you should first perform initial testing via Test mode in the Capriza Designer. To access test mode, click the Test icon in the toolbar.

Test Settings

Test mode allows you to verify the functionality of your Zapp as it will behave in the hands of users on their devices on the right-hand side, while showing the actions taken on the Zapp in the virtual browser on the left-hand side.

You may restart the Zappat the login page or first page (depending on settings) via the Start Over icon in the upper right hand corner.

Various settings are also available in the Test Settings dialog to enable you to better evaluate the login and caching settings of your Zapp and the associated end user experience. Please refer to for further details.

Run through all possible workflows in your Zapp multiple times with different user logins and types and different combinations of settings enabled.

Things to look for while testing include:

Does the Zapp perform the desired business process in the packaged application?

Have you captured all the screens possible in the desired business process?

Are warnings or error messages captured?

Does the Zapp work properly for different types of users with different permissions?

Do you encounter any errors when navigating through the Zapp?

How is the end user experience upon subsequent authentications with saved credentials and cookies cached?

If you've configured caching for your first page, have you chosen appropriate controls to configure as interactive?

Zapp Test Group

After completion of testing within the Designer, you should publish your Zapp and distribute itto a subset of users. Not only will this enable you to catch issues with user permissions or experience not seen in the Designer, but it is also a great opportunity to obtain feedback directly from the people who will be using you Zapp.

In general, the users you choose should enable you to:

Test your Zapp with Different User Roles/Accounts

Make sure that your test group includes multiple types of users who have different access permissions to the system you are zapping (admins, regular users, etc.) to ensure that the different roles are accounted for and that the Zapp works well across all user types.

Different user types may have different views of the same application. For example, admins may be able to view more fields or columns or permitted to take more actions than a regular user. If you grab a control that only some types of users are able to see or use, make sure the control is optional so as not to cause unexpected errors in the zapp.

Testing your zapp with different user types will help identify these differences and make sure all users have a great experience.

Test Across Devices

Zapps execute with a modern user experience on any platform or form factor that runs a modern browser. Zapps also adapt to any form factor, including smartphones, tablets, and desktops, providing a consistent and rich user experience.

Ensure the users within the test group reflect the variety of device types and OSs that are used throughout your organization. By testing across multiple devices, you can make sure the Zapp UI works well across different screen sizes and, for example, is not stretched or squeezed.

The Time Entry universal micro app assumes that each project row in the timesheet table also includes an option to delete a specific row from the table.

Each project row includes a swipe action to delete the specific row.

Executing the Delete action in the Zapp will delete this specific project row in the entire timesheet for all days represented in the table.

The delete button action may or may not lead to a delete confirmation page on the web application. If the delete action triggers a delete confirmation pop up, the micro app offers a corresponding mobile page that can be easily attached.

this article

Some web applications (SAP, for example) do not offer a delete confirmation step, therefore you might wish to provide a mobile-side delete confirmation pop up to make sure the user does not delete a project row by accident.

To enable the mobile-side confirmation pop up, open the button ILE, scroll down and turn on Mobile side confirmation.

In the text field you can enter any message you would like to display to the user. The message may include simple HTML tags such as <br> to add some space between sentences.

The messagewill display in a popup modal with a standard OK and Cancel buttons.

If you choose to enable the mobile side confirmation for the Delete Project button, the Delete Confirmation page is not required and may be removed from the Zapp.

This mobile-side confirmation popup can be used in other scenarios where you would want to make sure that the user is sure about the action he is taking.

Learn more about how to leverage design patterns in universal micro apps in .

Different actions are available for draft v. published Zapps. The following table enumerates these differences.

Draft

Published Zapp

Editing

Distributing to Users

Updating the URL

New Version

Archive

Cloning

Release to Production

Delete

When building a Time Entry Zapp, the weekly view can be customized and styled to match your needs.

Styling the weekly view

To style the weekly view of the timesheet table, go to Style mode and select the weekly view.

In the Properties tab, you can choose to change the background color of the header and font color of the days text.

In addition, you can choose to change the selected day font color, background color and underline color. By default, the selected day font color is the brand primary color and there is not background or underline color.

Each day in the weekly header can be represented by up to 3 lines of text. The most common views are a single line of text representing the day of the week:

Or two lines of text representing the day of the week and the day of the month:

You can control the text style of each line of text separately.

By default, the text representing each day in the weekly view header is dynamic and based on each column header in the timesheet table in the web application. For example, if the column header text is Mon 8/8, that will be the text that will appear in the weekly view.

The dynamic column header text will be presented in one line and will use the First Text styling.

The text can be split into two (or three) lines using a short script. The header text is split to two lines (day and date) out of the box for Zapps built on SAP and PeopleSoft applications. If youre building a Time Entry Zapp on a different system, please contact your Customer Success Manager so this option can be enabled for your specific system.

In addition, the weekly view text can be static on the mobile side. To do so, select the weekly view and go to the ITEMS tab. The placeholder text of each column header shows the dynamic text that appears based on the web application. You can override that by typing in any static text you would prefer.

Showing the current day or the selected day

By default, the timesheet table will show the first day of the selected period. It is possible to associate between the weekly view header and the calendar so we will know to select and highlight either the current day or the day that was selected in the calendar.

For example, assume that today is August 8 and youre viewing the week starting on August 7. The day view of August 8 will be selected.

Alternatively, if you select to view the week starting on August 14 by selecting August 16 from the calendar, then August 16 will be the selected day.

This capability is provided out of the box for Time Entry Zapps built on top of SAP and PeopleSoft applications. If youre building a Time Entry Zapp on a different system, please contact your Customer Success Manager so this option can be enabled for your specific system.

For devices not supporting TouchID (or if a user doesn't wish to enable Touch ID), users can instead configure a 4-digit password to be used as a second layer of authentication when re-opening WorkSimple. The below screens illustrate the user experience. Please contact your Customer Success Manager to configure this option.

To save your Zapp, click on the "Save Draft" button in the upper righthand corner of the Designer.

Publish

In addition, if you attempt to exit the Designer without saving, you will be prompted to save your Zapp or exit without saving.

Once saved, your Zapp will appear in the Zapp Owner's WorkSimple. The Zapp will also appear in the Capriza Dashboard with "(draft)" written next to the version number.

The menu for the draft version of your Zapp will not include the option to move the Zapp to Production or to Update the URL, and you will be unable to distribute your Zapp. For either of these options to become available, you must first your Zapp via the Designer.

The purpose of this article is to provide a description of Caprizas Implementation Methodology. It is intended to convey the nature of the work performed by the Capriza team during a typical implementation and the key steps required to go live.

configuring login cookies

Zapp Use Case Workshop

As a best practice, we recommend all clients begin their Capriza engagement with an on-site Zapp Use Case Workshop to fully define the scope of the engagement and their long term plans for Caprizas solution. The workshop is broken into two sessions: Use Case Discovery & Mapping and Execution & Planning.

Once the workshop is complete, the Customer Success Manager delivers the Zapp Roadmap. This document serves as Caprizas recommendation, feasibility assessment, and summary of what was learned during the workshop:

Participant Insights

Use Case Proposal

KPI Definition per Use Case

Recommended / Prioritized Roadmap

Initial Go-Forward Plan

Audience: Project Manager, Business Process Lead, Technical Lead, Customer Success Manager, Customer Success Engineer

Kick-Off Call

The clients assigned Customer Success Manager (CSM), Customer Success Engineer (CSE), and Regional Sales Manager (RSM) organize an initial project kick-off call to confirm high level project goals and requirements, project team roles and responsibilities, communication protocols, and timeline dependencies.

During this call, we ask a series of questions that help us understand each of these components, as this will be critical to defining an overall project plan, the critical path, and timelines for key milestones. We also use this time to request appropriate user access, better understand existing infrastructure requirements, their development environment, identify potential hurdles and limitations, and communicate these to the client based on our diagnosis.

Audience: Executive Sponsor, Project Manager, Technical Lead, Customer Success Manager, Customer Success Engineer

User Experience Design

The CSM and Caprizas internal Design team work with the clients team to create design documentation. This process begins with a walkthrough session where the client demonstrates the source application that will power the Zapp and walkthrough the proposed use case, workflows, and success criteria. Based off of these inputs, the Capriza Design team creates mockups of the proposed Zapp based on our established UX Best Practices. The current design of the clients website/application and brand standards are taken into consideration to ensure a consistent user experience during the entire process.

Customers are encouraged to send written feedback on the mockups after running them by internal stakeholders. Capriza iterates on these mockups until the scope is locked.

Audience: Project Manager, Business Process Lead, Technical Lead, Customer Success Manager, Customer Success Engineer

Technical Deployment ArchitectureCapriza works with the client team to design and implement the appropriate deployment architecture necessary to integrate Capriza with your source applications and client deployment platforms. Through a series of sessions, our experts assist the client in identifying, designing, and building runtime environments, networking infrastructure, and client platform integration to satisfy corporate security policies and systems.

Audience: Project Manager, Networking Lead, Firewall Lead, Technical Lead, Customer Success Manager, Customer Success Engineer

Implementation

Zapp Configuration

Your assigned CSM and CSE are responsible for configuring the initial Zapp based on use cases identified in the identification and design phases of the project.

Unit Testing and Zapp Iteration

Your assigned CSE validates individual Zapp components by performing unit testing. Any discrepancies, issues, or updates needed are addressed in an iterative cycle followed by regression testing to ensure continued and desired functionality of all prior capabilities.

Zapp Styling

Styling updates are incorporated into the Zapp as detailed in the Design phase. This is typically done after the core controls and screens have been built.

Zapp Review & Testing

Once the initial Zapp version is completed, the Capriza CSM and CSE QA the Zapp to ensure that they are configured and functioning properly. Capriza reviews the Zapp with your team and makes updates and troubleshoot issues as required.

We also work with you to help develop a test plan. In general, the testing phase consists of the following key steps.

Use Acceptance Testing

Your CSM works with you to put together a user acceptance testing strategy. We recommend these tests include a subset of users representing various user types and groups to account for all Zapp variations. Feedback should be solicited from these test users as it relates to overall user experience, any technical issues, and the Zapps overall value.

Performance Optimization

During this phase, our team will also ensure that the performance of the Zapp we are delivering is optimal. We will run time tests on both the source application and Zapp to establish baseline metrics and implement various caching strategies, such as first page caching and, as appropriate.

Pre-Deployment Tests

Differences in Testing and Production environments may bring to light issues not observed during the Zapp building or UAT processes. To ensure a smooth Go Live, additional testing should be performed in the Production environment pre-deployment.

Training

Capriza provides training sessions for Zapp designers to enable them to design, build, and maintain existing and future Zapps. Training includes creation of training guides and a 2.5 Day Zapp creation training session. In addition, Capriza helps your team define the organizational functions needed to successfully manage and maintain the ongoing lifecycle of Zapps.

The Training workshop typically takes place in parallel with the implementation or testing phase.

Launch and Adoption

Launch and adoption consists of three key stages:

Release to Production Once the Zapps have been tested in the production environment they are ready for distribution to end users. Capriza assists with defining the distribution groups which should have access to the Zapps. In general, we recommend rolling the Zapp out in phases to continue collecting user feedback and iterating upon the Zapps design.

Communicate to Target Audience Capriza assists you in developing marketing and promotional materials to send to the target audience to raise awareness of the new Zapp.

Assess Adoption Capriza analyzes the ongoing growth of Zapp users against adoption targets, timelines, and other KPIs established at the beginning of the project and offer any recommendations for revisions that based on our learnings may increase adoption. Adoption Reviews are carried out on the following intervals:

5 days Post-Launch;

3 weeks Post-Launch;

2 months Post-Launch;

Quarterly thereafter.

Revisions and Enhancements

Once the project achieves successful adoption, Capriza continues to work with your team to assist with product enhancements and apply best practices as they evolve.

Future Zapps

Your Customer Success Manager works with you to plan rollout of future Zapps. Capriza resources are available to support your team, including technical guidance and troubleshooting, creation of mockups, distribution best practices, and adoption evaluation.

Please watch the following video for an example of building an Approvals Zapp.

For Approvals Zapps, you can utilize the Universal Micro App (Zapp Template) for Approvals in the Capriza Designer. See Introduction to Universal Micro Apps.

Before you start, familiarize yourself with building a Zapp using a template.

Click on New Zapp, then Approvals. Find the Approvals Universal Micro App that best corresponds to the specific type of approval you are building a Zapp for. (Select Basic Approvals for a generic template).

Steps for Publishing a Zapp

Enter the Zapp Name and Description. Enter the web address/URL of the business application for your approvals process (ie. SAP, Oracle, Peoplesoft, etc.)

Read Controls, Pages, & Connections to understand what makes up a Zapp.

Attach the login page by following the wizard. Reference the Attaching Controls Using the Wizard section in building a Zapp using a template on how to attach the controls on the details page.

When attaching controls, there will be cases where you need to strengthen the control. For details, please read Strengthening Basics.

Using new pages, attach the navigation steps required to get to the approvals table. For how to capture navigation steps, watch this video.

Attach the approvals table. For details on this step, read the Attaching a table section of this article.

Click on an approval item to go into the details view. By following the wizard, attach the necessary details of the approval item as well as the Approve and Reject action buttons.

Capture the Reject request flow.Click on the Reject button. If there is a requirement to put in comments, attach the Reject Expense Report page.

Otherwise, delete the page. Go to Pages. Click on the Reject page, and click Delete Page.

Click into another approval request. Capture the Approve request flow.If there is a navigation button to return to the approvals list. Attach the OK button on the Approve Success page to it. Otherwise, choose to Keep control as virtual and click it to return to the approvals list.

(Optional) If your approval process includes attachments that need to be viewed, you can link to it using the paperclip icon in the approval request details page.

Toggle to Styling mode. For more details on styling, visit the Styling Help Section.

Toggle to Test mode. Test multiple different approvals to make sure there are no errors. For details visit Testing Zapps. For tips on resolving errors, please visit How to Resolve Common Errors.

Publish the Zapp. To access the Zapp on your mobile device, visit the following pages

Downloading WorkSimple

Please refer to the following video for an example of building a Lookup Zapp.

For most Lookup Zapps, you can utilize the Universal Micro App (Zapp Template) for Lookups in the Capriza Designer. See Introduction to Universal Micro Apps.

Before you start, familiarize yourself with building a Zapp using a template.

Click on New Zapp, then Lookups. Find the Lookup Universal Micro App that best corresponds to the specific type of lookup you are building a Zapp for. (Select Basic Search for a generic template.)

Steps for Publishing a Zapp

Enter the Zapp Name and Description. Enter the web address/URL of the business application for your lookup process (ie. SAP, Oracle, Peoplesoft, etc.).

Read Controls, Pages, & Connections to understand what makes up a Zapp.

Attach the login page by following the wizard. Reference the Attaching Controls Using the Wizard section in building a Zapp using a template on how to attach the controls on the details page.

When attaching controls, there will be cases where you need to strengthen the control. For details, please read Strengthening Basics.

Using new pages, attach the navigation steps required to get to the initial lookup page. For how to capture navigation steps, watch this video.

Attach the lookup search function.

Attach the results table. For details on this step, read the Attaching a table section of this article.

Click on an item to go into the details view. By following the wizard, attach the necessary details for the item.

Toggle to Styling mode. For more details on styling, visit the Styling Help Section

Toggle to Test mode. Test multiple different approvals to make sure there are no errors. For details visit Testing Zapps. For tips on resolving errors, please visit How to Resolve Common Errors.

Publish the Zapp. To access the Zapp on your mobile device, visit the following pages:

Downloading WorkSimple

The User Flow report on the Home page of the Capriza Dashboard enables you to track user adoption within a particular workflow in your Zapp. To configure this report, click the "Configure Pages" button at the bottom of the panel.

A popup will surface for configuring the order of pages in your user flow. Click the up and down arrows to choose the Zapp pages and order you would like tracked. Up to five pages can be included. Once finished, click "Apply."

To view your report, mouse over each of the concentric circles in the graphic. The innermost circle will be the first page in your funnel with each subsequent page moving further toward the edge of the circle. The shaded portion of each circle indicates the percentage of users that navigated to that Zapp page from the previous one, with a fully shaded circle representing 100%. Mousing over each circle reveals a thumbnail of that Zapp page as well as the percentage of users that navigated to that page, the total number of visitors, and the average time to load the page in the past 14 days.

After the user downloads WorkSimple, he needs to log in to access the app. With Instant Login, when he opens WorkSimple for the first time, he will have to enter your work email to authenticate.Once this is done, he will not have to log in again unless he signs out of WorkSimple or the authentication cookieexpires (default cookie expiration is set at 60 days but can be updated by your Customer Success Manager).

After the user downloads WorkSimple, he needs to log in to accessthe app. With the username/password option, when he opens WorkSimple for the first time, he will have to enter his work email and a Capriza-provided password to authenticate. Once this is done, he will not have to log in again unless he signs out of WorkSimple or the authentication cookieexpires (default cookie expiration is set at 60 days but can be updated by your Customer Success Manager).

Please contact your Customer Success Manager to configure this login option.

After a user downloads WorkSimple, he needs log in to access the app. With the Quick Login option, when he opens WorkSimple for the first time, he will have to enter his work email and click a link sent to his inboxsign in. Once this is done, he will not have to log in again unless he signs out of WorkSimple or the authentication cookieexpires (default cookie expiration is set at 60 days but can be updated by your Customer Success Manager). This option is the recommended standard for WorkSimple authentication.

This workflow illustrates the experience when a user accessing the sign inemail from the same device that WorkSimple is installed on.

When the signinemail is accessed from a different device, a pin code must also be entered.

This article describes the process and common use cases for enabling access to Zapps via internet browser.

What Does it Mean to Access Zapps via Browser?

Accessing Zapps via browser refers to the ability for end users to access a Zapp using its URL without first needing to log into Worksimple. In this scenario, the user only needs to complete authentication for the source application itself or, if his or her authentication credentials have already been cached, may be instantly logged in.

Common Use Cases

The ability to access Zapps via browser is generally used for publicly available SaaS application, such as Salesforce, where your end users may already access the source application via any internet browser. Enabling Zapp access via URL is not recommended for applications behind your firewall.

User Experience & Known Limitations

Userscan navigate through your Zapp just as you would within WorkSimple; however, push notifications and native mobile functionality (e.g. click to email/call, open the device's camera/gallery, etc.) are unavailable.

Whenrun on desktop, standard desktop-keyboard interactions, such as using Tab to navigate between fields and Enter to click a Button, are supported out-of-the-box.

Only modern browsers are supported. Please refer to this article for a complete list.

Configuring Browser-Based Access

Accessing Zapps via browser is enabled by default. To view these settings, visit the Zapp versions page for your selected Zapp. Click on the version for which you would like to enable anonymous access, and click "Advanced Environment Settings."

The setting, "This zapp requires login to Capriza," controls Zapp accessibility via browser is unchecked by default unless you select the option, "This web application is behind a firewall," when creating your Zapp.

View and update your profileinformation inthe Profile tab in the Capriza dashboard.

You can edit your first name, last name, phone number, email, etc. You can also update your profile image and change your password.

Zapps are apps created using the Capriza platform. While capable of running on any modern browser, they are optimized for modern mobile devices.

Zapps can be based on any HTML-based application, and the business logic, access controls, and even design elements will be carried over from the source application.

case study

While Zapps can be created for virtually any use case, we recommend breaking Zapps into simple, 1-minute workflows that users can complete with a few inputs. Some of the most common Zapp use cases are as follows.

Support & Maintenance

Field employees that provide support and maintenance services often must fill out paper forms and then later input the same information into a back office system, leading to longer repair times and lower customer satisfaction. Mobilizing the enterprise systems utilized by these teams allows employees to capture maintenance requests in real time and even incorporate photos taken with their mobile devices.

For a real world example, please see our City of Los Angeles case study.

Enabling Sales

When traveling from prospect to prospect, entering meeting notes or even generating price quotes and invoices typically must wait until the salesperson is back in the office. By providing simple, mobile workflows, salespeople can easily access pricing and product information and update deal statuses, ensuring sales forecasts remain up to date.

To read how the Linde Group leveraged Capriza to empower their sales team, click here.

Fulfillment & Revenue Recognition

Relying on paper processes to track fulfillment and delivery of orders can mean large lag times before enterprise systems are updated and, as a result, delays in revenue recognition and even compliance issues. With the ability to track order fulfillment and even scan barcodes via a zapp, the enterprise can recognize revenue in real time and fulfill compliance requirements.

Please see the Titan Machinery Corporation for an example of this use case.

Employee Self-Service

Mobilizing enterprise applications also enables companies to provide self-service options for key HR functions, such as onboarding, open enrollment, PTO requests, etc. Not only do these zapps save the HR team time but they lead to increased employee satisfaction by providing the seamless mobile transactions people, in particular millennials, expect in today's smartphone-dominated world.

The first time you run a Zapp, you will be asked for your login credentials. When Save credentials on this device is checked, the next time the Zapp is run it will bypass this login screen and take the user directly to the first page of the Zapp. Unchecking this option will require the user to login every time the Zapp is run.

SSO

If is enabled for your Zapps, the login page will be skipped, and the user will be taken directly to the first page of the Zapp.