<!-- 
RSS generated by JIRA (8.1.3#801003-sha1:6b6f07cffadda9a0d6efe24639daed8ce94dcdd6) at Sat Feb 10 05:48:14 GMT 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Rivet Logic Corporation JIRA </title>
    <link>https://issues.rivetlogic.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.1.3</version>
        <build-number>801003</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[LRA-61] Create a hook to extend Liferay and provide User&apos;s address validation</title>
                <link>https://issues.rivetlogic.com/browse/LRA-61</link>
                <project id="10765" key="LRA">Liferay Apps</project>
                    <description>We need to develop this for Liferay 6.2 CE GA 1. Use this repository:&lt;br/&gt;
&lt;a href=&quot;https://svn.rivetlogic.com/repos/rivets/logicstacks/hrportal/branches/6.2%20CE%20GA%201/&quot;&gt;https://svn.rivetlogic.com/repos/rivets/logicstacks/hrportal/branches/6.2%20CE%20GA%201/&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
This should be a stand alone hook that uses a service developed by you. This service should validate address using google API:&lt;br/&gt;
&lt;a href=&quot;https://developers.google.com/maps/documentation/geocoding/&quot;&gt;https://developers.google.com/maps/documentation/geocoding/&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
When a user is created the hook will validate the provided User address and if it not valid will inform the user and provide options that are valid according to Google service.</description>
                <environment></environment>
        <key id="36029">LRA-61</key>
            <summary>Create a hook to extend Liferay and provide User&apos;s address validation</summary>
                <type id="3" iconUrl="https://issues.rivetlogic.com/secure/viewavatar?size=xsmall&amp;avatarId=11098&amp;avatarType=issuetype">Task</type>
                                            <priority id="4" iconUrl="https://issues.rivetlogic.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="5" iconUrl="https://issues.rivetlogic.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="6">Completed</resolution>
                                        <assignee username="katalina.marcos">Katalina Marcos</assignee>
                                    <reporter username="mcalvo">mcalvo</reporter>
                        <labels>
                    </labels>
                <created>Tue, 7 Jan 2014 10:54:20 -0500</created>
                <updated>Thu, 6 Feb 2014 07:23:23 -0500</updated>
                            <resolved>Thu, 6 Feb 2014 07:23:23 -0500</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="55477" author="mcalvo" created="Wed, 8 Jan 2014 07:06:30 -0500"  >Based on Katalina&amp;#39;s research looks like it is not possible to use Google API. It says: &amp;quot;it says &amp;quot;The Geocoding API may only be used in conjunction with a Google map; geocoding results without displaying them on a map is&lt;br/&gt;
prohibited&amp;quot;.&lt;br/&gt;
&lt;br/&gt;
We are now exploring the possibility to use USPS service instead:&lt;br/&gt;
&lt;a href=&quot;https://www.usps.com/business/web-tools-apis/address-information.htm&quot;&gt;https://www.usps.com/business/web-tools-apis/address-information.htm&lt;/a&gt;</comment>
                            <comment id="55542" author="mcalvo" created="Thu, 9 Jan 2014 10:16:16 -0500"  >Although we were able get a Web Tool ID from USPS when we testing their services we always get this error: &lt;br/&gt;
&amp;quot;API Authorization failure. User XXXX is not authorized to use API Verify.&amp;quot;&lt;br/&gt;
&lt;br/&gt;
We called support and they weren&amp;#39;t able to help much. Finally they suggested to open another account, we did that and still get the same issue. Although according to their User Agreement, their API should only be used to deliver USPS packages.&lt;br/&gt;
&lt;br/&gt;
</comment>
                            <comment id="55543" author="mcalvo" created="Thu, 9 Jan 2014 10:19:34 -0500"  >We also tried to use UPS validation service, but in order to get an access key for UPS web services an UPS Account for shipping is needed.</comment>
                            <comment id="55546" author="mcalvo" created="Thu, 9 Jan 2014 10:27:49 -0500"  >Let use the Google service, and integrate it with a Google Map, to display the address of the user being added in that map.</comment>
                            <comment id="55597" author="mcalvo" created="Sat, 11 Jan 2014 09:46:35 -0500"  >An update from USPS service: &amp;quot;Thank you for contacting the USPS Internet Customer Care Center. I will be happy to assist you with the application process. I apologize for any inconvenience, but at this the Address API&amp;#39;s can only be used in conjunction with USPS Shipping Services and is not intended for cleansing databases or batch processing.&amp;quot; </comment>
                            <comment id="55877" author="mcalvo" created="Tue, 21 Jan 2014 06:23:32 -0500"  >Katalina is needed on another project. Pablo Nu&amp;#xF1;ez is going to continue this project.</comment>
                            <comment id="55969" author="mcalvo" created="Thu, 23 Jan 2014 11:51:12 -0500"  >Also please take into account that this portlet should be named Address validator, make any required code changes to reflect that, but don&amp;#39;t change the SVN project name.</comment>
                            <comment id="56006" author="mcalvo" created="Fri, 24 Jan 2014 08:22:21 -0500"  >Additionally once the code is ready, remember to Enable the Security Manager, following the steps outlined here:&lt;br/&gt;
&lt;a href=&quot;http://wiki.rivetlogic.com/display/Liferay/Enabling+Security+Manager+for+Liferay+plugins&quot;&gt;http://wiki.rivetlogic.com/display/Liferay/Enabling+Security+Manager+for+Liferay+plugins&lt;/a&gt;</comment>
                            <comment id="56322" author="mcalvo" created="Tue, 4 Feb 2014 06:24:14 -0500"  >1) welcome-file-list  in web.xml - do we need these for portlets?&lt;br/&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;This could be removed in all plugins&lt;br/&gt;
