<!-- 
RSS generated by JIRA (6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc) at Fri Apr 17 10:35:07 EEST 2026

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 add field=key&field=summary to the URL of your request.
For example:
http://jira.mobinets.com/jira/si/jira.issueviews:issue-xml/LS-41/LS-41.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Mobinets-JIRA</title>
    <link>http://jira.mobinets.com/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>6.1.4</version>
        <build-number>6159</build-number>
        <build-date>19-11-2013</build-date>
    </build-info>

<item>
            <title>[LS-41] Zain KW | Generic Connector Enhancement</title>
                <link>http://jira.mobinets.com/jira/browse/LS-41</link>
                <project id="14300" key="LS">L3 Support</project>
                    <description>&lt;p&gt;Customer wants enhancement in the Generic Connector and wants to add TAG as well for the shifting of an asset.&lt;/p&gt;

&lt;p&gt;Earlier the sequence is ACTIVE&amp;gt; GENERIC&amp;gt;PASSIVE&amp;gt;STATIC for the Serial in NEP.&lt;/p&gt;

&lt;p&gt;Now the PROPOSED CHANGE/ENHANCEMENT sequence: ACTIVE&amp;gt;PASSIVE&amp;gt;GENERIC&amp;gt;STATIC.&lt;/p&gt;

&lt;p&gt;We are parsing Serial Number under &#8220;Serial&#8221; column of Passive Data for Generic.&lt;br/&gt;
Now we need to work for the TAG as well.&lt;/p&gt;

&lt;p&gt;I suggest if we used below attribute of NEP for shifting purpose of TAG:&lt;/p&gt;

&lt;p&gt;Value	NEP Attribute&lt;br/&gt;
TAG 	Itembarcode&lt;/p&gt;

&lt;p&gt;Kindly check the above request and provide you valuable feedback.&lt;/p&gt;</description>
                <environment></environment>
        <key id="125908">LS-41</key>
            <summary>Zain KW | Generic Connector Enhancement</summary>
                <type id="10900" iconUrl="http://jira.mobinets.com/jira/images/icons/issuetypes/sales.png">CR</type>
                                                <status id="10013" iconUrl="http://jira.mobinets.com/jira/images/icons/statuses/generic.png">Cancelled</status>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="DSVirdi">Daljeet Singh Virdi</assignee>
                                    <reporter username="DSVirdi">Daljeet Singh Virdi</reporter>
                        <labels>
                    </labels>
                <created>Tue, 5 Nov 2024 05:02:25 +0200</created>
                <updated>Thu, 12 Feb 2026 05:41:59 +0200</updated>
                            <resolved>Thu, 12 Feb 2026 05:41:59 +0200</resolved>
                                                                    <component>NEP</component>
                        <due>Thu, 7 Nov 2024 00:00:00 +0200</due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                            <timeestimate seconds="0">0 minutes</timeestimate>
                            <timespent seconds="16200">4 hours, 30 minutes</timespent>
                                <comments>
                            <comment id="116009" author="dsvirdi" created="Wed, 27 Nov 2024 10:28:04 +0200"  >&lt;p&gt;Dear @Salim Ali Abubakar,&lt;/p&gt;

&lt;p&gt;Generic Connector introduced to reduce the number of small connectors with different Dump format.&lt;/p&gt;

&lt;p&gt;As mentioned in below sample case ,If the node discovered via BMC, it should come in NEP via IT xml import.&lt;br/&gt;
There is no need to import via Generic template. Because as per the current logic , if you import via Generic, it will show error as the preference given to Active Inventory over Generic (IT Inventory comes under one of the Active Inventory).&lt;/p&gt;

&lt;p&gt;Now If the time taking to provide the Serial to the asset is long, still it will be available in NEP IT Inventory for the financialization.&lt;/p&gt;

&lt;p&gt;Try to have a sample case where an Asset is not able to import in NEP having the TAG ID with below mentioned conditions :&lt;/p&gt;

&lt;p&gt;1)	Asset must not be present in Passive DB.&lt;br/&gt;
2)	Asset must not be coming via BMC discovery or any active Inventory.&lt;br/&gt;
3)	Asset must not be present in any of the Warehouse , where it can track with TAG ID.&lt;/p&gt;



&lt;p&gt;    NETWORKS TRANSFORMED&lt;/p&gt;

&lt;p&gt;Daljeet Singh Virdi| Senior Telecom Engineer&lt;br/&gt;
Mob: +91 9717304711&lt;br/&gt;
1102-1103, Tower C, Unitech Cyber Park, Gurgaon&lt;br/&gt;
daljeet.virdi@mobinets.com  |  www.mobinets.com    &lt;/p&gt;


&lt;p&gt;From: Salim Ali Abubakar &amp;lt;Salim.A@cybermak.net&amp;gt; &lt;br/&gt;
Sent: 25 November 2024 05:41 PM&lt;br/&gt;
To: Daljeet Singh Virdi &amp;lt;Daljeet.Virdi@mobinets.com&amp;gt;; Abir Messaikeh &amp;lt;Abir.Messaikeh@nuiva.com&amp;gt;; Medhat El Shenawy &amp;lt;Medhat.M@cybermak.net&amp;gt;&lt;br/&gt;
Cc: ALM Support &amp;lt;ALM.Support@cybermak.net&amp;gt;; support &amp;lt;support@mobinets.com&amp;gt;; L2_Team_Leb &amp;lt;L2_Team_Leb@mobinets.com&amp;gt;; Mohamad Ezzedine &amp;lt;Mohamad.Ezzedine@mobinets.com&amp;gt;&lt;br/&gt;
Subject: RE: ZKW | GENERIC TEMPLATE | NEW SEQUENCE ENHANCEMENT&lt;/p&gt;

&lt;p&gt;Dear Daljeet,&lt;/p&gt;

&lt;p&gt;As per a sample business case, &lt;br/&gt;
Consider an IT node that is discovered by BMC with a tag number manually imported through Generic template into the NEP with a Tag number which is given to the asset before being Serialized. &lt;br/&gt;
Note that sometimes the serialization may take a lot of time thus assets are provided with temporary Tag Numbers.  &lt;br/&gt;
Once the assets are serialized and imported into the NEP, Necessary changes to the assets should take place which will be the registering of the SN into the assets.&lt;/p&gt;

&lt;p&gt;Should you have any questions or require additional details, please feel free to reach out to me.&lt;/p&gt;

&lt;p&gt;Kind regards,&lt;/p&gt;

&lt;p&gt;Salim Abubakar,&lt;br/&gt;
ALM Support Team.&lt;br/&gt;
CyberMAK Information Systems.&lt;/p&gt;
</comment>
                            <comment id="116253" author="amessaikeh" created="Wed, 4 Dec 2024 15:14:24 +0200"  >&lt;p&gt;to be resumed in Q1  2025  upon management decision&lt;/p&gt;</comment>
                            <comment id="118099" author="nayoubi" created="Fri, 28 Feb 2025 05:50:05 +0200"  >
&lt;p&gt;WL   for changing the sequence between generic and passive: 5 days&lt;br/&gt;
+WL to add shifting base on tag nb from generic to passive: 3 days&lt;br/&gt;
+testing: 2 days&lt;/p&gt;</comment>
                            <comment id="127029" author="dsvirdi" created="Wed, 2 Jul 2025 10:17:58 +0300"  >&lt;p&gt;Dear @Hassan Abdine,&lt;/p&gt;

&lt;p&gt;Currently, the shifting is being performed based on the Serial Number, wherein Generic elements are given higher priority over Passive elements.&lt;/p&gt;

&lt;p&gt;Please note that there is no rule implemented based on Item Barcode.&lt;/p&gt;

&lt;p&gt;Kindly find the attached email containing the relevant documents outlining the rules based on Serial Number.&lt;/p&gt;

&lt;p&gt;For reference, Passive elements here refer to assets present in the Passive Database (DB).&lt;/p&gt;


&lt;p&gt;    NETWORKS TRANSFORMED&lt;/p&gt;

&lt;p&gt;Daljeet Singh Virdi| Senior Telecom Engineer&lt;br/&gt;
Mob: +91 9717304711&lt;br/&gt;
1102-1103, Tower C, Unitech Cyber Park, Gurgaon&lt;br/&gt;
daljeet.virdi@mobinets.com  |  www.mobinets.com    &lt;/p&gt;


