Sign-in does what you tell it the first time, and the safeguards around your cloud library got noticeably more careful.

Signing in

• A refused access code no longer takes two tries to fix — when a sign-in failed and DCT asked for your code again, the code you typed was not always the one it checked, so a perfectly good access code could come back refused and only worked on the following attempt. What you type is now what gets checked, the first time.

Your library and Udico Cloud

• DCT asks before your designs go to Udico Cloud, without exception — bridging a browser's library with an access code's cloud shelf has always been something you agree to first. In some circumstances that agreement could be recorded without the question ever being put to you, most often immediately after opening DCT, before your saved designs had finished loading. DCT now waits until it can genuinely see your library before treating the matter as settled.
• Your cloud backups are safer from a bad day at the server — Udico Cloud tidies up shelves whose access code is long gone. That tidying is now far more careful: it will not remove anything on the strength of a single lookup that came back empty. A shelf has to look unclaimed twice, a day apart, before anything is removed, and we are notified the first time it happens, so there is a full day in which a mistake can be caught and undone. If the licence service is having trouble, the cleanup skips that shelf entirely rather than guessing.
• A clearer message when the server is the problem — if Udico Cloud cannot reach its records while you are signing in or backing up, DCT now tells you the service is temporarily unavailable instead of saying your access code is invalid. Your code was never the issue, and the old wording sent people off to re-enter or replace a code that was working perfectly well.