Support multi language for content fields on offerings

Idea ID 1642220

Support multi language for content fields on offerings

Today in SMA-X we have to create a dedicated catalog offering for every language we offer when it comes to having the content (Description, user options, etc) in the specific language. 

This is not scalable and demands a lot of overhead administration. 

 

The idea is to support "parallel" fields per language per relevant field for all end user facing fields on one offering record. This could be similar to the language translation fields that are offered on the records tab when creating new custom fields. 

The competition generally has this functionality. 

7 Comments
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be reviewed by the product team. 

Micro Focus Expert
Micro Focus Expert

@Philipp_Koch -  please see this article for how to translate offerings. Assuming this meets the requirement? 

 

https://docs.microfocus.com/ITSMA/2018.02/NG/SM_X/Content/2200_ServiceCatalogManagement/sercatL10n.htm

Micro Focus Expert
Micro Focus Expert

Hi

Thanks. Yes there is a way today - but it is not very nice and not scalable. 

Here the reasons why:

- high admin overhead to administer, update, change

- cant be seen on the offering view and hence not easy to administer

- high effort to do, export, manage CSV, edit CSV, import

- CSV is not a good format to edit text in 

- not really scalable when you need to update many offerings. 

 

Cheers

Philipp

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Hello, and thanks for raising this,

This is just to comment about ER QCCR1E142530: my FlexCare account is a international SP and users from different countries for sure would like a future as described. We raised ER through ER escalation old process and had not received clear statement on feasibility; so an estimation about would be more than welcome.

If any doubt or needed added detail please tell me.

Thanks!
Pedro

Micro Focus Expert
Micro Focus Expert
Status changed to: Under Consideration

Thanks for all the votes and comments. We are looking into this as a future product enhancement. Check the notifications box to be emailed if the status changes.

Micro Focus Expert
Micro Focus Expert

For those of you who voted for this, we would like to capture some more information. An in-tool ability to edit all languages  for offerings and articles makes some sense, especially so that this is consistent across localization use cases (with email templates, record field display labels,). However Catalog and KM are different by design.

Catalog and KM consist of so much content, undergo frequent changes and additions, and tend to be localized for Self-Service purposes to many more languages. The only way to manage this efficiently is through an export/import process, often leveraging translation memory tools. Many customer use outside vendors for this.

So the question is, is the preference for export/import vs. in tool impact by customer size? Is this for demonstration or POC reasons? 

 

Honored Contributor.
Honored Contributor.

This should also include Display Name for Service Catalog Category (Tiles). Today we need to apply a complete Service Catalog for every language we need to support.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.