WORKTERRAProject Type: software

WORKTERRA

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

UDF Changes and having to reapply UDF eligibility when changed

    Details

    • Type: Support Activity
    • Status: Resolved
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Support Task Type:
      BOSS Setup
    • Reported by:
      Support
    • Module:
      BenAdmin

      Description

      When you change a UDF label the UDF needs to be reattached wherever eligibility is used that is attached to the UDF. It's very difficult to remember each custom form and/or eligibility rule that includes this UDF and since the UDF doesn't automatically update because of the label change across WORKTERRA this leaves room for major errors. It's preferred that if a UDF label is changed the change occurs automatically.

      Examples on when this occurs is when a Wellness UDF is added and there are options added to a drop down list that are then used in the eligibility criteria for rates or plan eligibility if the client wants to change the label of the options for the Wellness drop down the eligibility criteria has to be reapplied to look to the new label that was changed.

      David RhodesFYI
      Jennifer JohnsonFYI
      @

        Attachments

          Issue Links

          relates to

          Enhancement - An improvement or enhancement to an existing feature or task. WT-3984 Eligibility Rule Summary

          • Critical - This problem will block progress.
          • Closed

            Activity

            Ascending order - Click to sort in descending order
            amjohnson Amannda Johnson created issue -
            samir Samir made changes -
            Field Original Value New Value
            Assignee Vijay Siddha [ vijays ] Samir [ samir ]
            Hide
            Permalink
            samir Samir added a comment -

            Check this on priority

            Show
            samir Samir added a comment - Check this on priority
            samir Samir made changes -
            Assignee Samir [ samir ] Swapnil Pandhare [ swapnil.pandhare ]
            Hide
            Permalink
            swapnil.pandhare Swapnil Pandhare (Inactive) added a comment - - edited

            CC : Satya Vijay Siddha

            Hi Amannda Johnson

            There are two scenarios in this .

            1. After adding new field and applying eligibility on it, if field label is changed , eligibility doesn't work properly and name is not properly displayed on Eligibility criteria component.
            Harbinger comments :- We have verified this scenario and its working properly. When field label is changed , it works correctly at all places wherever eligibility is used

            2. After adding new field(only for dropdown list, checkbox, radio list) and applying eligibility on it, if field option label is changed , eligibility doesn't work properly and name is not properly displayed on Eligibility criteria component.
            Harbinger comments : - When option label is changed(only for dropdown list, checkbox, radio list), its not reflected in eligibility criteria. For this, wherever eligibility is applied ,needs to be changed from there. This implementation is since begining. Its not changed by recent stage build.

            When option label is changed, it cannot be applied to all places wherever eligibility is applied.Because, options are stored in a single string in database. It will be very complex to change eligibility from changed option label and also will impact performance.

            There can be below solution for this :
            1. To disable options on field setting in form builder if that field is used in eligibility.
            Please let us know if we should go with this change.

            Thanks,
            Swapnil P.

            Show
            swapnil.pandhare Swapnil Pandhare (Inactive) added a comment - - edited CC : Satya Vijay Siddha Hi Amannda Johnson There are two scenarios in this . 1. After adding new field and applying eligibility on it, if field label is changed , eligibility doesn't work properly and name is not properly displayed on Eligibility criteria component. Harbinger comments :- We have verified this scenario and its working properly. When field label is changed , it works correctly at all places wherever eligibility is used 2. After adding new field(only for dropdown list, checkbox, radio list) and applying eligibility on it, if field option label is changed , eligibility doesn't work properly and name is not properly displayed on Eligibility criteria component. Harbinger comments : - When option label is changed(only for dropdown list, checkbox, radio list), its not reflected in eligibility criteria. For this, wherever eligibility is applied ,needs to be changed from there. This implementation is since begining. Its not changed by recent stage build. When option label is changed, it cannot be applied to all places wherever eligibility is applied.Because, options are stored in a single string in database. It will be very complex to change eligibility from changed option label and also will impact performance. There can be below solution for this : 1. To disable options on field setting in form builder if that field is used in eligibility. Please let us know if we should go with this change. Thanks, Swapnil P.
            Hide
            Permalink
            swapnil.pandhare Swapnil Pandhare (Inactive) added a comment -

            Hi Amannda Johnson

            Please let us know if we should go with above solution.

            Thanks,
            Swapnil P.

            Show
            swapnil.pandhare Swapnil Pandhare (Inactive) added a comment - Hi Amannda Johnson Please let us know if we should go with above solution. Thanks, Swapnil P.
            swapnil.pandhare Swapnil Pandhare (Inactive) made changes -
            Status Open [ 1 ] Waiting for Customer Input [ 10500 ]
            rakeshr Rakesh Roy (Inactive) made changes -
            Assignee Swapnil Pandhare [ swapnil.pandhare ] Amannda Johnson [ amjohnson ]
            Hide
            Permalink
            swapnil.pandhare Swapnil Pandhare (Inactive) added a comment -

            Hi Amannda Johnson

            As discussed, we are implementing eligibility summary page.
            Please refer WT-3984 for this.

            Show
            swapnil.pandhare Swapnil Pandhare (Inactive) added a comment - Hi Amannda Johnson As discussed, we are implementing eligibility summary page. Please refer WT-3984 for this.
            swapnil.pandhare Swapnil Pandhare (Inactive) made changes -
            Link This issue relates to WT-3984 [ WT-3984 ]
            shubhankar Shubhankar Joshi (Inactive) made changes -
            Status Waiting for Customer Input [ 10500 ] Open [ 1 ]
            rakeshr Rakesh Roy (Inactive) made changes -
            Resolution Done [ 10000 ]
            Status Open [ 1 ] Resolved [ 5 ]
            Transition Time In Source Status Execution Times
            Swapnil Pandhare (Inactive) made transition -
            Open Waiting for Customer Input
            		21h 1m 1
            Shubhankar Joshi (Inactive) made transition -
            Waiting for Customer Input Open
            		4d 20h 56m 1
            Rakesh Roy (Inactive) made transition -
            Open Resolved
            		98d 6h 57m 1

              People

              Assignee:
              amjohnson Amannda Johnson
              Reporter:
              amjohnson Amannda Johnson
              Account Executive:
              Samir
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: