TransactField App Security
TransactField AppThis topic is related to TransactField App. | Deprecated in 21.11
This feature was deprecated in 21.11.
This topic discusses the various security measures within TransactField App. For more information, see our security architecture document.
Accessing Security
The TransactField App has various levels of security:
- The first time you log in, you must be online, and your user-name and password are verified against Journey Manager.
- On subsequent logins:
- If you are online, you will always be authenticated against Journey Manager.
- If you are offline, you can still log in and be authenticated against an encrypted stored copy of your credentials.
Note: This means that if your server password has changed, you must continue using your old password offline until you log in online.
- If your session is inactive for a specified length of time (predefined in Journey Manager), the session will time out and you will be required to log in again.
- If you fail to log in successfully after a specified number of times (predefined in Journey Manager), the TransactField App data (including data not saved back to the server) on your mobile device will be permanently deleted.
- All the TransactField App data is securely stored with 128-bit encryption.
- All communication is through the 'https' protocol to avoid 'man-in-the-middle' attacks.
In Journey Manager, administrators can set up 'Form Work Group Support' which impacts the stage at which a group of users may access a form in TransactField App.
The stages of a form include one or more of the following:
- New forms - visible in the 'Forms' listing.
- Saved or Assigned Forms - visible in the 'Task List'.
- Completed Forms - visible in the 'History' listing
Next, learn how to configure TransactField App.