Return-path: <sistemas@sicom.ws>
Envelope-to: israel@ssf.com.mx
Delivery-date: Wed, 27 May 2015 11:43:18 -0500
Received: from cocos2.grupoinda.net ([192.99.20.154]:39833)
	by vishnu.hosting-mexico.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256)
	(Exim 4.85)
	(envelope-from <sistemas@sicom.ws>)
	id 1YxeQE-001uUo-6m
	for israel@ssf.com.mx; Wed, 27 May 2015 11:43:18 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sicom.ws; s=default;
	h=Content-Type:Content-Transfer-Encoding:MIME-Version:Message-ID:Subject:From:To:Date; bh=FIO/P7HvdZ70Mw7JKEaEA9AOrIY6YaWQOHi/6z8IwYI=;
	b=E6cS9qc8LGWLGjqEe5mjTx/lW27kRddnPwwsWD1/+1Cgme7wgkc7SrNCmrnMOHoVItGS2ENMX2nJ6R6yZUo1hQcUyZq8dlQStKj7J01O/0Wmwpj8B4Zc2PvFQlkgTZoQ3Mpn2dwNDx/RIFp70yhdRCWwAw+HZydeQxdPn7X8yHQ=;
Received: from [177.240.169.60] (port=62593 helo=www.sicom.mx)
	by cocos2.grupoinda.net with esmtpa (Exim 4.85)
	(envelope-from <sistemas@sicom.ws>)
	id 1YxeQF-0006XB-HS
	for israel@ssf.com.mx; Wed, 27 May 2015 11:43:15 -0500
Date: Wed, 27 May 2015 08:57:48 +0000
To: israel@ssf.com.mx
From: SICOM Bug Tracker <sistemas@sicom.ws>
Subject: =?utf-8?Q?[G4S=5FModuloCpu_0001526]:_Cuando_la_UdR_esta_fuera_de_posici?=
 =?utf-8?Q?=C3=B3n_al_realizar_una_venta_el_registro_de_venta_no_es_limpia?=
 =?utf-8?Q?do.?=
Message-ID: <4b642893192d5d159179b68be2dbab63@www.sicom.mx>
X-Priority: 3
X-Mailer: PHPMailer 5.1 (phpmailer.sourceforge.net)
keywords: [G4S_ModuloCpu] Mejora en implementacion
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="utf-8"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cocos2.grupoinda.net
X-AntiAbuse: Original Domain - ssf.com.mx
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - sicom.ws
X-Get-Message-Sender-Via: cocos2.grupoinda.net: authenticated_id: mantis@sicom.ws
X-Spam-Status: No, score=1.0
X-Spam-Score: 10
X-Spam-Bar: +
X-Ham-Report: Spam detection software, running on the system "vishnu.hosting-mexico.net",
 has NOT identified this incoming email as spam.  The original
 message has been attached to this so you can view it or label
 similar future email.  If you have any questions, see
 root\@localhost for details.
 
 Content preview:  The following issue has been SUBMITTED. ======================================================================
    http://www.sicom.mx/mantis/view.php?id=1526 ======================================================================
    Reported By: esanchez Assigned To: esanchez ======================================================================
    Project: G4S_ModuloCpu Issue ID: 1526 Category: Mejora en implementacion
   Reproducibility: sometimes Severity: minor Priority: normal Status: assigned
    Target Version: 2.XX Origen de incidencia: Interno ======================================================================
    Date Submitted: 2015-05-05 11:06 GMT Last Modified: 2015-05-05 11:06 GMT
   ====================================================================== Summary:
    Cuando la UdR esta fuera de posición al realizar una venta el registro de
    venta no es limpiado. Description: Al querer realizar un servicio con un
   cliente que tiene posición GPS fuera de rango, el servicio no es permitido,
    pero sin embargo el registro de la venta no es limpiado y se guarda con los
    datos del cliente que fue introducido. Si inmediatamente se realiza un servicio
    sin identificar cliente, dicho servicio se guarda con los datos del cliente
    que fue introducido con la posición fuera de rango. [...] 
 
 Content analysis details:   (1.0 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
  0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
                             See
                             http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                              for more information.
                             [URIs: sicom.mx]
  1.1 DATE_IN_PAST_06_12     Date: is 6 to 12 hours before Received: date
 -0.0 SPF_PASS               SPF: sender matches SPF record
 -0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
                             domain
  0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
 -0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
X-Spam-Flag: NO


The following issue has been SUBMITTED. 
====================================================================== 
http://www.sicom.mx/mantis/view.php?id=1526 
====================================================================== 
Reported By:                esanchez
Assigned To:                esanchez
====================================================================== 
Project:                    G4S_ModuloCpu
Issue ID:                   1526
Category:                   Mejora en implementacion
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     assigned
Target Version:             2.XX
Origen de incidencia:       Interno 
====================================================================== 
Date Submitted:             2015-05-05 11:06 GMT
Last Modified:              2015-05-05 11:06 GMT
====================================================================== 
Summary:                    Cuando la UdR esta fuera de posición al realizar
una venta el registro de venta no es limpiado.
Description: 
Al querer realizar un servicio con un cliente que tiene posición GPS fuera de
rango, el servicio no es permitido, pero sin embargo el registro de la venta no
es limpiado y se guarda con los datos del cliente que fue introducido.
Si inmediatamente se realiza un servicio sin identificar cliente, dicho servicio
se guarda con los datos del cliente que fue introducido con la posición fuera
de rango.


Steps to Reproduce: 
1.- Configurar en el modo de servicio "Validar GPS".
2.- Tratar de realizar un servio identificando un cliente con posición fuera de
rango.
3.- Realizar un servicio sin identificar cliente.

====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2015-05-05 11:06 esanchez       New Issue                                    
2015-05-05 11:06 esanchez       Status                   new => assigned     
2015-05-05 11:06 esanchez       Assigned To               => esanchez        
======================================================================


