Under Community Review

Thank you for your suggestion to help improve SDL TMS. If I understand this correctly, extra preparation work on the file does not result in re-processing the file and getting new costs etc. I will wait to see what others think of the idea but in the meantime, I believe this should be possible through a customization to clear out the existing information from the database and the filing system in order to get Pre-processing generating the new statistics.

Regards,

David

Support 2nd round of Pre-processing

Support 2nd round of Pre-processing will be convenient.

Because if we use Convert Item then Pre-processing, it shows costing result.

But we made mistake at the Convert Item, we need to create a job again from scratch. Otherwise not reflected even we push back job to Convert Item and made changes.

Now a day integration to ManTra is increased. Sometime, hardly to ask client to re-create job.

Believe, if "Pre-processing" could clean up DB and files that previous Pre-processing generated, the issue will be solved.

Hitoshi Tatemura

  • Dear David,

    Thank you for your guidance. Yes, customization step named "Instant Quote Workaround" can do that.

    Start thinking of raising a separate Idea of feature request that modifying step to "Exception" then we can redo the non-human step of "Instant Quote Workaround". Is this make sense to you?