You are on page 1of 40
Entersoft MIS360 Entersoft MIS360 1.0 Technical Reference  Athens: 362, Syggrou Ave. & Evripidou, GR176 74

Entersoft MIS360

Entersoft MIS360 ® 1.0

Technical Reference

Entersoft MIS360 Entersoft MIS360 1.0 Technical Reference  Athens: 362, Syggrou Ave. & Evripidou, GR176 74

Athens: 362, Syggrou Ave. & Evripidou, GR176 74 Kallithea T:+30.210.9525.001 F:+30.210.9575.053 info@entersoft.gr

www.entersoft.eu

Thessaloniki: 21, Antoni Tritsi str., GR570 01 Pylaia

T:+30.2310.804.840 F:+30.2310.804.845 info@entersoft.gr

www.entersoft.eu

Sofia: Mladost 4 block 459, 1 st floor, BG1715 Sofia

T:+359.297.989.89

F:+ 359.297.539.76 info@entersoft.bg www.entersoft.eu

Bucharest: 13 George Galinescu Str., 4 th floor, Bucharest

T:+40.21.230.1201

F:+40.21.230.1200 sales@entersoft.ro www.entersoft.eu

Identity Document version 01.00.00 Software version 1.0.0 Last Update September 2011 Copyright © Copyright 2011 Entersoft
Identity Document version 01.00.00 Software version 1.0.0 Last Update September 2011 Copyright © Copyright 2011 Entersoft

Identity

Document version

01.00.00

Software version

1.0.0

Last Update

September 2011

Copyright

© Copyright 2011 Entersoft S.A. All rights reserved.

No part of this work may be reproduced, transmitted, stored, or used in any form or by any means, without the prior written permission of the publisher.

Regarding the present content …

It may be altered at any time.

It serves exclusively informative goals.

No guarantee whatsoever is handed out for the possible existence of mistakes or the wrongful use or non-wanted results produced by the use of processes hereby followed and recommended.

Athens: 362, Syggrou Ave. & Evripidou, GR176 74 Kallithea T:+30.210.9525.001 F:+30.210.9575.053 info@entersoft.gr

www.entersoft.eu

Thessaloniki: 21, Antoni Tritsi str., GR570 01 Pylaia

T:+30.2310.804.840 F:+30.2310.804.845 info@entersoft.gr

www.entersoft.eu

Sofia: Mladost 4 block 459, 1 st floor, BG1715 Sofia

T:+359.297.989.89

F:+ 359.297.539.76 info@entersoft.bg www.entersoft.eu

Bucharest: 13 George Galinescu Str., 4 th floor, Bucharest

T:+40.21.230.1201

F:+40.21.230.1200 sales@entersoft.ro www.entersoft.eu

Contents Entersoft MIS360 Identity 1 Copyright 1 Contents 2 1. IIS Server Installation 4 Prerequisites 1.1

Contents

Entersoft MIS360

Identity

1

Copyright

1

Contents

2

  • 1. IIS Server Installation

4

Prerequisites

  • 1.1 .......................................................................................................................

4

Setup procedure

  • 1.2 .................................................................................................................

5

  • 1.3 ..............................................................................................................

Directory security

10

  • 2. Version Upgrade

15

Entersoft MIS360

  • 2.1 ..............................................................................................................

15

IIS Application

  • 2.2 ..................................................................................................................

15

  • 3. Setting Up an iOS Device

19

  • 4. Customizing the application

23

  • 4.1 Menu

23

Reports tab

  • 4.1.1 ................................................................................................................................

24

Search tab

  • 4.1.2 .................................................................................................................................

24

  • 4.2 Agenda

25

  • 4.2.1 Today/30 days tab dedicated names

27

  • 4.2.2 Opportunities tab

27

  • 4.3 Insert / Update tasks

28

  • 4.3.1 User defined fields

30

Entersoft MIS360 4.3.2 Create a new task from the Contacts area..................................................................................... 32 4.3.3 Save an updated/new

Entersoft MIS360

  • 4.3.2 Create a new task from the Contacts

area.....................................................................................

32

  • 4.3.3 Save an updated/new task

..........................................................................................................

33

4.4

Contacts

...........................................................................................................................

33

  • 4.4.1 fields

User defined

......................................................................................................................

34

Save/Update

  • 4.4.2 a new Contact .........................................................................................................

35

  • 4.5 Related actions

.................................................................................................................

35

More info

  • 4.5.1 ...................................................................................................................................

35

Download details

  • 4.5.2 ........................................................................................................................

36

  • 4.5.3 Related reports ...........................................................................................................................

37

1. IIS Server Installation 1.1 Prerequisites Before installing the application “MIS360 x.x.x” in the server: Entersoft
  • 1. IIS Server Installation

1.1

Prerequisites

Before installing the application “MIS360 x.x.x” in the server:

Entersoft MIS360

Install .Net 3.5 Framework in IIS server. If it is already installed it appears in: Administrative Tools Server Manager Features .Net Framework 3.5.1

Execute the following commands in the command line in order to register the .NET installation on IIS:

 

o

In case of a x86 environment run:

 

%systemroot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis i

 

o

In case of a x64 environment run:

 

%systemroot%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis i

In case you have already installed .Net 4 in the

server

and you

want the

application to run

in a .Net 4

application pool in IIS, you must replace v2.0.50727 the above commands with v4.0.30319.

1. IIS Server Installation 1.1 Prerequisites Before installing the application “MIS360 x.x.x” in the server: Entersoft

Attention

The above commands install the version of ASP.NET that is associated with Aspnet_regiis.exe and update the script maps at the IIS metabase root and below. Only the script maps for applications that use an earlier version of ASP.NET are updated. Applications that use a later version are not affected.

1.2 Setup procedure Entersoft MIS360 Install the appropriate version of “MIS360 x.x.x setup.msi” according to your
  • 1.2 Setup procedure

