Two language(English and German) are available on SAP Launchpad Login page.
SAP MANUALS, I found that we have to redefine below property :
Application supported languages
application_languages=EN,DE,FR
But I am not able to find exact place where to make the changes to enable or disable Arabic language.
Can anyone please help on this?
regards,
Umar Abdullah
By default, launchpad texts are displayed in the logon language. You can override this setting using a URL parameter.
The language for launchpad texts is set according to the following process:
1) If a value is set for URL parameter sap-language and the specified language is installed on the backend server, launchpad texts are displayed in this language.
2) If no language is defined for URL parameter sap-language, launchpad texts are displayed in the default language set in the ABAP system in Maintain User Profile (transaction SU01).
3) If no language is defined for URL parameter sap-language or Maintain User Profile, the browser settings for header field Accept-Language are taken into account. The system selects the first language from the list that is maintained in the browser, and which is also installed in the SAP system.
Please see also the corresponding docu.
Related
I am implementing a standard SAP Fiori Application named 'My Leave Requests 3' into a SAP Fiori Launchpad on-premise.
I have followed the installation and configuration steps listed in the documentation and the application is up and running.
The applications default behavior uses a simple-approval process, thus one approver can be selected from one rendered input field as can be seen here:
The documentation states that the application supports multi-level-approval. Both frontend (SAPUI5) and backend (ABAP) already include code to handle multi-level-scenarios. This can also be seen in the prior screenshot: next to the input field are visible but disabled buttons.
Since all the logic for a multi-level-scenario exists, the application does not need a custom extension.
Thus, there must be a way to configure the default behavior or allow for MLA in what I assume would be a customizing menu within SAP NetWeaver.
Where can I adjust the application to use the implemented but non-default behavior?
IBM Cloud is showing me almost all menus, options, ... in my local language (take from the browser headers, I guess). How can I force the user interface to be in english? Without having to change the Windows or Browser configuration?
I'm a user of the free layer.
For the IBM Cloud console (the web UI) the language is determined by your browser setting. The the IBM Cloud documentation you can change the language using the language switch, usually at the bottom of a page.
In order to change the console UI you would need to install a browser extension with a so-called language picker.
As #data_henrik explained, the IBM Cloud web UI gets the language from your browser settings.
So you can follow these instructions to set it on your browser of choice:
Chrome browser
Firefox browser
Edge browser
Currently I work an an app where the user can create products for a catalog. The status is, he can do this in one language, data gets send to the backend and saved. The next step would be to make this creation process ready for multiple languages e.g. english or french. The behaviour should be the following, he choses the language inside a drop down field and gets a form in the selected language.
The problems I encountered and my solution process till now:
1) How should the view handling be? Should I create a new fragment for every language and exchange the content? If Im correct that would mean I would need to destroy and create fragements for the languages, right? And then create them with a binded model again.
2) How should I handle the model/models? Should I create one model with the data they share e.g. creation date and create a model with language related attributes? That would be my solution right now.
Maybe you already did something similiar or have some thoughts about this, thanks for any help!
You should do neither of those things. There are mechanisms in place, generally referred to as i18n that help you with this process. UI5 help available here:
https://ui5.sap.com/sdk#/topic/df86bfbeab0645e5b764ffa488ed57dc
and
https://ui5.sap.com/sdk#/topic/5424938fc60244c5b708d71b50a0eee4
In summary, translations should be done using the i18n mechanisms and the oData logon language.
Logging into the application, assuming it's hosted on an SAP gateway or SCP / Launchpad, the user's current logon language will drive at least all standard SAP translatable texts like the labels returned from data elements in your oData services. The appropriate url parameter is sap-language=EN, but it's set automatically from the current browser settings. Generally, you don't have to worry about this.
The same browser settings drive which particular i18n file is loaded. This could be specific like en_US for American English, or fr for French.
If you code your app without any hard coded translations but always follow the rules in the links above, adding a language should be trivial.
These translations could probably be triggered programmatically via a dropdown as well but I have never tried that since it's extra steps for my users.
Is there any way that i can do it for whole site?
For individual user instance, Go to user account settings > Preferences > Author mode, select classicUI
more info here: https://docs.adobe.com/docs/en/aem/6-3/author/author-environment/user-properties.html#Account Settings
Alternatively, to have all users of an AEM instance use the Classic UI by default, start off by going to the AEM Web Console Configuration (/system/console/configMgr). Make sure you’re signed in as an admin and do a find for “WCM Authoring UI Mode Service.” If the service is not visible, click on the OSGi button at the top followed by Configuration, and then do another find. Click on “WCM Authoring UI Mode Service” and change the “Default authoring UI mode” to “CLASSIC” (or back again to “TOUCH,” depending on what you want to do). You must enter “CLASSIC” or “TOUCH” in uppercase letters or an error message will show up when opening a site. Changing this setting will make the chosen UI the default for all sites of the AEM instance. When opening a site with /siteadmin, or /sites.html/content, the site should now open using the Classic UI. This should be the case for all users.
I would like to add functionality to the AtTask system by "adding a layer".
What I want to know is whether this can be achieved with a plug-in for Internet Explorer.
To give a concrete example:
This extra layer would allow users to click on "Online Edit" document (which is not available right now). The linked application will open, and when you click save, the file is loaded back to AtTask.
All this happens in the background via the AtTask API, and is transparent to the user.
The question is: is it possible to add functionality to a site by somehow adding layers?
Last comment: this plug-in (or whatever needs to be installed inbto the browser) will only be visible/active when accesing the AtTask website.
Thanks in advance for your responses.
Within the confines of AtTask your best bet is to use an "External Page" create a service that handles the data in the manner you need.
The Dashboard that contains your External Page can be added as a tab via Layout Templates.
Most of the heavy lifting would have to be handled by your application. You would have to link the document(s) you wish to edit.
Some sort of referrer would be necessary to place the revised document back into AtTask. The method in which the client can do this would be determined by your preference and requirements. I am sure you can find some sort of Wiz-Bang jQuery uploader.
Depending on the level of control you have with your user base, you could make an Application URL
Windows : Registering an Application to a URI Scheme
OS X : Launching Scripts from Webpage Links
I do not know of any other way to handle this other than what Steve suggested.
Having said that a possible solution to this is to create a new application and iframe in AtTask.
At the top or wherever on the page your application could have a link for "Online Edit". Then you would use javascript to extract the task id, project id or any other needed information you need for the api to get the needed content to edit. Then save using the same api information.
I have not tried this type of method but theoretically it could work.