This feature is currently in beta.
The new Strings View / View All Strings is currently only available for Account Owners and Project Managers. Only "active" strings are shown in the results. This feature is accessible via Jobs or the Projects (for customers who have access to our new user experience.
Access Strings View Via Jobs
Go to Jobs and click on a job. You can access all active strings in that job by clicking on either the View Strings link from the Job Summary card on the left hand side of the page, or via the View all strings link.
Access Strings View Via Projects
If the new Strings view has been enabled for projects for your account, you can click the "Strings View (beta)" link available from any of the 4 Content -> Translations pages (Awaiting Authorization, Excluded, In Progress, Completed).
Access Strings View Via New User Experience
If you have been given access to our New User Experience, all projects have a link to the projects Strings view via the Strings tab.
Edit in the CAT Tool
To open a string in the CAT tool, click Actions > Edit in CAT Tool.
- The exact filter of strings in the CAT tool will not be the same as the current filter in the Strings view. You may see other strings, and they may be in a different order. Only the language of the string selected will be available in the CAT tool.
- Most of the columns in the results are currently a fixed width. The source and translation columns are dynamic, and will widen as you make the browser window wider. Improvements to this are still to come.
- The ability to add an arbitrary string directly from the dashboard is not currently available from the New Strings view.
New features for search results:
- You can see strings that are Awaiting Authorization, In Progress, and Excluded at the same time. No need to search for “partially authorized” strings.
- You can now see results across multiple languages at the same time.
Understanding the new search results view and counters:
The counters in the results are the count of the source strings that match.
When looking at multiple target languages (the default), a source string will be repeated for each row with its current translation, and that language’s status.
You will see more results (rows) than the number of the string counts shown if you are looking at multiple languages. Example:
|Source string1||Source string1 ES translation||Spanish|
|Source string1||Source string1 FR translation||French|
The count of this result is 1 string (2 words). There are two rows in the result because there are two languages to show. In the future, Smartling will update the counts to reflect both the source string and word count, as well as the number of translations in the results (rows).
The search results use dynamic pagination. When searching across multiple languages, a result will never split a single source string and its translations across multiple pages. All of the translations for a single string will always be shown on the same page. As a result, the number of individual source strings that will be shown on a single page, and the number of results shown on a single page are dynamic. They adjust automatically depending on the total result set and the number of languages selected.
New features for filtering and searching:
- Search separately by text in the source string and text in the current translation.
- Search for exact strings by "quoting". However this won't work for strings with placeholders or HTML markup.
Will return any string with the word “content” in it.
Will return only the string that is exactly the single word, “content”.
- You can limit results to one specific File or URL by clicking the exact match checkbox.
- Search is not case sensitive, even exact search.
- All filters are combined using logical “AND”; you may get zero results when combining filters, even if an individual filter would have some results.
- The the behavior of the History filter has been updated. The "preselected" date ranges (e.g. last 24 hours) are now dynamic. The URL for the filter (and eventually saved searches with that filter, a forthcoming feature) will use the range relative to the time the page is being loaded. So you can get different results if you run the same filter today vs. tomorrow (or even 5 minutes or one hour later), because it’s really last 24 hours from the time the page is loaded. If you want to share a search or revisit a search for a specific time range use the Custom date range options to specify the exact time range. A saved search or shared URL with a custom range should produce the same results over time (assuming nothing else changes).
- The History filter continues to have limitations for how many results can be returned. The UX provides explicit feedback when a search using History is not able to be returned. You can narrow your history or remove it from the search.
- Most filters from the previous, Content > Translations section, are now available in the new Strings View. (Some filters are still in progress.)
Understanding the selections and actions:
Bulk Actions and Select All
All actions are now "bulk" actions and will apply to all selected strings. (You must make a selection before you can take any action.)
You can select/check a string on one page, navigate to another page, select other items, and then take an action, and the application will remember exactly which items you have selected, regardless of the page you are currently viewing.
You can also take an action on all of the items in a result set without navigating to all of the result pages. To perform an action on the entire result set:
- Select the All on this page checkbox that is in the table's header row.
- Choose the Select all matching current filter option that appears after you have selected all on the page.
"All on page" checkbox:
"Select all matching current filter" action link:
Source String actions vs. Translation Actions
Certain actions apply to the language specific translation that is selected, while other actions apply to the source string, regardless of which language is selected. Depending on the action, the application will operate on the source string or the translation.
For example, if you are looking at a results set that includes just one string that is "In Progress" across five languages, you will have five items (rows) in the result. If you choose the result for language1 and then take the action to "Add instructions", that instruction is applied to the source string. Therefore, the instruction that is added will be shown no matter what language someone is working on for that string. String instructions are applied to the source string and are shown for all languages.
Given the same result set (1 string for 5 languages). If you choose the row for language1 and then choose the action to Submit to the next workflow step, that action will only apply to the language and translation selected, since submitting, is a language/translation specific action.
Similarly - when you request translation you are taking actions on the specific language that is selected. Even if you choose to request translation in an existing job, and that job currently has other languages, only the languages specifically chosen will be added to the job. That can result in the job having a new language that is tracking; or that the the string is only being translated for one language of multiple languages that the job is currently tracking.
Not all actions can be applied to all selected strings or translations
The application will attempt to take the requested action on all selected strings. But it does not validate if that action actually can be applied. If it is not applicable, the action will not be performed and it will silently fail. No feedback is provided in this case.
Reload the page after you perform an action to see the updated results. Depending on your current filter, and the action just taken, you may get a smaller or larger result set. You may need to update your filter to see the strings or translations that you just took an action on.
- Most of the actions available in Content > Translations are available in the new Strings View. There are some that are still in progress.