The framework (everything but SevriceForms) is supported in multi language. The forms are what you build and nS does not know it exists, hence it is not translated by them.
You can build a service in english, create an exact replica and translate it into another language. Then via ordering permissions you can make the english service visible to english speaking people, etc...
The other option you have is to change the labels via onload scripts if you can detect the users language, since this
Please share your experience with using multple language service forms, assuming RC stores the data (as is) if reporting is needed the data could be separated in the same way, English versus Non-elglish, by permission setup.
We have a custom single sign on event because we have a LDAP structure with several child domains and this is not supported out of the box. Our tentative plan is to use the SSO event to pull the LocaleID from the HTTP headers and manipulate that in to the Org Unit names... I'll let you know how we go *crosses fingers*
Thanks for the input on this subject. We have plenty of exploring to do. Hopefully we can id the users locale or language with LDAP data. If this is possible would I need to have a staging database to store the Users information so conditional expression are used to determine the language or locale? Not sure how this might work.
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...