App Configuration. Version 6.0 August All rights reserved

Transcription

1 App Configuration Version 6.0 August All rights reserved

2

3 Contents CONTENTS... 1 INTRODUCTION... 2 LIMITATIONS... 3 FORM TYPES... 4 SYSTEM PARAMETERS... 8 ICONS IMAGE FOLDERS WEB SERVICES APP CONFIGURATION APP OPTIONS time@work App Configuration

4 Introduction This manual describes how can be configured for the iphone or Android App. The App enables users to enter data into Forms either online or offline on a mobile device. Forms may be configured for purposes such as: Expense Entry Time Capture (integrated with Timesheets) Form Entry for any purpose (absence request, procurement, invoice registration, etc.) The App is downloaded from the Apple App Store or from Google Play and then connected through the entry of credentials such as login name, password and server, to a particular instance of time@work, expense@work, or forms@work. All required data and logical rules are then downloaded from the server. The App currently allows: The creation of form transactions on the App Upload of transactions either for immediate submission into systems@work authorisation, review or posting workflow, or for further modification, confirmation and submission from the PSW Download of forms created in the PSW or imported into the PSW (e.g. credit card statements) for further modification and addition of transactions in the App Authorisation of forms Receipt of notification of actions to perform on Timesheets and Forms in the PSW When configuring systems@work for App use there are the following issues to consider: Form Types (constraints and options) System Parameters Image Folder time@work Reference Manual

5 Limitations The App works with Form Types defined in the or database. It is important to understand, however, that not all the functional features and logic that work in the browser-based PSW are available in the App. Note that the following statement uses terminology. In terms of workflow, the following options are not yet available: 1. Form Review 2. Proxy Submission and Employee Confirmation 3. Form Splitting 4. Partial Return 5. Selectable Routing In terms of data entry, the following options are not yet available: 6. Account Entry In terms of image handling: 7. Only one image (or PDF) and one audio file may be attached to each row 8. Form level attachments are not possible In terms of data control, the following options are not yet available: 9. Restriction of Expense Type by Form Type 10. Restriction of Analysis Values by Project 11. Restriction of Analysis Value by Task 12. Restriction of Analysis Values by Analysis Value App Configuration

6 Form Types Main Tab Suppress Submit Mobile Forms Append If, by default, you have configured the system so that transactions uploaded from the App are to be immediately submitted to authorisation, review or posting workflow, then you might want to suppress this for this Form Type, so that transactions uploaded from the Form Type are held as in progress data in the PSW for later submission. If you are not immediately submitting uploaded transactions from this Form Type to authorisation, review or posting workflow, then you should check this field if you want transactions from this Form Type to be appended to an existing in-progress form in the PSW that has the same Memo field. For example, if you are using Custom grouping in the App and you have uploaded expense transactions for a trip to Paris where the group is Paris then any subsequent transactions uploaded from the App also with a Group field time@work Reference Manual

7 of Paris will be appended to any existing in-progress form with a Group/Memo field of Paris. Suppress for App Creation Allow for App Entry Allow for App Authorisation Upload As Check this field to make this Form Type unavailable for form transaction creation in the App. Check this field if you want to synchronise the App with Forms created in the PSW. For example, a credit card form imported into the PSW could thereby be made available in the App for completion. Check this field if you want to be able to authorise forms of this type in the App. Sometimes you might want to create a more simple version of a Form for use in the App and to upload transactions from this more simple form into the more complex form used in the PSW. This is only possible if you are not immediately submitting transactions from this Form Type. time@work App Configuration

8 All forms used in the iphone App must include a non-validated text-type activity analysis field marked as both Header and Memo. You must make sure that Analysis Category is included as a column on the Column Sequence tab. time@work Reference Manual

9 All Form Types configured for use in the App must allow attachments of types jpg, pdf and m4a and only these types. App Configuration

