How to use Nintex workflows and Nintex forms with Multilingual SharePoint 2016 Sites Using Variation ?


Badge +1

Problem Scenarios:

Customer wants SharePoint sites for their public facing E-services (Build using Nintex form and Workflows) in ENGLISH and ARABIC both. These e-services should be accessible using all desktop, laptop and mobile devices (tabs, iPhone, android phones and windows phone). When site is switched from English to Arabic customer is expecting all contents (including Nintex desktop and mobile forms) should be translated to Arabic.

In SharePoint sites, we are using VARIATIONS which create a separate site for ENGLISH and ARABIC.

 

Nintex Support Required:

Currently we required your guidelines and support on following items:

  • How to use same workflows hosted under English site for Arabic users
  • How to access and translate NINTEX form hosted under root site from Arabic site
  • How workflow items i.e. Main List Item, Task List Items, Nintex forms, Mobile forms for main list and Task list will be converted to Arabic.

 

All the Nintex form required to be hosted under SharePoint site with master pages.

Pls. suggest best possible solution to achieve above requirements for the customer. Pls. highlight the limitations as well.

 

Note: Customer don’t want Duplicate Lists, Duplicate workflows or Duplicate Nintex form to keep management and administration simple.                                    


2 replies

Userlevel 2
Badge +11

With the available functionality you could consider:

  • Nintex Forms: here you have 2 options (store the used language in the form for use in workflows):
    1. use 2 panels per form with the same content but in different language. Use JavaScript (or a choice/dropdown on top of the screen) to determine current language and hide the other language's panel.
    2. Use a lookup list where Title is the text id and a column for each language's translation (or use Title for the English text and a 2nd column for the Arabic text). On the form you can use the Lookup function in label controls to select the label text in the proper language.
  • Nintex Workflows: you might consider working with email texts for each language stored in a lookup list and insert SP properties where necessary. Task can be setup with Nintex Forms as well (using the above guidelines).

Hopefully this can get you going.

Badge +1

Hi Jean,

Thanks for reply.

That means SharePoint variations will not work for Nintex forms.

Suppose we have one SharePoint site which has a switch for language conversion. In this case, do we have to maintain 2 switches, as Nintex form is hosted under a SharePoint site with master page, one for SharePoint site (header, top nav and quick launch), and another switch for Nintex form ?

Pls. suggest.

Reply