2) We need RL copyright in all java, jsp, js files&lt;br/&gt;
3) Use a constant class for all the param names and double quoted strings&lt;br/&gt;
4) replace  e.printStackTrace(); with log statement in localserviceimpl</comment>
                            <comment id="56372" author="katalina.marcos" created="Wed, 5 Feb 2014 06:17:46 -0500"  >Completed:&lt;br/&gt;
&amp;nbsp;&lt;br/&gt;
1) Removing welcome-file-list in web.xml&lt;br/&gt;
2) Adding RivetLogic copyright in java, jsp, and js files &lt;br/&gt;
3)Adding class AddressVerificationConstants for some param names and double quoted strings &lt;br/&gt;
4) Replacing e.printStackTrace with log statements&lt;br/&gt;
&lt;br/&gt;
Another issues were addressed:&lt;br/&gt;
&lt;br/&gt;
1) Fixing an javascript issue: An error ocurred when an user click select without none selected address&lt;br/&gt;
2) If the api is not Google Geocoding, the view map url is not showed. Refactoring was needed.&lt;br/&gt;
3)If the values for longitude and latitude were null (this depends of the API) it was generating an exception</comment>
                            <comment id="56373" author="mcalvo" created="Wed, 5 Feb 2014 06:19:57 -0500"  >Please rename the portlet to Address validator</comment>
                            <comment id="56394" author="katalina.marcos" created="Wed, 5 Feb 2014 13:00:51 -0500"  >Renaming portlet to validator/validation instead of verification</comment>
                            <comment id="56408" author="katalina.marcos" created="Thu, 6 Feb 2014 07:23:23 -0500"  >The portlet was renamed. It was added to SVN repository as a new one.&lt;br/&gt;
The old project address-verification-portlet was removed from repository.</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                        <customfield id="customfield_11470" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_11170" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i00bmv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10070" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1886</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10021" key="com.atlassian.jira.plugin.system.customfieldtypes:datepicker">
                        <customfieldname>Resolution Date</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Wed, 5 Feb 2014 00:00:00 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            </customfields>
    </item>
</channel>
</rss>