Entersoft MIS360

Install the appropriate version of “MIS360 x.x.x setup.msi” according to your server specifications (x86 or x64 environment). In the first screen press Next, as is shown in the following image:

1.2 Setup procedure Entersoft MIS360 Install the appropriate version of “MIS360 x.x.x setup.msi” according to your

In the next step, select the IIS folder where the website will be installed and its name. We recommend using the default (at least for the virtual directory name). Then press Nextas in following confirmation screen:

1.2 Setup procedure Entersoft MIS360 Install the appropriate version of “MIS360 x.x.x setup.msi” according to your
Installation will take a few seconds: Entersoft MIS360 If the installation was completed successfully, then the

Installation will take a few seconds:

Entersoft MIS360

Installation will take a few seconds: Entersoft MIS360 If the installation was completed successfully, then the

If the installation was completed successfully, then the following message will appear in the last step. In the following

screen leave the “Launch MIS360 x.x.x” checkbox enabled and click “Close”.

Installation will take a few seconds: Entersoft MIS360 If the installation was completed successfully, then the

After the installation is completed, a new window will appear from which you must configure the settings required in order for the web application to communicate with the application server.

Entersoft MIS360 In the “Connection” tab you must set the application server’s location and the web

Entersoft MIS360

Entersoft MIS360 In the “Connection” tab you must set the application server’s location and the web

In the “Connection” tab you must set the application server’s location and the web server’s login credentials. More

specifically:

IP Address: You must set the application server’s IP address as it is defined in the CSConfig/ES00Server.config file.

Port: The TCP/IP port used from the application server, defined in the CSConfig/ES00Server.config file.

Database ID: The database’s code as is defined in the CSConfig/ESDBDef.xml file

User name, Password, Company, Brach: A user credentials that will be used in order for the application to login in the application server and execute all necessary functionalities. The user defined here must have administrative privileges in the application.

Entersoft MIS360 In the “Connection” tab you must set the application server’s location and the web

Note that

You can change any of the above settings at any time, by executing the ESWebConfigurator.exe file,

located in the web application’s bin folder. After you have made all necessary definitions you can test your settings by pressing the “Test Connection” button. If

your settings are correct then an “OK” pop-up message will appear on your screen (see following image), otherwise an error message will GUIDe you to alter your settings.

Entersoft MIS360 By pressing the “ASMX Service Test” button your default browser will try to open

Entersoft MIS360

Entersoft MIS360 By pressing the “ASMX Service Test” button your default browser will try to open

By pressing the “ASMX Service Test” button your default browser will try to open your web application’s service page. If

everything is correctly set in your IIS web application, you will see the following screen. Otherwise an error page will be displayed.

Entersoft MIS360 By pressing the “ASMX Service Test” button your default browser will try to open

In order for the web application to have the appropriate privileges for accessing and modifying files, you must define a local account that will be used by the service control manager. This account differs based on the web server’s operating system and the IIS’s version. By pressing the “IIS user” button a window will pop-up (it might take some seconds to load) showing you the proper Windows User Account for your web application to interact with the operating system. This information will be used in a later step.

Entersoft MIS360 Finally, in the “MIS360” tab, you should provide the application server’s and the second

Entersoft MIS360

Entersoft MIS360 Finally, in the “MIS360” tab, you should provide the application server’s and the second

Finally, in the “MIS360” tab, you should provide the application server’s and the second web application’s location and

name respectively. More specifically:

Application folder: You must define the application server’s location either by hand or by pressing the Select button.

IIS Data folder: This is the name of the web application that will be used for saving temporary data. This application has already been created in the IIS from the installation process and we recommend you keep the default value recommended by the setup.

Entersoft MIS360 Finally, in the “MIS360” tab, you should provide the application server’s and the second
Entersoft MIS360 The “Update” button is used for updating the application folder’s content with new reports

Entersoft MIS360

The “Update” button is used for updating the application folder’s content with new reports and commands that are used from the MIS360 application. By clicking this button, the application unzips the AppSrvFilesx.x.x.zip file’s

contents

in

the

ERP

application’s

ESFilters,

ESDashboards

and

ESScrollerCommands

folders.

The

AppSrvFilesx.x.x.zip” is located at the root folder of the ESMISServices website.

  • 1.3 Directory security

As mentioned earlier, in order for the web application to have the appropriate privileges for accessing and modifying files, you must define a local account that will be used by the service control manager. We will now use the windows user account found after pressing the “IIS user” button. You must go to your web applications’ folders created from the installation -they are located by default in the C:\inetpub\wwwroot folder- and give full permissions for this IIS user for the folders ESMISServices and ESMISData .

After you have set the appropriate privilege rights, you must define some basic properties for the newly created web applications. In order to do so you must first go to Start Control Panel Administrative tools

  • Internet Information Services (IIS) Manager. From there find the two sites that are located

under the “Web Sites” node in the IIS tree and for both folders follow the next steps:

 Go to the folder’s properties page (right click -> properties)  In the “Virtual Directory”
Go to the folder’s properties page (right click -> properties)
In the “Virtual Directory” tab press the “Configuration” button. Make sure that in the options tab the “Enable
parent paths” checkbox is enabled.

To enable the “parent paths” option in a web application installed in IIS version 7 you should click the website’s folder at the websites tree to the left and double-click the “ASP” option.

Entersoft MIS360 In the form that appears set the “Enable Parent Paths” to true: Only for

Entersoft MIS360

Entersoft MIS360 In the form that appears set the “Enable Parent Paths” to true: Only for

In the form that appears set the “Enable Parent Paths” to true:

Entersoft MIS360 In the form that appears set the “Enable Parent Paths” to true: Only for

Only for the ESMISServices web application, right click on the folder and from New select the Virtual Directory… option

