Question about the internationalization plugin

If I remember correctly, we've had instances where the file doesn't pickup for some reason. We just keep trying again until it eventually picks up. We also developed a small process called Label Check that outputs all the labels in the resource file which tells us if the file has been picked up by the system or not.

Thanks - I've been using the "try until it works" method already but I was wondering if there wasn't a more consistent way to get the system to flush the cache and pick up the new version. Sometimes the first update works and sometimes it's the 20th.

Deployments to forward environments with an inconsistent behavior like this make me nervous and I was hoping for a more surefire method.

I agree. Wish there was a more foolproof way of doing this.

I don't believe we've ever had instances where it took us 20 attempts for it to pick up. When it does happen it only takes 2 or 3 attempts for it to pick up. It could also be something wrong with the file (end of line, special character).

We've also been toying with the idea of storing all the labels in a database table and having a process (which could be scheduled) generate the resource file.

I agree - hence my question at large.

We also considered doing something similar but instead of storing individual values (1 per row) and generating a resource file we were going to store entire JSON dictionaries for set's of translations (ie: 1 dictionary per form/app/record). That way we could minimize database calls and bypass the need for a dictionary at all.

I would recommend reaching out to the author of the plug-in for further assistance with this issue: forum.appian.com/.../e-77531