In a new, optional import strategy, the system handles all imports as urg. corrections, but after import, the system deletes the transport requests from the import buffer. If you use this import strategy, the import buffer therefore remains small.
Doesn't the bold text mean that also SDMJ will be handled as urg. correction?
However, there may still be reasons to work with this import strategy. In general, you require it if you work exclusively with small changes that are not dependent on each other. Also, particularly for content dependencies, often only the developer can decide which transport requests are imported and which are not . In this case you would not want to use a project import, but instead you would use individual imports with the new import strategy.
This is our requirement- we don't want to use project import. That's why we choose SDHF. But urg. corr. can only have one active transport request... So we have to use SDMJ, but still be able to transport single change requests.
How to do that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.