Clarify Playbook Appian Application Internationalization Strategy

RE: Clarify Playbook Appian Application Internationalization Strategy

Richard Nolan — Fri, 24 Jan 2020 16:41:31 GMT

We do understand that part, the issues is particularly in the wording that Bob has highlighted....

RE: Clarify Playbook Appian Application Internationalization Strategy

Mike Schmitt — Fri, 24 Jan 2020 16:35:04 GMT

I think you might be overlooking the part that specifies "expression-backed record". Using this method, you'd presumably be able to transform any data in the background prior to it reaching the OOB record type definition (column names, labels, etc).

RE: Clarify Playbook Appian Application Internationalization Strategy

Richard Nolan — Fri, 24 Jan 2020 15:51:52 GMT

Bob and I are aware of how to use Resource Bundles via the loadbundle plugin. At issue here are two things: the fact that there is no way to efficiently load a bundle for the grid/list views in an Entity-backed record (essentially we'd need to load the bundle for every item - which seems innefficent).

And, the wording of the instructions that Bob quoted. What is meant by passing the bundle into an element of the record source CDT. This is not clear to me.

RE: Clarify Playbook Appian Application Internationalization Strategy

btravis — Fri, 24 Jan 2020 15:33:55 GMT

Hi Robert,

We understand the strategy to use resource bundles and create a local variables in the context of an interface object. It's still not clear how to load the bundle once and use it throughout the record type designer interface. How do we define a variable, as suggested in the playbook, inside the record list view expression and use the variable throughout the record type designer (record list definition, related action button labels).

Or are you suggesting we need to reload the bundle inside every column label and related action button using expressions? If so then the playbook recommendation doesn't make any sense:

"Internationalized apps need to use an expression-backed record to load the bundle once and pass the bundle into an element of the record source CDT. In the record list view the bundle element of the source CDT can be referenced to internationalize labels and data in the list view"

Thanks.

RE: Clarify Playbook Appian Application Internationalization Strategy

Robert Shankin — Thu, 23 Jan 2020 18:25:46 GMT

You can i18nize any component which includes an expressionable display element (i.e. a label).

Ideally on an interface, you can load the bundle into a variable and then index out the value like so:

 label:index(local!i18n_bundle, "firstName", "First Name")

where local!i18n_bundle is the bundle, "firstName" is the key, and "First Name" is the default display value in the event that no value matches that key.

Were there use cases in which you don't have the luxury of loading your bundle in advance, I suppose you can do it on the fly:

 label:index(rule!i18n_loadBundleFromFolder(cons!someFolder), "firstName", "First Name"),

RE: Clarify Playbook Appian Application Internationalization Strategy

btravis — Thu, 23 Jan 2020 01:27:36 GMT

Hi Robert,

Sorry my question wasn't clear, we understand we need to load a bundle as you described, however how to we reference the resource bundle when setting column labels in the record list view or labels for action/related action buttons for example?

RE: Clarify Playbook Appian Application Internationalization Strategy

Robert Shankin — Wed, 22 Jan 2020 20:47:38 GMT

Hi Bob

For better context, any mention of a "bundle" is in the context of the `load resource bundle` plugin.

The plugin enables the product to interact easily with "bundle" files by exposing some functions (detailed on the plugin page).
Bundles are essentially lists of key/value pairs. Typically, there is one bundle per language, and any text that needs to be translated is wrapped in expressions to tell Appian which word or phrase to display from the given bundle.

https://community.appian.com/b/appmarket/posts/load-resource-bundle