Should a sequence item configure actions of the driver?

UVM
1

If a transaction can had a variable delay between other transactions, should that information for the amount of delay be within the transaction or shouls therr be a configuration object that the driver looks at for the amount of delay and the user should update the configuration each time they want to chagne the delay?

Same question goes for a parity error does that information be contained in the driver configuration object or the transaction it self?

2

In reply to DVCoder:

My recommendation is to encapsulate all elements which affect the transaction (data/delay/errors) into the transaction itself. This provides the greatest flexibility to control the test using the test sequence.