10 System Parameters Additional Tab Web Services Submit Mobile Forms Web Services must be checked to enable communication between the App and the Web Services. Check this field if you want all data uploaded from the App to be submitted (i.e. for Authorisation or Posting) immediately. Otherwise Forms in Progress will be created, one for each Upload by default. Store with Errors Append Check this field if you will allow App users to upload data that contain errors. This is only possible if Submit Mobile Forms is not checked. Check this field if you are not submitting form data immediately and if you want each upload from the App to append to forms that have the same Group value. For example if you have established a custom group Paris, then you may upload several times to a form in progress where the Group field is Paris. time@work Reference Manual

11 Allow New Mobile Employee Default Mobile Employee Not Applicable Not Applicable App Configuration

12 Icons Icons may be associated with Form Types, Clients, and Projects (Expense Groups, and Expense Types in These icons are stored in the database and are downloaded to the App on first use and when changes are detected. Note that if you do not assign an icon to a Project then the Client icon is inherited by the Project. time@work Reference Manual

13 If you do not specify icons for Clients or Projects then a simple coloured circle will be shown in the App. time@work App Configuration

14 Image Folders Images captured by the App are uploaded and stored by Web Services in the folder specified on the Attachments tab of System Parameters. By default this should be: C:\Program Files WEB\linkeddocs (with the appropriate substitutions of or ). Reference Manual

15 Web Services The App obtains data from the SQL database using a web service that is separate from the systems@work PSW and requires a separate URL. The components for this web service are installed into a separate folder in the systems@work/web folder - Web Services. This folder contains a web.config file that governs the behaviour of the App s web services. In order that the App and web services should work, the following must be done: Installation IIS configuration web.config configuration HTTPS configuration Installation A web services option has been added to the standard installation wizard. time@work App Configuration

16 IIS Configuration A new virtual directory must be configured (as below). For further advice, contact systems@work Support. Web.config configuration The most important parameters are the following two: <add key="pswserver" value="sqlservername" /> <add key="pswdatabase" value="sqldatabasename" /> Note that in case you are using advance SQL security (see systems@work Installation Guide), the following tag must also be set: <TAWDbSet>... </TAWDbSet> This can be copied from the web.config file for the PSW. HTTPS Configuration Although the systems@work App can be used with HTTP rather than HTTPS, we strongly advise that HTTPS be used. time@work Reference Manual

17 If you choose to use HTTPS the web server must be secured by a certificate issued by an appropriate SSL authority (self-signed is insufficient). Here are some sample settings. Please contact systems@work Support for more guidance on this issue. time@work App Configuration

18 App Configuration Once a user has downloaded and installed the systems@work App he or she must enter the credentials that will enable him or her to use it with a corporate database. Login Name Password Company Server The same as used for accessing the PSW The same as used for accessing the PSW As configured during IIS Configuration (see above). time@work Reference Manual

19 App Options Language This is the language set or implied on the Employee s record and cannot be modified here. time@work App Configuration

20 Grouping Every transaction in the App is grouped using the field defined as the Header Memo field on the Form Type. By Month the group field is automatically set to the month to which the transaction date belongs, and cannot be altered By Week the group field is automatically set to the week to which the transaction date belongs, and cannot be altered Custom you can group transactions together in any way you choose (e.g. Paris, Miscellaneous, etc.) but this requires extra steps No Groups this is the easiest option. The group field is set to. Once data have been uploaded to the server they are presented (or submitted) in forms that contain all records with the same group value for the same Form Type. Recent Items This controls the number of recently used currencies you will see listed first when you must select a currency code in a multi-currency Form Type. It also controls the number of Projects/Expense Types listed first in the Project/Expense Type selection page. Save History Automatic Upload Confirm Automatic Upload Switch this on to store all uploaded transactions in the Uploaded page. Switch this on if you want automatically to upload data to the server when you are online and if you remain on the Home Page of the App and are inactive for more than five seconds. Switch this on if you want to confirm automatic upload each time it is initiated. Note that if you reject upload when asked to confirm, then automatic upload won t be invoked for an hour. Login Shows the user name you are logged in as. time@work Reference Manual