Envelope-to: julio@ssf.com.mx
Delivery-date: Tue, 12 Jan 2016 21:46:47 -0600
Date: Tue, 12 Jan 2016 21:46:03 -0600
From: Rogelio Delgado <issuessicom@gmail.com>
Reply-To: noreply@108.161.137.201
To: julio@ssf.com.mx
Message-ID: <5695c87bcd46f_9203fe8a94fccbc13598f@develop.mail>
References: <merge_request_145@108.161.137.201>
Subject: G4S | Fix plantilla customer actualizar udr (#81)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5695c87bcb8c5_9203fe8a94fccbc1358c8";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
 
 Content preview:  New comment for Merge Request 81 http://108.161.137.201:9000/Rogelio/g4s/merge_requests/81#note_241
    Rogelio Delgado [...] 
 
 Content analysis details:   (-0.8 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: 108.161.137.201]
 -0.7 RCVD_IN_DNSWL_LOW      RBL: Sender listed at http://www.dnswl.org/, low
                             trust
                             [209.85.218.47 listed in list.dnswl.org]
  0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
                             (issuessicom[at]gmail.com)
 -0.0 SPF_PASS               SPF: sender matches SPF record
  0.0 WEIRD_PORT             URI: Uses non-standard port number for HTTP
  0.0 NORMAL_HTTP_TO_IP      URI: URI host has a public dotted-decimal IPv4
                             address
  0.0 HTML_MESSAGE           BODY: HTML included in message
 -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 RCVD_IN_MSPIKE_H2      RBL: Average reputation (+2)
                             [209.85.218.47 listed in wl.mailspike.net]
X-Spam-Flag: NO


----==_mimepart_5695c87bcb8c5_9203fe8a94fccbc1358c8
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

New comment for Merge Request 81

http://108.161.137.201:9000/Rogelio/g4s/merge_requests/81#note_241


Rogelio Delgado

Aqu=C3=AD solo est=C3=A1s contemplando el caso en que la primera celda es=
t=C3=A9 vac=C3=ADa, pero puede darse el caso de que por error no introduz=
can valor para la primera celda no tiene valor, pero las dem=C3=A1s si. E=
n ese caso no deber=C3=ADa ingnorar la fila, sino lanzar error pero con e=
sta validaci=C3=B3n la ignorar=C3=ADa y el usuario ver=C3=ADa que no se i=
nsert=C3=B3 su registro y no sabr=C3=ADa por que. Creo que la correcta fo=
rma de validar esto es si TODOS los datos mandatorios de una fila est=C3=A1=
n vacios, entonces si ignorar la fila y pasar a la siguiente, si existe U=
N SOLO dato mandatorio en una fila, se debe de realizar el proceso de par=
sing de la fila y lanzar los errores correspondientes.


----==_mimepart_5695c87bcb8c5_9203fe8a94fccbc1358c8
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html lang=3D'en'>
<head>
<meta content=3D'text/html; charset=3Dutf-8' http-equiv=3D'Content-Type'>=

<title>
GitLab
</title>
</meta>
</head>
<style>
  p.details {
    font-style:italic;
    color:#777
  }
  .footer p {
    font-size:small;
    color:#777
  }
</style>
<body>
<div class=3D'content'>
<p class=3D'details'>
New comment on diff for
<a href=3D"http://108.161.137.201:9000/Rogelio/g4s/merge_requests/81#note=
_241">SCGasPAR/SCGasPAR-web/src/main/java/mx/ssf/sicom/scgaspar/web/catal=
ogs/massiveData/CustomersUploadedFileOperations.java</a>
:
</p>
<div>
<p>Aqu=C3=AD solo est=C3=A1s contemplando el caso en que la primera celda=
 est=C3=A9 vac=C3=ADa, pero puede darse el caso de que por error no intro=
duzcan valor para la primera celda no tiene valor, pero las dem=C3=A1s si=
. En ese caso no deber=C3=ADa ingnorar la fila, sino lanzar error pero co=
n esta validaci=C3=B3n la ignorar=C3=ADa y el usuario ver=C3=ADa que no s=
e insert=C3=B3 su registro y no sabr=C3=ADa por que. Creo que la correcta=
 forma de validar esto es si TODOS los datos mandatorios de una fila est=C3=
=A1n vacios, entonces si ignorar la fila y pasar a la siguiente, si exist=
e UN SOLO dato mandatorio en una fila, se debe de realizar el proceso de =
parsing de la fila y lanzar los errores correspondientes.</p>

</div>


</div>
<div class=3D'footer' style=3D'margin-top: 10px;'>
<p>
=E2=80=94
<br>
You're receiving this notification because you are a member of the Rogeli=
o Delgado / G4S project team.
<a href=3D"http://108.161.137.201:9000/Rogelio/g4s/merge_requests/81#note=
_241">View it on GitLab</a>
</p>
</div>
</body>
</html>

----==_mimepart_5695c87bcb8c5_9203fe8a94fccbc1358c8--