Data Migration and Integration Questions

Which business rule timing should be used to change field values just before the record is written to the database?

An admin has received an update set XML from another instance. What should happen on the target instance before the contained changes are applied?

Which business rule timing runs after the database action and does not make the user wait for completion?

What is the standard mechanism for collecting many configuration changes and moving them between development and test instances?

Which platform feature can make a form field mandatory or hidden based on conditions without requiring server side record logic for the UI behavior?

Sending a non urgent outbound notification should not delay the user who is saving the record. Which business rule timing is best suited for that work...

An admin imports an update set into test and wants to identify collisions before applying the changes. What should they do first?

A field should become mandatory on a form when Category is Hardware and no server side script is needed. Which feature is the best fit?

A business rule must set values on the current record before the record is written to the database. When should it run?

Client scripts need server derived information available when a form first opens. Which business rule timing is designed for that purpose?

When importing a CSV file on a schedule which record defines the file source and format details?

Which feature loads external data into a staging table before it is mapped into a target table?

Which configuration maps fields from an import set table to a target table and can run field transform scripts?

In a transform map what is the purpose of coalesce?

External CI data needs to be staged normalized and then loaded into the CMDB. Which approach is most appropriate?