as shown in the following image:

Entersoft MIS360 The above step must be followed three times, thus three new virtual directories will

Entersoft MIS360

Entersoft MIS360 The above step must be followed three times, thus three new virtual directories will

The above step must be followed three times, thus three new virtual directories will be created under the ESMISServices web application. The aliases for these three virtual directories must be the following:

DashboardImages: This virtual directory will be used for storing the dashboard items required from the application. Its path must point at the DashboardImages folder under the ESMISData web application in the IIS as shown in the following image.

misAnalysis: This virtual directory will be used for storing htm pages regarding multiline reports. Its path must point at the misAnalysis folder under the ESMISData web application in the IIS).

misDocs: This virtual directory will be used for storing the database’s related documents (located in the ES00Documents table). Its path must point at the DashboardImages folder under the misDocs web application in the IIS.

Entersoft MIS360 The above step must be followed three times, thus three new virtual directories will
Entersoft MIS360 Note that It is required to set read and write privileges for these three

Entersoft MIS360

Entersoft MIS360 Note that It is required to set read and write privileges for these three
Entersoft MIS360 Note that It is required to set read and write privileges for these three

Note that

It is required to set read and write privileges for these three virtual directories at the last step of their creation, by enabling the appropriate checkboxes (as shown in the image below).

Entersoft MIS360 Note that It is required to set read and write privileges for these three
Entersoft MIS360 To add a virtual directory in a website installed in IIS version 7, right

Entersoft MIS360

To add a virtual directory in a website installed in IIS version 7, right click your website’s folder at the websites tree to the left and click “Add virtual directory…”. Now fill the appropriate data in the appeared window as mentioned above and click “OK”.

Entersoft MIS360 To add a virtual directory in a website installed in IIS version 7, right
2. Version Upgrade The “Entersoft MIS” product consists of two different appli cations: Entersoft MIS360 
  • 2. Version Upgrade

The “Entersoft MIS” product consists of two different applications:

Entersoft MIS360

The “Entersoft MIS 360” iOS application downloaded from the App Store and

The application running in your IIS that communicates with your application server.

The upgrade procedure for each one of the above applications will be described in the following sections.

  • 2.1 Entersoft MIS360

The “Entersoft MIS 360” iOS application can be downloaded to iOS devices (iPhone/iPad/iPod) only from the Apple’s App Store. When Entersoft publishes a new version for this application, it will be available at the Apple’s App Store and the older version will no longer be available for download.

In case a device has already a version installed then this version must be upgraded through the iOS application upgrade

process to the latest version. If the device does not have “Entersoft MIS 360” already installed, then only the latest

version will be available for download.

  • Note that

This Entersoft MIS 360 application’s version number consists of two tokens: x.y, where x is the major

version number and y is the minor version number, e.g. 1.0, 1.1, 1.2.

  • 2.2 IIS Application

By the time a new version of the “Entersoft MIS 360” application becomes available at the Apple’s App Store a new IIS application will also be available for download from the Entersoft’ s FTP server. However there might be some cases where a new IIS version will be available and a new iOS application won’t be required. This will occur in cases new

scrollers, or dashboards or commands have been updated or inserted.

  • Note that

This IIS application version number consists of three tokens: x.y.z, where the first two follow the same numbering as the “Entersoft MIS 360” iOS application’s version number. The third token (z) is used for defining the IIS patch version’s number. For example if the “Entersoft MIS 360” version is 1.2 version, then the IIS application‘s corresponding version will be the 1.2.0. In case of only an IIS version upgrade, only the last token will be changed, e.g. 1.2.1, 1.2.2 … version.

Entersoft MIS360 In order to upgrade an installed IIS version you will need the new “

Entersoft MIS360

In order to upgrade an installed IIS version you will need the new “MIS360 x.x.x setup.msi” version according to your server specifications (x86 or x64). The steps you must follow are:

Go to Start -> Control Panel Add or Remove Programs, find the currently installed “MIS360”

application and click “Remove”.

Note that The application will be removed but all its settings along with all your customized
Note that
The
application will be removed but all its settings along with
all your customized files won’t be
affected.

Install the “MIS360 x.x.x setup.msi” file. In the following screen press the “Next” button:

Entersoft MIS360 In order to upgrade an installed IIS version you will need the new “

In the following screen set exactly the same values as the values you set when you installed the application for the first time (these values are described in section 1.2). Then press “Next” and start the installation.

