The purpose of this document is to assist in the configuration of Coins ERP+ to enable use of mobile Customer Care application. The configuration and setup should only be implemented once the M1x Integration Guide has been followed and completed which is a pre-requisite to the mCare configuration. The mCare configuration must be completed before UAT/LIVE deployment of mobile application to end users.
This document is intended to provide full instructions for the necessary setup required for mCare application. Furthermore, it may describe additional Inspection/Customer Care module setup that are client specific. This document 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 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_index.COINSMobile | COINSMobile | * | CAN-DO('HS_SUBLOC,HS_SUBCAT,HS_APPLOC,HS_NACHKITEMS,HSSTDISSUE,HSIWSTATCODE',ttco_index.coi_type) | CAN-DO('HS_SUBLOC,HS_SUBCAT,HS_APPLOC,HS_NACHKITEMS,HSSTDISSUE,HSIWSTATCODE',co_index.coi_type) | Yes |
| co_table.COINSMobile | COINSMobile | * | CAN-DO('HSPRTY,HSISSCAT,CCCANCREAS',ttco_table.cta_rtype) | CAN-DO('HSPRTY,HSISSCAT,CCCANCREAS',co_table.cta_rtype) | Yes |
| hs_chkitem.COINSMobile | COINSMobile | kco,hih_chklist,him_seq,him_chkitem,him_desc,his_category,vlo_code,his_subloc,him_subject,him_notes,rsp_dbrowid |
|
| Yes |
| hs_chklist.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 |
| hs_inslist.COINSMobile | COINSMobile | kco,hic_instype,hil_saleclass,hih_chklist,rsp_dbrowid |
|
| Yes |
| hs_instype.COINSMobile | COINSMobile | kco,hic_instype,hic_desc,hic_signreq,hic_signwho,rsp_dbrowid,hic_char__1,hic_char__2 |
|
| Yes |
| hs_qdefn.COINSMobile | COINSMobile | * |
|
| Yes |
| hs_qdet.COINSMobile | COINSMobile | * |
|
| Yes |
| hs_qval.COINSMobile | COINSMobile | * |
|
| Yes |
| sy_mobcfgdfn.COINSMobile | COINSMobile | * |
|
| Yes |
| sy_mobcfglk.COINSMobile | COINSMobile | * |
|
| Yes |
| sy_mobcfgval.COINSMobile | COINSMobile | * |
|
| Yes |
| sysdb.COINSMobile | COINSMobile | * |
|
| Yes |
| vp_location.COINSMobile | COINSMobile | * |
|
| Yes |
Adding ESB Process Publish
Creating a new ESB Process Publish
Note - root access required / KCO Specific
Go to the ‘System’ module settings.
Under ‘Enterprise Service Bus’, click ‘ESB Process Publish’.
Add a new process on the following list as shown below.
Bulk Add can be used as per the attached.
(Optional) - Once the processes have been added, the task data can be published. Select the process and tap on ‘Resend’
√ | Process | Endpoint | Fields |
| HSU900 | COINSMobile | hs_inspect:kco,hic_instype,hih_chklist,job_num,jph_phase,vwb_code,hin_insref,hin_insdate,hin_inspector,hin_status,hin_notes,hin_reason;vp_wbsdef:vud_code,vwb_sysstat,vwb_add__1,vwb_add__2,vwb_add__3,vwb_add__4,vwb_saleclass,hpg_group;hs_inspectHistory:hin_insref,hin_insdate,hin_inspector,hin_status,hin_notes;hs_issueInsHistory:his_ref,his_raised,his_status,his_priority,his_category,his_employee,his_desc,his_abstract,his_closed,his_notes,vlo_code,his_time,his_loguser,his_subcat;hs_insitem:hii_sseq,hii_insitem,hii_desc,his_category,vlo_code,his_subloc,hii_status,him_chkitem |
| HSU901 | TaskDataPublish | hs_task:kco,hta_complete,hta_person,hev_type,hta_key1,hta_ref,hta_stadate,hta_statime,hta_inst,hta_notes,hta_reason;vp_wbsdef:vwb_code,vud_code,job_num,jph_phase,vwb_sysstat,vwb_add__1,vwb_add__2,vwb_add__3,vwb_add__4,vwb_saleclass,hpg_group;hs_issueHistory:his_ref,hcm_ref,his_raised,his_status,his_priority,his_category,his_employee,his_desc,his_abstract,his_closed,his_notes,vlo_code,his_time,his_loguser,his_subcat;hs_issue:his_ref,his_key1,his_key2,his_key3,his_raised,his_status,his_priority,his_category,his_employee,his_desc,his_abstract,his_closed,his_notes,vlo_code,his_time,hcm_ref,his_loguser,his_subcat,his_sladate,his_slatime;hs_isstask:hta_ref,his_ref; |
| HSU903 | COINSMobile | * |
Adding ESB Process Queue
Creating a new ESB Process Publish
Note - Global
Go to the ‘System’ module settings.
Under ‘Enterprise Service Bus’, click ‘ESB Process Queue’.
Add a new process on the following list as shown below.
√ | Queue | Description | Program |
| TaskDataPublish | Publishing the Customer Care task data | ccpesb001.processMessage |
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.
(Optional)- Once the processes have been added, the task data can be published. Select the process and tap on ‘Resend’
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.
4. (Optional)- Once the processes are added, the task data can be published. Select the table and tap on ‘Resend all records’
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 mCare.txt click save
Once branding has been applied to CLIENT Coins ERP+ environment (importing roles & licenses 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 mCare and Coins ERP+, then Concurrent Users for that role will need to be included within the licence.
Each user (user of mCARE) requires the following role to be assigned to them (licensed to Role %CCMOB1 – mCare) as shown on following screenshots;
This is a Coins ERP+ Mobile requirement that needs to be configured by Coins Consultant/Customer on the Customer Coins ERP+ environment.
Setup Document Management
To link the photos/signatures submitted from the mobile devices, the following tables need to be added.
This is a Coins Mobile requirement that needs to be configured by Coins Consultant/Customer on the Customer Coins 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 mCare. Global.
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.
hs_inspect
hs_issue
hs_task
Test by attaching any document against the task on Coins ERP+ Customer Care/Inspections modules.
Go to Customer Care Workbench and locate a task.
Click on the paper clip icon.
Attach any document.
Test by attaching any document against the issue on Coins ERP+ Customer Care module.
Go to Customer Care Workbench and locate an issue.
Click on the paper clip icon.
Attach any document.
Mobile Configuration Definitions Settings (MCD)
The Mobile configuration MCD are a set of mobile parameters (similar to module) that are available after a Coins ERP+ upgrade or when initially setup by system (SYSADMIN) user. These are global available to all KCOS. The mobile parameters can be used to manage rich features on mCare and dynamically control the end user settings. The values set on each mobile parameter are KCO specific and they can be set in three different levels (Company, Contract & User) subject to business process.
System module> System Setup>Mobile Setup.
System Admin users can only configure the MCD onto an Environment.
DO NOT change the default values set in MCD.
Import/Export MCD
This is a Coins ERP+ Mobile requirement that needs to be configured by Coins Consultant/Customer admin on the Customer Coins ERP+ environment.
If some or all MCD are not available on Coins ERP+, it is possible to import them from attached for the version of mCare. Some of these parameters may be Coins ERP+ version dependent and may require a Coins ERP+ upgrade/fix/patch back.
If you are performing a LIVE update then you need export all parameters (CC*) from your non-live envionment and import it into your LIVE enviornment.
Copy value value from Export Mobile definitations.
Paste into the field for Import Mobile definitions.
Defining the Mobile Configuration Definitions (MCD)
The parameters can be set at 3 different levels. Company, Contract and User level. To identify which level an MCD can be set, you can check the field ‘Type’ within the Mobile configuration definitions.
If an MCD parameter is defined within a particular level, it will take precedence over the higher level.
