Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,18 +1,33 @@
1		-==== Database Overview ====
	1	+==== **Database Overview** ====
2	2
3	3	Before connecting to the mobile database, ensure you have updated your SQL Management Studio, current working version is **20.2.37.0**. Take note to tick the checkbox option that says: **Trust Server Certificate**,** **when trying to connect. The IP address for the server is **172.30.0.6 **and** **database credentials can be found at [[https:~~/~~/vault.zoho.com/>>https://vault.zoho.com/]]. Below is a breakdown of some important tables that can be found in the database and their purpose:
4	4
5	5
6		-|Table Name|Description|
	6	+|**Table Name**|**Description**|
7	7	|[dbo].[mobileAppSettings]|This contains basic information required for the mobile app to run. It points the mobile app to a web service which is responsible for handling database operations and business logic. The service URL is specified in a field called, "**WebServiceURL**".** **Each mobile app must also be assigned a unique company id, which is stored in a field called, "**CompanyName**"; The format for this field must be as follows: **CODE@GUID**|
8		-| | |
9	9
10		-==== Google Play Store: ====
	9	+==== **Google Play Store** ====
11	11
12	12	In order to deploy an android application on the Google Play Store you'll need the following: (credentials can be found on ZOHO).
13	13
14		-URL: [[Google Play Store Login>>https://https:accounts.google.com]]
	13	+URL: [[https:~~/~~/play.google.com/console/developers>>https://play.google.com/console/developers]]
15	15	Username//: [[innovation@ebsphere.com>>mailto:innovation@ebsphere.com]]//
16	16
	16	+In Visual Studio, we need to configure / update the android manifest with the following information: (The manifest can be found at ebapp.android > properties > androidmanifest.xml)
17	17
	18	+|**Property Name**|**Example**|**Description**
	19	+|Application name|MWPF|Short alphabetic code which represents the client
	20	+|Package Name|com.globalkinetic.mineworks|Reverse domain name
	21	+|Version Number|160|Numeric value which increments at each deploy, not shown to the user
	22	+|Version Name|3.3|(((
	23	+Version number which is displayed to the user
	24	+)))
	25	+
	26	+Important! Ensure the following has been configured before rebuilding and deploying the application. The MainActivity class requires an "Activity" attribute with details that are specific to the client to are doing the deployment for. We also need to change the "**appsettings.release.json**" file to include a reference to the client record stored on the "**dbo.mobileAppSettings**" table mentioned previously; this is the reason the company code must be unique.
	27	+
	28	+After packaging the application, you will need to sign it. The key and / or credentials required for signing can be found in the corresponding client found on SharePoint (Usually in a folder called KeyStore, Keys etc): EB Sphere (Pty) Ltd Team Site - Documents\Teams\Innovation\Mobile Application.
	29	+
	30	+
	31	+
	32	+
18	18