Skip to Content
0
Jul 04, 2023 at 01:50 PM

Pros/cons of having a field in Job info vs. in the Position (and then syncing to Job Info) ?

71 Views Last edit Jul 07, 2023 at 02:09 PM 2 rev

My company has EC implemented and we use position management. Often times, me and my team find ourselves questioning whether a field/data point is supposed to be added to the position object(and then sync to Job Info) or just stored in job info.

We are trying to add a field in the system that indicates what template of performance evaluation to assign to someone, depending on the nature of their job. Something like a cost center, or a department makes sense that its in the positions object. This particular field, not sure. Are there any benefits or downsides of having something just in Job info? In which option is easier to get rid of this field if we no longer need the field? Any best practices or rule of thumbs?