13.07.2015 Views

Action Request System 5.1 Developing AR System Applications ...

Action Request System 5.1 Developing AR System Applications ...

Action Request System 5.1 Developing AR System Applications ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Developing</strong> <strong>AR</strong> <strong>System</strong> <strong>Applications</strong>: AdvancedLocalizing Form ViewsAs the architect of a localized environment, you can create locale-specificviews of forms to accommodate the preferred locale of your users. Users willgenerally log in specifying their preference, but, whendefining the locale for a form view (or any <strong>AR</strong> <strong>System</strong> component),administrators have the option of defining only the portion ofthe variable. This design allows users to log in with their preference, for example, fr_CA (French Canadian), but only a single formview is needed with a fr locale specified to accommodate all French-speakingcountries. A localized view of a form is accessed through a browser byspecifying the preferred locale in a URL (see the information about openingforms in a browser in the <strong>Developing</strong> <strong>AR</strong> <strong>System</strong> <strong>Applications</strong>: Basic guide.<strong>AR</strong> <strong>System</strong> is designed with a fallback lookup mechanism when searching fora view to display to users. This enables <strong>AR</strong> <strong>System</strong> to always find a view toopen, even when the user does not specify a preferred locale. For moreinformation about the fallback lookup mechanism, see Creating a LocalizedView of a Form on page 119. For more information about how a view isselected for the user, refer to the <strong>Developing</strong> <strong>AR</strong> <strong>System</strong> <strong>Applications</strong>: Basicguide.After a form view is defined for a specific locale, features throughout <strong>AR</strong><strong>System</strong> are then used to localize the following components of the form view:! User interface components—Features of a view that users see, andinclude:! Field labels! Selection field values! Banner namesThese values are localized by manually entering the localized valuesindividually through the View Properties dialog box, or all together usingan automated procedure.! Message components—Underlying <strong>AR</strong> <strong>System</strong> messages and text, andinclude:! <strong>System</strong> messages! Active Link Message! Filter Message! Help text linked to active link or filter workflow triggersLocalizing <strong>AR</strong> <strong>System</strong> Forms and <strong>Applications</strong> ! 113

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!