The purpose of this section is to assist in the configuration of Coins ERP+ to enable use of the mobile Forms application.

The configuration and setup should only be implemented once the M1x Integration Guide has been followed and completed, which is a prerequisite to the mForms configuration. The mForm configuration must be completed before UAT/LIVE deployment of the mobile application to end users.

These topics are intended to provide full instructions for the necessary setup required for mForms application. Furthermore, it may describe additional setup for the following elements in Coins ERP+: Contract, H&S, Plot Based, Service Visit) which are client specific.

Note: This section is not finalised and any of the information below is subject to change.

Database and Processes publishing

The system users and look up data for mobile application will be published onto M1x middleware via Coins ERP+ ESB publishing. This will entail creating some tables and processes. This is only possible when the Coins ERP+ system parameters and ESB Brokers have been setup as per the M1x Integration Guide.

Setting up Coins ERP+ ESB Database Publish

Creating a new ESB Database Publish Tables

Note - root access required / KCO Specific (1 min per KCO). The following will need to be set within each KCO if global KCO is not being setup.

Go to the ‘System’ module settings.
Under ‘Enterprise Service Bus’, click ‘ESB Database Publish’.
Add a new tables on the following list as shown below.
Bulk Add can be used as per the attached.
Once the tables are added, the reference data needs to be published. Select all tables and tap on ‘Resend All Records’

√	Table	Endpoint	Fields	Condition	Query	Prevent Duplicates
	co_table.COINSMobile	COINSMobile	*	CAN-DO(HSACTYPE,HSPRTY,HSISSCAT,CCCANCREAS',ttco_table.cta_rtype)	CAN-DO(' HSACTYPE,HSPRTY,HSISSCAT,CCCANCREAS',co_table.cta_rtype)	Yes
	dm_template.COINSMobile	COINSMobile	*			Yes
	hs_action.COINSMobile	COINSMobile	*			Yes
	sy_mobcfgdfn.COINSMobile	COINSMobile	kco,hih_chklist,hih_desc,rsp_dbrowid	$retire = hs_chklist.hih_retired;resutt = can-do('N',retire);	NOT hs_chklist.hih_retired	Yes
	sy_mobcfglk.COINSMobile	COINSMobile	kco,hic_instype,hil_saleclass,hih_chklist,rsp_dbrowid			Yes
	sy_mobcfgval.COINSMobile	COINSMobile	kco,hic_instype,hic_desc,hic_signreq,hic_signwho,rsp_dbrowid,hic_char__1,hic_char__2			Yes
	sy_mobfel.COINSMobile	COINSMobile	*			Yes
	sy_mobffield.COINSMobile	COINSMobile	*			Yes
	sy_mobform.COINSMobile	COINSMobile	*			Yes
	sy_mobfsec.COINSMobile	COINSMobile	*			Yes
	sy_mobfstat.COINSMobile	COINSMobile	*			Yes
	sy_moblink.COINSMobile	COINSMobile	*			Yes
	sy_mobsched.COINSMobile	COINSMobile	*			Yes
	sy_mobxitem.COINSMobile	COINSMobile	*			Yes
	sy_mobxlist.COINSMobile	COINSMobile	*
	sysdb.COINSMobile	COINSMobile	*
	wf_template.COINSMobile	COINSMobile	kco,wfp_code,wfp_desc,wfg_code,wfp_doc,wsp_status

Adding Global ESB DB Publish

Creating a new Global ESB DB Publish

Note - root access required

Go to the ‘System’ module settings.
Under ‘Enterprise Service Bus’, click ‘Global ESB DB Publish’.
Add a new process on the following list as shown below.

√	Table	Endpoint	Fields	Condition	Query	Prevent Duplicates
	dm_template.COINSMobile	COINSMobile	*
	menuparm.COINSMobile	COINSMobile	*

(Optional)- Once the processes are added, the task data can be published. Select the table and tap on ‘Resend all records’

Adding Global ESB Process Publish

Creating a new Global ESB Process Publish

Note - root access required

Go to the ‘System’ module settings.
Under ‘Enterprise Service Bus’, click ‘Global ESB Process Publish’.
Add a new process on the following list as shown below.

√	Process	Endpoint	Fields	Condition
	DMU900	COINSMobile	*
	SYU900	COINSMobile	*
	SYU901	COINSMobile	*

(Optional)- Once the process are added, the task data can be published. Select the process and tap on ‘Resend’

Roles and User Licence Requirements

Coins ERP+ will need to import the attached role for branding.

Requires SYSAdmin access/DAYPWD

System > User Maintenance > Import Roles
Copy and Paste Role from mForms.txt click save

Once branding has been applied to CLIENT Coins ERP+ environment (importing roles and licences installed) then the users of the mobile devices need the role to be configured against their Coins ERP+ username. All users need to be Coins ERP+ Named Users however if users are required to access both mForms and Coins ERP+, then Concurrent Users for that role will need to be included within the licence.

Each user (user of mForms) requires the following role to be assigned to them (licensed to Role %JCMF– mForms) as shown on following screenshots;

This is a Coins Mobile requirement that needs to be configured by Coins ERP+ Consultant/Customer on the Customer Coins ERP+ environment.

Document Management Setup

In order to link the photos or signatures submitted from the mobile devices, the following tables need to be added.

This is a Coins ERP+ Mobile requirement that needs to be configured by a Coins Consultant or the Customer on the Customer Coins ERP+ environment.

Note - The following tables will be created by the Coins ERP+ web service as soon as the category is called on Coins ERP+ or by mForms.

Creating a Document management link

Go to the ‘System’ module settings.
Under ‘System setup’, ‘Document Management Links’
Add the following tables and set the Base URL as coins.
sy_mobcfield
sy_mobcform
sy_mobffield

See screenshot below.

Once the above DM links have been added and documents have been sent back into Coins ERP+, the category maintenance links will automatically be created:

We will need to manually add in the description “Completed Mobile Form” for the sy_mobcform category.

mForms Configuration