Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-12986

Dakotaland FCU - Lincoln Life leading value

    Details

    • Type: Support Activity
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Support Task Type:
      Configuration
    • Environment:
      Production
    • Reported by:
      EDI
    • Company:
      Dakotaland
    • Module:
      BenAdmin - Customization
    • Issue Importance:
      Must Have
    • Severity:
      Simple

      Description

      Company Template: Lincoln_Life_Final
      Affected Columns: OLI Cvgs, OAD Cvgs, OSLI Cvgs, OSAD Cvgs, OCLI Cvgs
      Leading values: OLI-, OAD-, OSLI-, OSAD-, OCLI-
      Export Date: 1/3/18

      Hi Vinayak Kulkarni,

      Sorry I finally have the time to test and open a ticket for this file. This Lincoln format is different than other Lincoln files that were built for other clients. I had another ticket a while ago JIRA# WT-11672 regarding a lincoln macro to use, but Amit had said it will pass all enrolled Life coverages on the same column with commas separating them. This won't work for my file, because the affected columns are spread out differently.

      I was also suggested to try the check box "Do Not Apply Padding For Blank Value" under the Edit Sub Template Field, but the leading value are still coming out on every row although the employee is not enrolled in the plan. Is there a way to only pass leading value if enrolled in the benefit? If this is possible, the file will be ready to go weekly. In the meantime I've been removing them manually which only takes me about a few minutes to do before posting to the carrier.

      See screenshot for comparison between a good file and bad file. Let me know if you need additional info.

      Thank you,

      Alex

        Attachments

        1. compare.png
          compare.png
          23 kB
        2. screenshot-1.png
          screenshot-1.png
          49 kB

          Activity

          alexn Alex Nguyen created issue -
          alexn Alex Nguyen made changes -
          Field Original Value New Value
          Description *Company Template:* Lincoln_Life_Final
          *Affected Columns:* OLI Cvgs, OAD Cvgs, OSLI Cvgs, OSAD Cvgs, OCLI Cvgs
          *Leading values:* OLI-, OAD-, OSLI-, OSAD-, OCLI-
          *Export Date:* 1/3/18

          Hi [~Vinayak.Kulkarni],

          Sorry I finally have the time to test and open a ticket for this file. This Lincoln format is different than other Lincoln files that were built for other clients. I had another ticket a while ago JIRA# WT-11672 regarding a lincoln macro to use, but Amit had said it will pass all enrolled Life coverages on the same column with commas separating them. This won't work for my file, because the affected columns are spread out differently.

          I was also suggested to try the check box "Do Not Apply Padding For Blank Value" under the *Edit Sub Template Field*, but the leading value are still coming out on every row although the employee is not enrolled in the plan. Is there a way to only pass leading value if enrolled in the benefit? If this is possible, the file will be ready to go weekly. In the meantime I've been removing them manually which only takes me about a few minutes to do before posting to the carrier.

          See screenshot for comparison between a good file and bad file.
          *Company Template:* Lincoln_Life_Final
          *Affected Columns:* OLI Cvgs, OAD Cvgs, OSLI Cvgs, OSAD Cvgs, OCLI Cvgs
          *Leading values:* OLI-, OAD-, OSLI-, OSAD-, OCLI-
          *Export Date:* 1/3/18

          Hi [~Vinayak.Kulkarni],

          Sorry I finally have the time to test and open a ticket for this file. This Lincoln format is different than other Lincoln files that were built for other clients. I had another ticket a while ago JIRA# WT-11672 regarding a lincoln macro to use, but Amit had said it will pass all enrolled Life coverages on the same column with commas separating them. This won't work for my file, because the affected columns are spread out differently.

          I was also suggested to try the check box "Do Not Apply Padding For Blank Value" under the *Edit Sub Template Field*, but the leading value are still coming out on every row although the employee is not enrolled in the plan. Is there a way to only pass leading value if enrolled in the benefit? If this is possible, the file will be ready to go weekly. In the meantime I've been removing them manually which only takes me about a few minutes to do before posting to the carrier.

          See screenshot for comparison between a good file and bad file. Let me know if you need additional info.

          Thank you,

          Alex
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) made changes -
          Attachment screenshot-1.png [ 71325 ]
          Hide
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment -

          Hi Alex Nguyen

          Do Not Apply Padding for blank value will work only if Is padding required, please try making below highlighted change and save sub-template

          Let us know if this doesn't work. Thanks.

          Show
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment - Hi Alex Nguyen Do Not Apply Padding for blank value will work only if Is padding required, please try making below highlighted change and save sub-template Let us know if this doesn't work. Thanks.
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) made changes -
          Assignee Vinayak Kulkarni [ vinayak.kulkarni ] Alex Nguyen [ alexn ]
          Resolution Done [ 10000 ]
          Status In Progress [ 3 ] Resolved [ 5 ]
          Hide
          alexn Alex Nguyen added a comment -

          Thank you so much, Vinayak Kulkarni. For testing, I tried both check boxes for the OCLI and it's coming out correctly on file. Sorry I must have missed the 2nd option the last time we discussed. I'm sure the other columns will also work.

          Alex

          Show
          alexn Alex Nguyen added a comment - Thank you so much, Vinayak Kulkarni . For testing, I tried both check boxes for the OCLI and it's coming out correctly on file. Sorry I must have missed the 2nd option the last time we discussed. I'm sure the other columns will also work. Alex
          alexn Alex Nguyen made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          alexn Alex Nguyen made changes -
          Link This issue relates to EDI-1944 [ EDI-1944 ]
          Transition Time In Source Status Execution Times
          Vinayak Kulkarni (Inactive) made transition -
          Open In Progress
          3h 50m 1
          Vinayak Kulkarni (Inactive) made transition -
          In Progress Resolved
          1m 58s 1
          Alex Nguyen made transition -
          Resolved Closed
          14h 54m 1

            People

            Assignee:
            alexn Alex Nguyen
            Reporter:
            alexn Alex Nguyen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: