Abhay Patil (Inactive) added a comment - 05/Jun/17 08:36 PM - edited Lalit Kumar - As for the 55 unused fields, if they show up as options in the system then they need to be safely removed from the system first. CC Satya Cindy Wibbing Chris Ellenberger Damion M Velasquez Van Nguyen Amit Thorve (Note: can you please delete the outdated attachments? There are five files that have names beginning with "Field Mapping". Of course one can see the dates, but it would be better if you could retain just the latest file.)

Lalit Kumar (Inactive) added a comment - 20/Jun/17 08:18 AM - edited Hello Satya , As indicated above we can remove the 55 unused fields if they show up in the system.Requesting you to please create a separate ticket for removing the fields. Also, I have removed the old files uploaded by me. Please remove the following files uploaded by you. [^Field Mapping Definitions - 20160712.xls] and [^Field Mapping Definitions - 20170407.xls] Regards, Lalit Kumar

Satya added a comment - 22/Jun/17 01:25 PM Hi Vinayak, As discussed, can you please schedule to remove 55 mentioned fields. Link JIRA ticket to this parent ticket to keep track. Regards, Satya Prakash

Vinayak Kulkarni (Inactive) added a comment - 23/Jun/17 11:10 AM Hi All, New jira WT-9922 is created to remove unused fields from fields mapping screen.

Cindy Wibbing (Inactive) added a comment - 21/Aug/19 10:55 AM Hi Vinayak Kulkarni Can we get an updated Field Mapping Definitions lists.  We were looking for some of the fields that are now in Workterra but not on the 2017 list provided.  Also, from the Macros listing you provided we are trying to verify our interpretation of the macros so that we can make sure we are using them correctly on the file feeds.  Can you please review and make any additional notations associated with the last column on our interpretation.   Field Name (Harbinger) Import / Export File Type Definition Nature Amenable to data transformation? Current EDI Interpretation/Comment Enrollment Plan Type Export Both This field will fetch 'Plan Type'  from the database table 'plan design.'             Direct Field From Database NO Pull Plan Type on Benefit.  Is this only for a single plantype selected?  Will it pull for multiple plan types selected on the template. Enrollment Enrolled IN Export Both Do not use as an updated field 'Member Enrolled In' Conditional Field (Macro) YES Pulls the enrollment for the employee record only even if defined on dependent subtemplates.  Ignores the enrollment associated with any dependent records. Enrollment Last Enrolled IN Custom Field Both This field will populate the last planned enrolled by the employee Conditional Field (Macro) NO Pulls the most recent enrollment for any member, EE, SP or Child.  Used to pull information on terminated records (i.e. Health Tiers, Effective dates.) Enrollment Spouse Enrolled In Custom Field   This property indicates whether the spouse is enrolled in benefit plan or not. Conditional Field (Macro) YES Only looks to the Spouse benefit.  Not subtemplate dependent but plan dependent.  Will look to see if the spouse is in the enrollment for plan in rule.  Can be used on columnwise Employee SubTemplate to look to Spouse enrollment for plan. Enrollment Member Enrolled IN Export Both This property indicates whether a member (employee, spouse, child) is enrolled in a benefit plan or not. Conditional Field (Macro) YES Subtemplate dependent not plan dependent.  Will look to see if the the member is in the enrollment for plan in rule engine based on the subtemplate the rule is defined on.  Member Enrolled IN on Spouse Subtemplate looks to whether the Spouse is enrolled on the plan, Member Enrolled IN on Employee Subtemplate looks to whether the Employee is enrolled on the plan and Member Enrolled IN on Child Subtemplate looks to whether the Child is enrolled on the plan. Enrollment  Member Enrolled In Benefittype Export     Conditional Field (Macro)   ? Enrollment  Child Enrolled IN Custom Field  Both This property indicates whether the child is enrolled in benefit plan or not. Conditional Field (Macro) YES Only looks to the Child benefit.  Not subtemplate dependent but plan dependent.  Will look to see if the child is in the enrollment for plan in rule.  Can be used on columnwise Employee SubTemplate to look to Child enrollment for plan. Thanks! Cindy