&lt;p&gt;From: Hassan Abdine &amp;lt;Hassan.Abdine@nuiva.com&amp;gt; &lt;br/&gt;
Sent: 02 July 2025 11:33 AM&lt;br/&gt;
To: Daljeet Singh Virdi &amp;lt;Daljeet.Virdi@mobinets.com&amp;gt;&lt;br/&gt;
Cc: Abir Messaikeh &amp;lt;Abir.Messaikeh@nuiva.com&amp;gt;; Aurobinda Panda &amp;lt;Aurobinda.Panda@mobinets.com&amp;gt;; Mostafa Kalawoun &amp;lt;Mostafa.kalawoun@mobinets.com&amp;gt;&lt;br/&gt;
Subject: Re: Zain KW | Generic Enhancement for Passive DB elements&lt;/p&gt;

&lt;p&gt;Hi Daljeet,&lt;/p&gt;

&lt;p&gt;Could you please highlight the difference between the current rules/priority and the new ones?&lt;/p&gt;

&lt;p&gt;Thank you,&lt;br/&gt;
Hassan&lt;br/&gt;
________________________________________&lt;br/&gt;
From: Daljeet Singh Virdi &amp;lt;Daljeet.Virdi@mobinets.com&amp;gt;&lt;br/&gt;
Sent: Monday, June 30, 2025 12:00 PM&lt;br/&gt;
To: Hassan Abdine &amp;lt;Hassan.Abdine@nuiva.com&amp;gt;; Hassan Abdine &amp;lt;Hassan.Abdine@nuiva.com&amp;gt;&lt;br/&gt;
Cc: Abir Messaikeh &amp;lt;Abir.Messaikeh@nuiva.com&amp;gt;; Aurobinda Panda &amp;lt;Aurobinda.Panda@mobinets.com&amp;gt;; Mostafa Kalawoun &amp;lt;Mostafa.kalawoun@mobinets.com&amp;gt;&lt;br/&gt;
Subject: Zain KW | Generic Enhancement for Passive DB elements &lt;/p&gt;

&lt;p&gt;Dear @Hassan Abdine,&lt;/p&gt;

&lt;p&gt;Pl find the below new request shared by customer for Generic enhancement in terms of Passive DB assets.&lt;/p&gt;

&lt;p&gt;Kindly go through it and provide your valuable feedback for the same.&lt;/p&gt;

&lt;p&gt;I would like to clarify the logic for the Generic Connector &#8211; Shifting Passive Assets by Barcode, especially in light of some observed contradictions.&lt;br/&gt;
Please review the below refined and elaborated logic, and confirm if it aligns with your expectations &#8212; or advise if there are any comments or changes needed:&lt;br/&gt;
________________________________________&lt;br/&gt;
Passive Asset Handling via Generic Template&lt;br/&gt;
When a passive asset dump is loaded through the Generic Template, the system will behave as follows:&lt;br/&gt;
&#8226;	If the asset already exists in the mobile app passive inventory (based on ItemBarcode): &lt;br/&gt;
o	Priority will be given to the Generic Template Passive Asset details.&lt;br/&gt;
o	This means the asset&#8217;s attributes (Site ID, Category, Part No, Model, etc.) will be updated/overwritten using the Generic Template.&lt;br/&gt;
&#8226;	If the asset is later removed from the Generic Template: &lt;br/&gt;
o	The system assumes it is no longer being managed externally.&lt;br/&gt;
o	It will revert to using the mobile app inventory as the data source (if the asset still exists there).&lt;br/&gt;
&#8226;	If the asset reappears in a future Generic Template dump: &lt;br/&gt;
o	The system will again prioritize the Generic Template and update the asset attributes accordingly.&lt;br/&gt;
&#8226;	Important Note on Updates: &lt;br/&gt;
o	Passive asset attributes will only be updated when the asset is present in the Generic Template.&lt;br/&gt;
o	If it is removed from the template, the system will no longer apply updates from it and will rely solely on the mobile app inventory.&lt;br/&gt;
________________________________________&lt;br/&gt;
This clarification is to address the earlier confusion regarding how the system can prioritize the Generic Template and yet update passive asset attributes consistently &#8212; the key is updates only occur when the asset exists in the Generic template&lt;/p&gt;
</comment>
                            <comment id="128611" author="dsvirdi" created="Thu, 24 Jul 2025 06:21:17 +0300"  >&lt;p&gt;Dear Salim, Medhat &lt;/p&gt;

