Concept: Edit Additional Data Step

To update effective-dated custom objects on effective-dated business objects, you can include Edit Additional Data
steps in any of these business processes:

Business Object	Business Process
Academic Appointment Track	Add Academic Appointment
Academic Appointment Track	Update Academic Appointment
Employee Contract	Edit Employee Contract Additional Data Event
Employee Contract	Employee Contract
Job Requisition	Edit Job Requisition Additional Data
	Job Requisition
	Job Requisition Change
Learning Course	Manage Course
Learning Course Offering	Manage Course Offering
Learning Program	Manage Program
Position Restrictions	Create Position
	Edit Position Restrictions
	Edit Position Restrictions Additional Data
Worker	Change Job
	Contract Contingent Worker
	Edit Worker Additional Data Event
	End Contingent Worker Contract
	Hire
	Termination

When Edit Additional Data
is a step within an overall business process, Workday creates event lites under the new event lite type of Custom Object Effective-Dated Change. When an action event contains 1 or more Edit Additional Data
work flow steps:

Before the event completes, Workday creates 1 event lite and 1 corresponding transaction log lite with an entry moment that matches the parent event when the event completes, regardless of how many steps you include.

After the event completes, Workday creates 1 event lite and 1 corresponding transaction log lite with an entry moment of the step when it completes. Post completion Edit Additional Data
steps have a different entry moment than the parent event.

When you correct an Edit Additional Data
step, Workday creates 1 event lite entry and a corresponding transaction log lite entry.

Workday creates an event lite in the transaction log when you update effective-dated custom objects using a standalone business process.

When you correct the effective date of a business process event, Workday creates an additional Transaction Log Lite entry with the previous effective date and the entry moment. The original correction entry with the new effective date remains in the transaction log.

To verify or audit the values of Workday custom objects, use the transaction log to find instances of Custom Object Non-Effective-Dated Change - Event Lite Type. The event lite type includes the changed custom object name, the owning instances, and who changed the custom object and when the change occurred. It doesn't include details describing the actual changes to the custom object data.

If you need to retrieve custom object data from Workday for use in an external system, you can query the transaction log for current custom fields values.

Using Business Processes and Custom Objects

Use a business process to edit custom field data on effective-dated custom objects. You can only select custom objects that support effective-dated business objects.

To view or update effective-dated custom objects on a business object outside of staffing business processes, use 1 of these standalone business processes:

Edit Employee Contract Additional Data Event

Edit Job Requisition Additional Data

Edit Position Restrictions Additional Data

Edit Worker Additional Data Event

Update Academic Appointment

Set up an Edit Additional Data
step for each effective-dated custom object. You can only route this business process step to security groups that have permission to access the selected custom object.

When you have the required business process security, select

Additional Data

Edit Effective-Dated Custom Object

from the related actions menu of the Workday object. Enter an effective date. Workday applies the date to all custom objects that you add or update.

To view the effective-dated custom objects, select

Additional Data

View All As Of

from the related actions menu of the Workday object.

You can configure step label overrides on Edit Additional Data
business process steps.

For Edit Additional Data
steps routed to you:

You can edit only active custom fields for a custom object.

When you submit the Edit Additional Data
step, Workday evaluates any custom object validations. When it detects invalid data, it displays an error message.

You can only delegate an Edit Additional Data
step to a member of a security group that has permissions on the security domains that secure the custom object. On the Edit Additional Data
items in My Task, the delegate can view details of the event by clicking

View Details

in the gear icon.

Workday skips the Edit Additional Data
steps when you submit 1 of these business processes through either:

A web service with auto-complete enabled.

An EIB using the Automatic Processing option.

You can modify the custom field data while the business process is in progress. To modify the data after the business process is complete, select

Business Process

Correct Additional Data

from the related actions menu of the business process. To modify data, you must have permissions on the:

Correct
action in the business process security policy.

Security domains that secure the custom object.

Snapshots for Effective-Dated Custom Objects

Individual custom objects don't have separate snapshots. Workday stores the data for all custom objects for a business object on the same snapshot. When a new effective-dated snapshot is created, Workday copies the data from the previous snapshot as a starting point. Workday copies the data for all custom objects even when the custom object has a step in the business process that creates a new effective-dated snapshot.

When a later-dated effective date for custom data exists, your changes aren’t carried forward to it. Make the same changes for every subsequent effective date. When Workday displays an alert warning you of a later-dated effective date, apply the same changes to the effective date indicated in the alert.

When a business process event invokes an Edit Additional Data
step, Workday creates an effective dated snapshot. When multiple business processes that update custom data are in process at the same time for the same business object, some changes might be lost if these are in conflict:

Event effective dates.

Snapshot creation time.

Event completion order.

When you rescind any Edit Additional Data
events, ensure that custom data is restored correctly by rescinding the events in reverse effective-date order. Example:

Rescind the latest effective date first, including future-dated events.

Rescind subsequent events that updated 1 or more custom objects from the latest date backwards.

If any events completed with an out-of-order effective date, reapply updates to custom data after all the events back to the latest effective date are rescinded.

The value of an inactive or removed field remains in existing snapshots, but the value is not copied to new snapshots and will not be visible on a new snapshot. Note that a new snapshot can be created by a different business process that updates the custom objects.

Access the

View Out of Order Custom Object Changes

task by selecting

Additional Data

View Out of Order Custom Object Changes

from the related actions menu of a worker to:

Compare custom data across multiple effective dates.

Identify effective dates added or updated when a later effective date with custom data already exists.

Update incorrect custom data by using the links provided in the grid.

View custom data for out-of-order effective-dates.

The

View Out of Order Custom Object Changes

task is secured to the System Auditing
domain. You must have View and Modify access on the domain to be able to make changes within the task. You must also have view access for the domains that secure the custom objects to see the details when you click the links in the grid. Details for custom objects that you don't have view access to won't be visible.