-
Type:
Story
-
Status: Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: 7.4.3.5 CE GA5, 7.4.13 DXP U1, Master
-
Component/s: Workflow
-
Labels:
-
Epic Link:
As an Operations Manager, I want to be able to localize my workflow process so that users will be able to track their progress and interact with the workflow in their preferred language.
Design Deliverables
Context
Currently it is only possible to localize the name of a workflow. With the migration to React we would like to expand this functionality to localize all aspects of the workflow that are viewed by the end user. This would include the name of each node, the name of each transition and the notification generated by the workflow.
These localized values will be viewed by the end user in the Workflow Tracker (LPS-131424), Workflow Metrics (LPS-86637), My Workflow Tasks, etc. The language displayed to the end user will be determined by the language the user has selected as their default, or by the page language (if the workflow / workflow metrics are being displayed on a page).
With this story we are delivering the MVP for localizations. It was decided by the team to tackle this before migrating nodes so that the foundation would be set for localization before they began the migration. As such, the user will only be able to localize the title of the workflow for now. As we migrate the notification property, transitions and each node, they will all be able to be localized because of the ground work accomplished in this story.
In this Story's scope, users should be able to:
- Add support for multiple languages within the React Designer.
- Localize the name of the workflow.
Not in the scope:
- Localize the name of the workflow nodes or transitions.
- Localize Workflow Notifications (this will be implemented in LPS-139562).
- Add localization for properties not seen by the end user.
Acceptance Criteria
Given that a user is defining a new workflow process using the React Designer,
when he finishes modeling the process flow,
then he should be able to add support for translations to multiple languages.
Given that a user is defining a new workflow process using the React Designer,
when he adds a translation to a new language,
then he should be able to localize the workflow title.
Definition of Done (DoD):
- All Acceptance Criteria were passed;
- Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
- Code with peer review completed;
- Validated by QA, Product Designer and/or PM;
- No critical bug related to Story scope (ex.: similar of FP4, FP5);
- Make sure that all system documentation were updated (if necessary)
Make sure that it has the extensions points needed to allow GS and customers to customize the feature (If applicable)
- depends on
-
LPS-129925 Create basic structure for New/Edit Workflow page
-
- Closed
-
- is related to
-
LRDOCS-10216 Be able to localize my workflow process
-
- Closed
-
- mentioned in
-
Page Loading...
1.
|
[PM] Acceptance Criteria | LPS-138348 |
![]() |
Closed | Joseph Pak | |
2.
|
[DS] Mockups | LPS-138382 |
![]() |
Closed | Arthur Coninck | |
3.
|
[FE] Apply the localization component | LPS-141434 |
![]() |
Closed | Product Team Zulu | |
4.
|
[QA] Manual validation - Round 1 | LPS-142258 |
![]() |
Closed | Lucas Falcao |