&lt;p&gt;We had a discussion with our product team and it is understood from the scenarios described by Daljeet from Al Duraidi that we need to update our rules so that AL duraidi corrects partially some  data available in existing Passive DB  through generic template for some period of time however  initially the generic template was designed to import data one time, also there is a possibility to revert back on old data provided in Passive DB again which is creating too much complexity.  Since those changes are provided initially manually by Alduraidi /Zain KW, we need to check the possibility to  apply those data change on Passive DB directly manually and not NEP  and we continue our usual  daily sync  for updated data without any rules updates since our main source of information for daily update of passive element is the Passive DB &lt;/p&gt;

&lt;p&gt;This is the context of our discussion so let us know your feedback accordingly&lt;/p&gt;

&lt;p&gt;Regards&lt;br/&gt;
Abir&lt;/p&gt;</comment>
                            <comment id="129422" author="habdine" created="Tue, 5 Aug 2025 10:22:46 +0300"  >&lt;p&gt;as discussed, as CyberMark are the master of passive data, they shall be responsible of updating passive attributes, and NEP will sync ...&lt;/p&gt;</comment>
                            <comment id="132026" author="dsvirdi" created="Wed, 10 Sep 2025 08:44:00 +0300"  >&lt;p&gt;We are checking with Cybermak to provide suitable to discuss the way forward on this tickt.&lt;/p&gt;</comment>
                            <comment id="142208" author="dsvirdi" created="Tue, 27 Jan 2026 04:21:15 +0200"  >&lt;p&gt;As checked with Cybermak they will check internally to way forward on this ticket.&lt;/p&gt;</comment>
                            <comment id="143306" author="dsvirdi" created="Thu, 12 Feb 2026 05:38:33 +0200"  >&lt;p&gt;Closure confirmed by Customer&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                        <customfield id="customfield_11700" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>Actual Start</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 5 Nov 2024 00:00:00 +0200</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10306" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>Baseline End</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 7 Nov 2024 00:00:00 +0200</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10305" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>Baseline Start</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 7 Nov 2024 00:00:00 +0200</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_12600" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Classification</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="13201"><![CDATA[CR]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:multiselect">
                        <customfieldname>Customer</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="12400"><![CDATA[Zain Kuwait]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11702" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>Date of Baselining</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 11 Nov 2024 04:01:49 +0200</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_11009" key="com.innovalog.jmcf.jira-misc-custom-fields:calculated-text-field">
                        <customfieldname>Dev. Actual Duration</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[0 minutes]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10304" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                        <customfieldname>Gantt Options</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10200"><![CDATA[Milestone]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10800" key="com.capitalcityconsultants.jira.plugins.customfields.ccc-lastcomment:last-comment">
                        <customfieldname>Last Comment</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>&lt;p style=&quot;display:inline&quot;&gt;&lt;b&gt;Evaluation License Error:&lt;/b&gt; EXPIRED&lt;/p&gt;</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_12500" key="com.atlassian.jira.toolkit:originalestimate">
                        <customfieldname>Original Estimate</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11008" key="com.innovalog.jmcf.jira-misc-custom-fields:calculated-text-field">
                        <customfieldname>PDM Actual Duration</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[0 minutes]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10301" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>Planned End</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 7 Nov 2024 00:00:00 +0200</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10300" key="com.atlassian.jira.plugin.system.customfieldtypes:datetime">
                        <customfieldname>Planned Start</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 7 Nov 2024 00:00:00 +0200</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10901" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|xtigrd:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10004" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_11704" key="vivid.trace:VTDirections-custom-field-type">
                        <customfieldname>VTDirections</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        </customfields>
    </item>
</channel>
</rss>