Details

    • Customer:
      Zain KSA 3.X

      Description

      Dear @Bassem Sabbagh,

      As per our earlier discussion, kindly assign an AI DEV resource to implement a rule for parsing nodes as outlined below:

      Note: This rule will apply when the same node (NEName) appears with two different models. The first model will be "BTS5900" and the second one will be "BTS3900" (see example for reference).

      Rule: We need to parse only the node that comes with NEType="BTS5900" and ignore the one with NEType="BTS3900".

      Example: For the node (NEName="ARR0519-P1-HUB_SRAN-FON"), it appears in the dump with two different models: NEType="BTS5900" and NEType="BTS3900". We need to parse only the entry with NEType="BTS5900" and disregard the entry with NEType="BTS3900".

      Best regards,
      Indrasan

      Issue Links

        Activity

        Hide
        Bassem Sabbagh added a comment -

        Assigned to Sandhya to define the WL

        Show
        Bassem Sabbagh added a comment - Assigned to Sandhya to define the WL
        Hide
        Sandya Sharma added a comment -

        WL is one day.

        Show
        Sandya Sharma added a comment - WL is one day.
        Hide
        Bassem Sabbagh added a comment -

        to be started and delivered by 9-1

        Show
        Bassem Sabbagh added a comment - to be started and delivered by 9-1
        Hide
        Indrasan Yadav added a comment -

        Dear @Sandya, please commit the code for same as now issue has been fixed in shared XML (2025-01-09-05.30.41_ZainKsa)

        Show
        Indrasan Yadav added a comment - Dear @Sandya, please commit the code for same as now issue has been fixed in shared XML (2025-01-09-05.30.41_ZainKsa)
        Hide
        Sandya Sharma added a comment -

        commit done.

        Show
        Sandya Sharma added a comment - commit done.
        Hide
        Indrasan Yadav added a comment -

        We are now closing this child JIRA as it pertains to an individual issue.

        As suggested by @Ahad, all code commit JIRAs will be covered under the parent JIRA.

        Show
        Indrasan Yadav added a comment - We are now closing this child JIRA as it pertains to an individual issue. As suggested by @Ahad, all code commit JIRAs will be covered under the parent JIRA.

          People

          • Assignee:
            Indrasan Yadav
            Reporter:
            Indrasan Yadav
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Planned Start:
              Planned End:
              Actual Start:
              Date of Baselining:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 1 day, 7 hours
              1d 7h

                Drag and Drop