Entersoft MIS360 Press “Close” while leaving the “Launch MIS360 x.x.x” checkbox enabled (in orderto open the

Entersoft MIS360

Entersoft MIS360 Press “Close” while leaving the “Launch MIS360 x.x.x” checkbox enabled (in orderto open the

Press “Close” while leaving the “Launch MIS360 x.x.x” checkbox enabled (in orderto open the configurations window).

Entersoft MIS360 Press “Close” while leaving the “Launch MIS360 x.x.x” checkbox enabled (in orderto open the

In the configuration window all your settings will remain the same as they were before the new version’s installation.

Entersoft MIS360 Finally press the “Update” button in the “MIS 360” tab to update the required

Entersoft MIS360

Entersoft MIS360 Finally press the “Update” button in the “MIS 360” tab to update the required

Finally press the “Update” button in the “MIS 360” tab to update the required files of your application server.

Entersoft MIS360 Finally press the “Update” button in the “MIS 360” tab to update the required
3. Setting Up an iOS Device Entersoft MIS360 In this section we describe the steps required
  • 3. Setting Up an iOS Device

Entersoft MIS360

In this section we describe the steps required to set up an iOS device so that it can communicate with the application

server. Before you set up the device you must first download and install the “Entersoft MIS 360” application at the

device from the Apple App Store.

After you have installed the version, you must select the “MIS 360” application’s icon from your iOS device’s desktop and the login screen will appear:

3. Setting Up an iOS Device Entersoft MIS360 In this section we describe the steps required

In the login screen you must fill the user’s username and password. These credentials must be the same as the ones defined in the ERP application. Once you do so, you must click the “Settings” button and fill the URL of your application server which can be either an IP address or a domain name, e.g. mail.entersoft.gr. If your server’s URL doesn’t start with the prefix “http://” or “https://” the application will automatically (and you won’t be informed for it)

edit your URL and save it as “http://<the_url_you_filled>/ESMISServices/misservices.asmx”.

If your server’s URL doesn’t follow the above format (e.g. because the virtual directory has been created in a different

path),

then

you

will

have

to

write

the

whole

URL

on

your

own,

e.g.

http://123.123.123.123:4567/MyServer/ESMISServices/misservices.asmx.

The first time the device connects to the server, the server will automatically create a new record in the ES00Device

table (with the registered MIS360 devices) and the following message will appear in the device’s screen:

Entersoft MIS360 The registered devices can be found from inside the ERP application from the “Devices

Entersoft MIS360

Entersoft MIS360 The registered devices can be found from inside the ERP application from the “Devices

The registered devices can

be

found from

inside the ERP application

from the “Devices Management”

View

(ESTMPDADevice\ES00Device_DEF) located in the Sales menu.

Entersoft MIS360 The registered devices can be found from inside the ERP application from the “Devices

For every new device the administrator must fill the device’s name (from the description field) and the device’s user.

These user’s credentials will be used for logging the MIS 360 o application in the iOS device. Once you finish editing this fields (all other fields are ignored) you must press the Save button, in order for the device to be activated.

Entersoft MIS360 The save button automatically activates a device only if the corresponding business rule is

Entersoft MIS360

Entersoft MIS360 The save button automatically activates a device only if the corresponding business rule is

The save button automatically activates a device only if the corresponding business rule is enabled. Before editing the

device’s form you must first go to Tools and configuration\Additional development tasks\Rules activation from the application’s
device’s form you must
first
go
to
Tools
and
configuration\Additional development
tasks\Rules activation from the application’s menu and enable the “Device checks” business rule, shown in
the following image:

If the device hasn’t been activated and the user tries to login the application, then the following message appears, thus informing the user that activation is pending.

Entersoft MIS360 The save button automatically activates a device only if the corresponding business rule is
Entersoft MIS360 Once the user logins the application, the user interface appears, whose language differ s

Entersoft MIS360

Once the user logins the application, the user interface appears, whose language differs based on the user’s language. More specifically the application’s language depends on the “Standardization code” column’s value. This column is available from Customization Organization Parameters Languages. These column’s value can be one of the following:

  If set to “el-GR” then the application’s language is Greek If set to “en-US”
If set to “el-GR” then the application’s language is Greek
If set to “en-US” then the application’s language is English
4. Customizing the application Entersoft MIS360 Entersoft provides a suggested solution regarding the MIS 360 applica
  • 4. Customizing the application

Entersoft MIS360

Entersoft provides a suggested solution regarding the MIS 360 application’s layout and functionalities, however because every company has its own workflows, the application can be customized in many levels in order to meet your specific needs. In the following sections we will describe the application’s distinct areas and the customization actions that can be applied.

4.1

Menu

The application’s menu is defined in the “MISMenu.xml” file which is located in the “Configuration” folder in the ESMISServices web application. The application reads this menu file in order to construct the tabs that assemble the Menu Bar (at the bottom of the application’s screen). By default the menu bar is composed of 6 menu items which are defined as corresponding elements in the MISMenu.xml file. The file’s basic elements are the following:

reportsScreen: Refers to the Report menu tab which contains the application’s dashboards

todayScreen: Refers to the Agenda menu tab which contains the representative’s agenda with his assigned tasks.

favoritesScreen: Refers to the Favorites menu tab, containing the user’s list of favorite items.

searchScreen: Refers to the Contacts menu tab, containing the company’s Contacts (legal or physical)

generalSearchScreen: Refers to the Search menu tab, available from the More menu option, where the user can make his searches (by default the user can only search for products).

settingsScreen: Refers to the Settings menu tab, available from the More menu option, where the user can define the application’s server address.

The user can change the order of the menu tabs or disable one or more of them (simply by deleting the corresponding elements in the xml file) or change their title in the application by changing the assigned value in the title attribute located under each menu element. Every time such a change takes place the user must re-login the application in order to view the new menu.

4. Customizing the application Entersoft MIS360 Entersoft provides a suggested solution regarding the MIS 360 applica

Attention

Be careful while you make changes to the xml files located in the Configuration folder because the

elements’ names are case sensitive.

In case of the Report and Search menu tab, the user can make a series of other definitions beside the ones described above. The customization of these two areas will be described in the following sections.

Entersoft MIS360 4.1.1 Reports tab As mentioned before the reportsScreen element is used for defining the

Entersoft MIS360

4.1.1

Reports tab

As mentioned before the reportsScreen element is used for defining the dashboards that will appear under the Reports tab in the application’s menu bar. Dashboards can be grouped into logical areas and these will be the distinct areas that will appear to the user once he selects to view the application’s reports. These report areas are defined under the <reportsScreen> element in the xml file. For each one of these report categories the following properties can be defined:

title: The report’s title

report: This element’s child elements will be the reports located under the specific category

The user can change the report category’s title, change the reports located under a category, hide one or more report

categories or include new report categories. If any new report categories are added, they will be shown in the application but with an empty icon.

In order to show a report in the application the following attributes must have values:

title: Sets the report’s title GID: This attribute’s value is used in order to identify distinct reports. Its value must be unique

group: The area where the dashboard is located. This area must exist in the ESDashboards folder in the ERP’s application directory

id: The folder where the dashboard’s definition is made. This must be a folder under the folder defined in the group attribute above

type: This attribute’s value must be set to “dashboard”

reportGroupName: There are some cases where a report category must be grouped into sub-categories. For example the Sales category is sub-divided into the “Retail-Analytics” and the “Sales Analytics” sub-categories. In those cases a value must be provided in this attribute, which will refer to the name of the different sub-

 

category in the menu. If no groupings are required then this attribute’s value must be set to empty.

4.1.2

Search tab

As mentioned before the generalSearchScreen element is used for defining the areas in which the user will make his searches. These areas are shown under the Search menu tab, which is visible by pressing the “More” option.

By default this tab allows the user to search only for products, but it can be updated in order to include searches for

other application’s entities such as customers, suppliers, tasks and others. Every such search location must be defined under a searchGroup element under the generalSearchScreen element. For every search area the following definitions must be made:

title: The name of the search area in the menu. The area’s name will appear once the user selects the search menu tab

Entersoft MIS360  listGroup : The area where the search view application’s folder is located. This

Entersoft MIS360

listGroup: The area where the search view application’s folder

is located. This area must exist in the ESFilters folder in the

listID: The name of the view that will be used for the search. This view must be located under the area defined in the listGroup attribute

titleColumn: When the user performs a search, the result set always shows two fields for each record. In this attribute we defined the name of the field in the view that will be shown in the first row for each record in the list of results. For example, when the user searches for products the first row in the result set always shows the

product’s description. This is because the titleColumn attribute’s value is set to Description which is the field in the view containing the product’s description

subTitleColumn: In this attribute we define the name of the field in the view that will be shown in the second row for each record in the list of results. For example, when the user searches for products the second row in

the result set always shows the product’s code. This is because the subTitleColumn attribute’s value is set to Code which is the field in the view containing the product’s code 1 .

paramName: The parameter name in the view located in the listGroup\listID area, that will be used by the user for inserting the search criteria.

itemGroup: Once the user selects a specific record from the result set, then a new window appears with more information regarding the record. The view that retrieves data when the user presses the “More info” button must be located in the area defined in this attribute (which must be under the ESFilters area in the application’s folder).

itemID: The view’s name that will be used for retrieving data when the user presses the “More info” button from the record’s form. This view must exist under the area defined in the itemGroup attribute.

param: The name of the parameter in the view defined in the itemGroup\itemID area that will be used for retrieving only the selected record’s data and not all data in the view.

keyColumn: The field in the view listGroup\listID that contains a unique value for the record and whose value will be assigned in the field defined in the param attribute. For example, when the user selects a product, then the parameter ISUDGID (defined in the property param) in the view ESTMPDAMap\ESTMPDAMapItem is assigned the column’s GID value (defined in the property keyColumn) in the view ESMobileQueries\ESItem.

4.2

Agenda

The agenda menu option provides essential information to the logged-in representative regarding his tasks and opportunities. The agenda is organized chronically in order for the sales executive to arrange his schedule and sort his priorities: the user can view his tasks for the current date or for the next 30 days as well as his opportunities.

1 The rest of the view’s listGroup\listID fields - excluding guid typed columns and including the columns defined in the titleColumn and subTitleColumn attributes - will be shown to the user when he selects to view a specific record’s data.

Entersoft MIS360 By default in the agenda menu option the user can view his assigned sales

Entersoft MIS360

By default in the agenda menu option the user can view his assigned sales appointment, collection, opportunities and sales tasks. These task types are defined based on their international id, from the company parameters, in the

“Synchronization Parameters with PDA” category. More specifically:

In the parameter “MIS 360 Sales appointment international id” the user must define the sales appointment task type’s international id

In the parameter

MIS 360 Collection international id” the user must define the collection task type’s

international id

In the parameter “MIS 360 Sales action international id” the user must define the sales action task type’s international id

In

the parameter “MIS

360

Opportunity international id” the user must define the opportunity type’s

international id.

Each tab in the agenda menu option besides the “New tasks” tab executes a view in order to retrieve data from the database server. The views that are used from these areas are the following:

Today

tab:

Tasks

shown

in

this

tab

are

records

in

the

view

“Today”

(ESMobileQueries\ESMyActsToday)

 

30days

tab:

Tasks

shown

in

this

tab

are

records

in

the

view

“Next

30

days”

(ESMobileQueries\ESMyActNextThirtyDays)

 

Opportunities:

Tasks

shown

in

this

tab

are

records

in

the

view

“Sales

opportunities

agenda”

(ESMobileQueries\ESMyOpportunities)

From the agenda menu option the user can view only his assigned tasks and not all tasks in the CRM application. This is possible because all of the above views have a parameter named with the special keyword “PDAUserGID” which is automatically assigned the logged-in users GUID. If this parameter doesn’t exist then all resources’ tasks will be displayed in the agenda.

Not all of the above view’s fields are shown in the agenda’s first screen but only those that have a specific name in the filter. These fields differ based on whether the task is shown under the Today/30 days tab or the Opportunities tab. The dedicated names in the filter for the first agenda screen are mentioned in the following sections.

4.2.1 Today/30 days tab dedicated names Entersoft MIS360 The view s’ fields shown in the first
  • 4.2.1 Today/30 days tab dedicated names

4.2.1 Today/30 days tab dedicated names Entersoft MIS360 The view s’ fields shown in the first

Entersoft MIS360

The views’ fields shown in the first screen (see image above) must have the following names in the filter:

Description: The task’s subject Start: The task’s planned start date Person: The task’s trade account Contact: The task’s Contacts Notes: Based on whether this field has a value or not, the special pen icon appears in the record (

)
)
  • 4.2.2 Opportunities tab

The view’s fields shown in the first screen (see image above) must have the following names in the filter:

Description: The opportunity’s subject

PlannedClosedDate: The opportunity’s planned closed date

Person: The opportunity’s account. By default this field is an expression the view containing the opportunity’s related person and his Contact in the form Contact@person

OppRevenue: The opportunity’s estimated revenues

OppProbability: The opportunity’s estimated certainty

Status: Based on this value the application can show the opportunity’s status code

Entersoft MIS360  Notes : Based on whether this field has a value or not, the

Entersoft MIS360

Notes: Based on whether this field has a value or not, the special pen icon appears in the record (

)
)
Entersoft MIS360  Notes : Based on whether this field has a value or not, the
  • 4.3 Insert / Update tasks

A user cannot only view his already assigned tasks, but he can also update their fields or even create new tasks and afterwards upload them in the back office application. The views used for presenting the tasks’ fields in the MIS360 application as well as the commands used for uploading an updated task or a new task in the application server differ

based on the task’s type.

Every time a user edits an already existing task or creates a new one, then all new given values must be transferred from the iOS device in the application server. In order to achieve this, a specific view is used as the “intermediate” for transferring data from the device to the ERP back office application. The views used for different task types are the following:

Sales appointment: The view used in this case is the ESTMEditApp view located in the

ESFilters\ESMobileQueries area

 

Collection or sales task: The

view

used

in

this case

is

the

ESTMEditTask

view

located in

the

ESFilters\ESMobileQueries area

 

Opportunities:

The

view

used

in

this

case

is

the

ESTMEditOpp view

located

in

the

ESFilters\ESMobileQueries area

Some of the fields in these views are shown in the new/update task form and must have specific names as their names in the filter. The dedicated names are the following:

Entersoft MIS360  ISUDGID : Used for storing the task’s GUID. This field will have the

Entersoft MIS360

ISUDGID: Used for storing the task’s GUID. This field will have the already assigned value in case of update or a new value in case of insertions.

SharedNotes: This field is used for storing the user’s comments, as they are inserted in the “Comment” field from the update task form. This view’s fields content will be used for inserting a new line in the task’s communication field.

Status: This field is used for storing the task’s state. It is used in both cases: insertion or update of a task.

Description: Used for storing the task’s subject. It corresponds to the “Subject” field in the new task form.

PlannedStartDate: Used for storing the task’s planned start date. It is used in cases the user creates a new

sales appointment or collection or sales task. PlannedClosedDate: Used for storing the task’s planned closed date. It is used in cases the user creates a new opportunity task.

OppRevenue:

Used in cases a user creates or updates an opportunity for storing the task’s estimated

revenues.

OppProbability: Used in cases a user creates or updates an opportunity for storing the task’s estimated certainty.

In case a user creates a new task, then in the new task’s form he must define the task’s account, its Contact and the account’s site (see image below). Whenever the user clicks a field on this form, then a list with available options appear in the screen from which the user can make his selection.

Entersoft MIS360  ISUDGID : Used for storing the task’s GUID. This field will have the

The views used for displaying a list of selections when the user clicks on the above fields are the following:

Entersoft MIS360  Account : The list displays the records in the ESMobileQueries\ESAccContacts view, with the

Entersoft MIS360

Account: The list displays the records in the ESMobileQueries\ESAccContacts view, with the following parameters (the names must be the ones stated below):

 

o

PersonName: The text given by the user in the search

o

Tasktype: The task’s international id

Contact: The list displays the records in the ESMobileQueries\ESAccContacts view, with the following parameters (the names must be the ones stated below):

 

o

Person: The selected account’s GID

o

Tasktype: The task’s international id

Site: The list displays the records in the ESMobileQueries, ESAccountSites view, with the following parameter(the names must be the ones stated below):

o

Person: The selected account’s GID

Besides editing the above fields, a user can also give values to all of the task’s user defined fields by filling the corresponding fields in the task’ s details form (described in the following section).

  • 4.3.1 User defined fields

The user defined fields form is available to the user when he clicks the “Edit details” button which is visible from the

insertion and the update task form. By default the application shows the task’s user defined fields: text 1

4, number 1…

... 4, date 1…4 and category 1…5. However these fields can be replaced with any of the task’s fields as long as they are

defined in the view with the following names in the filter:

Text fields: The fields shown in this area are defined in the view with name in the filter Textxxx Decimal fields: The fields shown in this area are defined in the view with name in the filter Numberxxx Date fields: The fields shown in this area are defined in the view with name in the filter Datexxx UDFx fields: The fields shown in this area are defined in the view with name in the filter Categoryxxx

Entersoft MIS360 In case a user selects to edit a udf field then a pop-up list
Entersoft MIS360 In case a user selects to edit a udf field then a pop-up list

Entersoft MIS360

In case a user selects to edit a udf field then a pop-up list will appear with all available values for this field from which the user can make his selection. This list of values may differ based on the field and is defined in the UDFScrollers.xml file which is located in the “Configuration” folder in the ESMISServices web application. All views that are associated with the same entity must be defined under the same group. All groups are defined in a detail element, where in the type attribute the user must define the entity’s type. The valid entity types are the following:

es.sap: The view will be used for all sales appointment tasks

es.opp: The view that will be used for all opportunity tasks

es.col: The view that will be used for all collection tasks

es.stk: The view that will be used for all sales tasks

In case other task types than the default ones are used (the default have international ID ES.SAP, ES.OPP, ES.STK and ES.COL), then you must replace the attribute taskid in the above file with the used tasks’ international id defined in the company parameters.

The view associated with each user defined field for a specific task category, must be defined under a field element. In the name attribute the user can set the field’s caption in the form as in the example below.

<field name="Extra details"> <scrollergroup>ESMobileQueries</scrollergroup> <scrollerid>ESTaskDnlDetails</scrollerid> <descriptionfield>description</descriptionfield> <codefield>code</codefield> </field>

For each view the following elements must be defined:

Entersoft MIS360  scrollergroup : The area where the view is located. This must be a

Entersoft MIS360

scrollergroup: The area where the view is located. This must be a folder under the ESFilters folder in the ERP application’s folder

scrollerid: The view’s code. The view must exist under the ESFilters\viewgroup area in the application’s folder.

decriptionfield: The field which will be shown in the form once the user makes his selection

codefield: The selected record’s key that will be assigned in the task’s field. This must be either a code or a GUID field.

  • 4.3.2 Create a new task from the Contacts area

When the user selects a specific person’s record, he can create a new task from the form’s related actions. Depending

on whether the selected account is a physical or a legal person, the required fields in the form differ. More specifically:

In case of a legal person, the customer’s field will be filled in the new task’s screen and the user will only have to define the person’s Contact and his site:

 In case of a legal person, the customer’s field will be filled in the new

When the user searches for a Contact then the ESMobileQueries\ESAccContacts view will be executed where the selected account’s GID will be assigned to the fFromPersonGID parameter

In case of a physical person, the Contact’s field will be filled in the new task’s screen and the user will only have to define the Contact’s account and the Contact’ site:

Entersoft MIS360 When the user searches for a Contact then the ESMobileQueries\ESAccContacts view will be executed
Entersoft MIS360 When the user searches for a Contact then the ESMobileQueries\ESAccContacts view will be executed

Entersoft MIS360

When the user searches for a Contact then the ESMobileQueries\ESAccContacts view will be executed where the selected Contact’s GID will be assigned to the fContactGID parameter

  • 4.3.3 Save an updated/new task

When the user finishes editing a new or an updated sales appointment task, he must press the “Upload” button located at the upper left corner of his screen in order for the task to be uploaded. If he does so, all values assigned in the fields of the views ESMobileQueries\ESTMEditxxx are transferred in the ERP application by executing the following view commands (located in the ESScrollerCommands folder):

Sales appointment: ESMobileQueries\ESTMEditApp\ESTMEditAppFromIphone Collection & sales task: ESMobileQueries\ESTMEditTask\ESTMEditTaskFromIphone Opportunity: ESMobileQueries\ESTMEditOpp\ESTMEditOppFromIphone

When the user presses the upload button, a record is also created in the ES00GPSLog table in the database in order to keep track of the iOS device user’s alterations and insertions. In this record we keep various data such as the task’s GUID, the user’s device id and the location and time of modification/insertion.

4.4

Contacts

In the Contacts menu tab option the user can view the company’s accounts and create new Contacts that are associated

to

a

specific

account.

When

the

user

searches

for

a

specific

account then the

ESMobileQueries\ESPersonInvestigation view is executed, where the user’s search value is assigned to

the SearchParam parameter in the view.

Entersoft MIS360 In case the user wants to create a new Contact, then he must first

Entersoft MIS360

In case the user wants to create a new Contact, then he must first select the account to which the Contact will be related in the new Contact form. The view used for showing the available company’s accounts (these are legal persons only by default) is the ESMobileQueries\ESAccContacts, where the application assigns in the FromName parameter, the text given by the user in the search.

When the new Contact is saved, it must be uploaded from the iOS device in the back office ERP system. In order to achieve this, a specific view is used as the “intermediate” for transferring data from the device to the ERP application. The view used for this purpose is the ESMobileQueries\ESTMNewContact, located in the ESFilters folder.

Some of the fields in the above view must have specific names as their names in the filter. The dedicated names are the following:

Person: This field is used for storing the selected person’s GUID to which the new Contact will be created. This field’s content is associated to the “Account” field in the new Contact’s form.

LastName: This field is used for storing the Contact’s last name as it is inserted in the “Surname” field from the new Contact’s form.

FirstName: This field is used for storing the Contact’s name as it is inserted in the “Name” field from the new Contact’s form.

CellPhone: This field is used for storing the Contact’s mobile phone as it is inserted in the “Telephone” field from the new Contact’s form.

EMailAddress: This field is used for storing the Contact’s e-mail as it is inserted in the “Email” field from the new Contact’s form.

Specialization: This field is used for storing the Contact’s specialization as it is inserted in the “Job title” field from the new Contact’s form.

Department: This field is used for storing the Contact’s department as it is inserted in the “Department” field from the new Contact’s form.

JobTitle: This field is used for storing the Contact’s activity as it is inserted in the “Activity” field from the new Contact’s form.

Besides editing the above fields, a user can also give values to all of the Contact’s user defined fields by filling the corresponding fields in the Contact’ s details form (described in the following section).

  • 4.4.1 User defined fields

The user defined fields form is available to the user when he clicks the “Edit details” button which is visible from the

insertion and the update task form. By default the application shows the task’s user defined fields: text 1

...

4, number 1…

4, date 1…4 and category 1…5. However these fields can be replaced with any of the task’s fields as long as they are

defined in the view with the following names in the filter:

Entersoft MIS360  Text fields : The fields shown in this area are defined in the

Entersoft MIS360

Text fields: The fields shown in this area are defined in the view with name in the filter Textxxx

Decimal fields: The fields shown in this area are defined in the view with name in the filter Numberxxx

Date fields: The fields shown in this area are defined in the view with name in the filter Datexxx

UDFx fields: The fields shown in this area are defined in the view with name in the filter Categoryxxx

Entersoft MIS360  Text fields : The fields shown in this area are defined in the

In case a user selects to edit a udf field then a pop-up list will appear with all available values for this field from which the user can make his selection. This list of values is defined in the UDFScrollers.xml file which is located in the “Configuration” folder in the ESMISServices web application. All views that are associated with Contacts must be defined under a detail element which has the value Contact in the type attribute.

  • 4.4.2 Save/Update a new Contact

When the user finishes editing a new Contact he must press the “Upload” button located at the upper left corner of his screen. If he does so, all values assigned in the fields of the view ESMobileQueries\ESTMNewContact are transferred in the ERP application by executing the following the ESMobileQueries\ESTMNewContact\ESTMNewPerson view command (located in the ESScrollerCommands folder).

  • 4.5 Related actions

Every time a user selects a specific record from the agenda or a specific Contact’s record from the list of Contacts or a specific record from the list of search’s records, then a list of related actions appear in a pop-up window. These actions may differ based on the task’s type and the entity and are described in more detail in the following sections.

  • 4.5.1 More info

The “More info” option appears when the user selects a specific task record from the agenda or a specific record from the search’s results. If he does so the application displays a new screen with all fields in the basic views (the agenda’s views mentioned in section 4.2 and the search’s views defined in the MISMenu.xml file) except from the GUID typed columns and the columns that have the following name as their name in the filter:

 Icon  Description  Start  Name  Name1  Notes  Subject  Description1

Icon

Description

Start

Name

Name1

Notes

Subject

Description1

Latitude

Longitude

InternationalID

phone

email

NoOfDocuments

addressphone

SharedNotes

End

OppRevenue

OppProbability

Person

  • 4.5.2 Download details

Entersoft MIS360

Except for the fields that are shown when the user selects the “More info” action, he can obtain more information regarding tasks or Contacts by selecting the “Download details” option. This option is available from the selected record’s actions and shows different data based on the entity (task or Contact) and its type (in the case of tasks).

The views used for each entity are defined in the TaskScrollers.xml file which is located in the “Configuration” folder in the ESMISServices web application. Each view’s definition must be made under a <scroller> element in the file, where for each view the user must define the following:

taskid: In this attribute we define the entity for which the view will be used. The distinct types that can be assigned in this attribute are the following:

o

ES.SAP: The view will be used for all sales appointment tasks

o ES.OPP : The view that will be used for all opportunity tasks o ES.COL :

o

ES.OPP: The view that will be used for all opportunity tasks

o

ES.COL: The view that will be used for all collection tasks

o

ES.STK: The view that will be used for all sales tasks

o

Contact: the view will be used in the Contacts area

Entersoft MIS360

scrollergroup: The area where the view is located. This must be a folder under the ESFilters folder in the ERP application’s folder

scrollerid: The view’s code. The view must exist under the ESFilters\Scrollergroup area in the application’s folder.

For example in the definition below, when a user select to download details for a sales appointment task, then the application will retrieve all visible fields in the view ESTaskDnlDetails, located in the ESMobileQueries area.

<scroller>

<taskid>ES.SAP</taskid>

<scrollergroup>ESMobileQueries</scrollergroup>

<scrollerid>ESTaskDnlDetails</scrollerid>

</scroller>

In case other task types than the default ones are used (with international ID ES.SAP, ES.OPP, ES.STK and ES.COL),

then you must replace the attribute taskid in the above file with the used tasks’ international id.

o ES.OPP : The view that will be used for all opportunity tasks o ES.COL :

Attention

Because every report’s data must be related with the selected record, all views that are defined in this xml file must have the entity’s GUID as a parameter with name ISUDGID in the filter. When the view is selected then the selected record’s GUID is parsed in the ISUDGID parameter in the view.

  • 4.5.3 Related reports

From this option the user can view more complex reports which contain more than one line in their result set. The “Related reports” action is visible from almost all areas in the application: from the agenda’s menu, the Contacts’s area and the search’s area.

The views used for each entity are defined in the AnalysisScrollers.xml file which is located in the “Configuration” folder in the ESMISServices web application. All views that are associated with the same entity must be defined under

the same group. All groups are defined in a group element, where in the name attribute the user must define the entity’s

type. The elements defined in this xml file are the following:

group name: In this element the user defines the distinct entities with which the views will be associated. The distinct types that can be assigned in name attribute are the following:

o ES.SAP : The view will be used for all sales appointment tasks o ES.OPP :

o

ES.SAP: The view will be used for all sales appointment tasks

o

ES.OPP: The view that will be used for all opportunity tasks

o

ES.COL: The view that will be used for all collection tasks

o

ES.STK: The view that will be used for all sales tasks

o

Contact: the view that will be used in the Contacts area

Entersoft MIS360

In case of the records in the search area, the user must define as the group’s name the token defined as the title of the corresponding <searchgroup> element in the MISmenu.xml

scrollergroup: The area where the scroller is located. This must be a folder under the ESFilters folder in the ERP application’s folder

scrollerid: The view’s code. The view must exist under the ESFilters\scrollergroup area in the application’s folder.

In the example below when a user selects to download details for an opportunity task, then the application will show all views defined under the group name ES.OPP. These would be the views ESOppItems and ESTaskDnlDetails located in

the ESMobileQueries area that will appear in the option’s list with captions “Opportunity line items” and “Subtasks” respectively.

<group name="ES.OPP"> <type name="Opportunity line items"> <scrollergroup>ESMobileQueries</scrollergroup> <scrollerid>ESOppItems</scrollerid> </type> <type name="Subtasks"> <scrollergroup>ESMobileQueries</scrollergroup> <scrollerid>ESFindSubTasks</scrollerid> </type> </group>

In case you don’t use the default task types (with international ID ES.SAP, ES.OPP, ES.STK and ES.COL), then you must replace the attribute taskid in the above file with the used tasks’ international id.

o ES.SAP : The view will be used for all sales appointment tasks o ES.OPP :

Attention

Because every related report’s data must be associated with the selected record, all views that are defined in this xml file must have the entity’s GUID as a parameter with name ISUDGID in the filter.

Entersoft MIS360 When the view is selected then the selected record’s GUID is parsed in the

Entersoft MIS360

When the view is selected then the selected record’s GUID is parsed in the ISUDGID parameter in the view.