Return-path: Envelope-to: israel@ssf.com.mx Delivery-date: Tue, 26 May 2015 09:33:36 -0500 Received: from cocos2.grupoinda.net ([192.99.20.154]:56596) by vishnu.hosting-mexico.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.85) (envelope-from ) id 1YxFvC-001hYA-0I for israel@ssf.com.mx; Tue, 26 May 2015 09:33:35 -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=M8u3kkXyKXbIlEXtnKaW+sM9zVIUsmJItfz8Px27VRU=; b=Y6OFZXE7za9s/e8N8oAJELKkH02SsCn4W/Zd15O+1xHVy5t1IlnXXCSA5CiZH40Oa9NFc/V8wotpPtgzNGugs+Oow2vAoMQTUUUgF08RaG2NyCDIIwibcSj8ZO4/SExRc1YYP2wfRSbn1k/z/4LINerxrKFKfSrM+BSTQpY+CBM=; Received: from [177.240.169.60] (port=25954 helo=www.sicom.mx) by cocos2.grupoinda.net with esmtpa (Exim 4.85) (envelope-from ) id 1YxFvD-0001EX-2X for israel@ssf.com.mx; Tue, 26 May 2015 09:33:35 -0500 Date: Tue, 26 May 2015 01:48:12 -0500 To: israel@ssf.com.mx From: SICOM Bug Tracker Subject: [G4S_ModuloCpu 0001577]: Realizar una revision de condiciones a partir de un caso de uso Message-ID: <56f1861c34f6548863f833a7303a32c8@www.sicom.mx> X-Priority: 3 X-Mailer: PHPMailer 5.1 (phpmailer.sourceforge.net) keywords: [G4S_ModuloCpu] General 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=1577 ====================================================================== Reported By: rgarcia Assigned To: ====================================================================== Project: G4S_ModuloCpu Issue ID: 1577 Category: General Reproducibility: have not tried Severity: trivial Priority: normal Status: new origen_incidencia: Cliente ====================================================================== Date Submitted: 2015-05-26 01:48 CDT Last Modified: 2015-05-26 01:48 CDT ====================================================================== Summary: Realizar una revision de condiciones a partir de un caso de uso Description: Revisar bajo que circuntancias podria pasar que el consecutivo de ventas se reinicie (inicie en 1) y el consecutivo de movimientos no, (continue en el valor que iba). [...] Content analysis details: (1.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 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 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] X-Spam-Flag: NO The following issue has been SUBMITTED. ====================================================================== http://www.sicom.mx/mantis/view.php?id=1577 ====================================================================== Reported By: rgarcia Assigned To: ====================================================================== Project: G4S_ModuloCpu Issue ID: 1577 Category: General Reproducibility: have not tried Severity: trivial Priority: normal Status: new origen_incidencia: Cliente ====================================================================== Date Submitted: 2015-05-26 01:48 CDT Last Modified: 2015-05-26 01:48 CDT ====================================================================== Summary: Realizar una revision de condiciones a partir de un caso de uso Description: Revisar bajo que circuntancias podria pasar que el consecutivo de ventas se reinicie (inicie en 1) y el consecutivo de movimientos no, (continue en el valor que iba). El caso se reporta el Termogas y al parecer ocurrio justo despues de una actualizacion. Se tenian consecutivos de venta XXXX y movimiento 3001 Al ver el primer corte realizado. Se tiene el corte 179 que abarca desde la venta 1 hasta la 25, pero la venta 1 tiene referenciado el movimiento 3002. La idea es saber como puede reiniciarse el contador de ventas unicamente. folio movimiento 3633 venta 2 del corte 179 folio movimiento 3632 ultima venta 3631 del corte 178 ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2015-05-26 01:48 rgarcia New Issue ======================================================================