6.1. General rules for working with tasksThe tasks in the merchandising system and the unified database of retail points of sale of the Customer’s company occupy a very important place. Using tasks, data is collected on the PDA by merchandisers, changes are made to the system database. Creating and editing tasks occurs using the WEB-interface of the system. On the PDA, the agent can view tasks and enter the necessary information into them. After synchronization, data from the PDA are recorded in the system database, and reports are generated from them. All operations with tasks are performed through the task list (Fig. 4.1). At the top of the list are filters with which you can select tasks. The following is a list of tasks. The list can be sorted by any column. To do this, click on the column heading.
The right side of the list contains icons for performing available operations with tasks: – Go to the list of points of sale types to set default values. The list will be filled only for those tasks for which the props “Detail by types of CTs” are not equal to “are the same for all types of points of sale”. The function “Detail by type of CT” is provided for setting matrices. The task will be reflected only in the list of assigned points of sale / contractors. – viewing task details. You can also view the details of the task by clicking on the description of the task. – edit task details. – delete a task. In the window for viewing the task details (Fig. 4.2), all task details and their default values are displayed. The buttons are located at the bottom of the window: – return to task list – edit task details – go to the list of points of sale types and values of the details of this task for each type for points of sale – copy the task. In this case, a new task will be created with the same details.
You can create a new task from the list of tasks using the “Create” button (Fig. 6.1). In the window for creating a new task (Fig. 6.3), you must enter the values of the general details of the task, select the type of task and specify the default values for the special details.
All tasks have common and special details. The general details are the same for all tasks, and the special ones vary depending on the type of task. The general details include:
- Operation – indicates which operation the task on the mobile component will relate to. In total, up to six operations can be configured. Usually included: “Daily Report”, “Merchandising Standards” and “Visit Tasks”.
- Task group – the group to which the task will relate. In sections, all tasks are grouped, which facilitates and speeds up work on a mobile device. Note: for the “Daily Report” operation, a rule is set for automatic display of tasks in the mobile component.
- Task type – data that a user with a mobile component can enter depends on the type of task. The system provides types of tasks that allow you to automate the collection of almost any information using the mobile component of the system. All types of tasks available in the system will be described below.
- Description – a description of the task that will be displayed on the mobile device. According to the description, the user must understand the meaning of the task and enter the relevant information into the mobile component.
- Storing of unique values for each point of sale – a sign that indicates that for this task in the mobile component, individual values for each point of sales will be displayed (for example, in the operation “Merchandising Standards” for each point of sales in the task the number of POSM will be displayed, which actually located at this point of sale).
- Valid until – the duration of the task. This parameter is controlled by the mobile component and after the specified date the task in the mobile component becomes unavailable.
- Task status – a feature by which the system determines the availability of a task for editing. It can take the values “Editing is allowed – it is not transferred to the PDA”, “It is transferred to the PDA, editing is partially prohibited”. If the sign “Transferred to the PDA, editing is partially prohibited” is set for the task, then editing the details of the task is available only to system administrators. This is done to avoid situations when the task is already used by users on mobile devices, and through the WEB-interface the details of the task are changed, which can distort the results obtained from the mobile component of the system.
- Detail by point of sale type – a sign by which it is determined whether the default values for a given task will be the same for all types of points of sale (task groups), or whether they will be different for each type of point of sale (task groups). If the values are different, then you need to go to the list of point of sale types and set the default value for this task for each type of point sale. In addition, you can specify in the list whether this task will be displayed for a given type of point of sale.
- Sort order – you can set the order of tasks so that more priority tasks are displayed first in the list.
- The default value – s a feature by which it is determined whether the task should store the previous values entered (often used during auditing).
6.2. Types of tasksThe system contains the following types of tasks: 1. Date output task 2. Task with date and time output These types of tasks are needed to enter the date and time. A calendar window pops up on the mobile application. 3. The task with the choice of options from the directory This type of task is used for tasks in which you need to select pre-prepared options. Pre-creating a directory with answer options. 4. A task with the output of up to 5 numerical parameters, and a comment This type of task is needed when you need to enter several numerical values for one position. 5. The task of entering up to 3 numeric parameters with a logical control of their value with the subsequent selection of the comment option (p.6.2.1.). 6. A task with the ability to enter a sign of availability, a comment (p.6.2.2.). 7. A task with the ability to enter a sign of availability, price and comment. 8. A task with the ability to enter quantities, prices and comments.
6.2.1. Task with 3 parameters, with logical control and commentaryThe full name of this type of task: “A task with input of up to 3 numerical parameters with logical control of their value with the subsequent selection of a comment option” (Fig. 4.4).
The task is intended to collect numerical information with the ability to collect up to three parameters simultaneously. In addition, after entering the first parameter in the mobile component, there is a logical control of the entered information according to a given rule. If the result of the control is negative,the user must select from the list the reason for the non-compliance with the rule. Examples of this type of task usage can be the task “Enter the price on scratch 25” or “Removing POSM balance”. In the first case, the user enters one numerical value and the check is performed according to the rule “Monitoring of the zero value by the first”. If the user on the mobile device leaves the price zero, then it is considered that this product is not at the point of sale and the user must select the reason for the lack of goods from the list. In the second version, the user enters the actual POSM balance at the point of sale, and two other numerical parameters (required and recommended quantities) are set via the WEB interface. After entering, the actual quantity is compared with the mandatory according to the rule “Monitoring the first value in the second”, and if the actual quantity is less than the mandatory, the user must select a reason from the predefined list. In addition to the general details, the filling rules of which are described in p. 4. of this instruction, a task of this type has special details: numerical values 1, 2 and 3. For each numerical value, the user can specify his description in the “Description of value” field and the value according to by default in the “Numeric value” field. The number of values for this task is determined by the fields “Description of the value”. How many descriptions are given – so many values will be displayed on the mobile device. In addition to three numerical values, this type of task has three more special attributes: “Option for processing values on a PDA”, “Reference code” and “Default value”. The requisite “Variant of processing values on the PDA” indicates which logical scenario will be executed on the mobile device. In total, the system provides for two scenarios: “Monitoring of zero value by the first parameter” and “Monitoring of the first parameter by the second”. The first scenario involves comparing the “Numeric value 1” attribute with 0. If “Numeric value 1” = 0, then on the mobile device a list of values from the directory indicated in the “Code of the reference” attribute appears. This scenario is used in the “Enter Scratch Price 25” task. The second scenario involves comparing the details “Numerical value 1” and “Numerical value 2”. If the value of the “Numeric value 2” attribute is greater than the value of the “Numeric value 1” attribute, a list of values from the directory indicated in the “Code of the reference” attribute will appear on the mobile device. Such a scenario is used in the tasks “Removing POSM residues”. The requisite “Сatalogue Code” is used to indicate the values from which directory will appear on the mobile device when a logical scenario is triggered. The requisite “Default value” indicates whether default values will be set for this task. If the default values are specified, then for each attribute “Numerical value” you can specify the default value that will be displayed on the screen of the mobile device. Specifying default values can significantly reduce the processing time of tasks, enabling the user of the mobile component to agree with the default value and not enter the value manually. At the same time, refusal to specify default values allows you to attract the attention of users to this task and to monitor its implementation.
6.2.2. Task with the ability to enter a sign of availability and commentThe full name of this task is “A task with the ability to enter a sign of availability, comment”. The task is intended to collect data on the presence of goods, POSM, equipment or the performance of any tasks, the result of which will be a Yes / No answer and a note to it. An example of such a task might be the question “Are there life:) packages”. The user of the mobile component answers Yes, if packets are present, or No – if not present. When creating a task with the type “Task with the ability to enter a sign of availability, comment” (Fig. 4.5), all general details and two special details are filled in. Special for this type of task are the details “Yes / No by default” and “Note by default”.
In the props “Yes / No by default” the default value is indicated, which will be highlighted in the mobile component. Correct filling of this parameter allows you to speed up the completion of this task on a mobile device. In the props “Default Note” attribute, you can specify the note that will be displayed on the mobile device. There you can write a response template, which the user of the mobile component will supplement with the necessary data.