0046168: Entity Replicator copy configs and others from 1 environment to another

Description

Entity Replicator copy configs and others from 1 environment to another

Steps To Reproduce

WHAT IS THIS?
* An utility in the Openbravo backoffice that allows to copy a record from any window or subtab from 1 environment to another
When you select a tab, the subtabs info is also replicated
* Replication means: create if uuid does not exist already, update if uuid exists already
* Simple button in backoffice able to run for 1 or several records selected in any backoffice window or subtab: in a popup, you select in which environments or environments you want to copy too
* But might be also an more general utility that can be talked by Process Request or external processes via API

CONFIGURATION
* Only need to enter the list of environments Name / URL that you want to be able to select in the popup
* For sure, user executing this utility must have the same rights / password (or maybe there could be an input in the popup to enter the password of the target environment)

WHY USEFUL?
* Copying Promotions definitions or OTF Rules configurations done in TEST: once validated in TEST, easily replicated in PROD and TRAINING without having to create them again, reducing manual errors
* Same for Touchpoint Types and their Payment Methods, or a complete configuration of a 1st store and terminal: helpful for Services and CSU
* Even copying complex entities between PRODUCTION environments like PROD <> PRODUNIT and being able to do cross store returns between stores in different PRODUCTION environments

Proposed Solution

* This tool will become some kind of a MUST for properly and efficiently managing big customers using several environments (PRE PROD / PROD UNIT / PROD)
* It is not trivial regarding uuids, since in many cases, for instance integrations of products in different systems, same product will have different UUID in M_PRODUCT_ID in TEST VS PROD, for instance
* We should be able to make it very user friendly of selecting one or many records in backoffice window
* Or we could define "Entities": for instance, an entity could be a whole new country configuration with its stores and touchpoint types and touchpoints (and all the required related entities sequence numbers, payment methods, etc...)
* Behind the scenes, the infrastructure of exporting/importing datasets could be re-used for that

Issue History
Date Modified	Username	Field	Change
2021-03-26 16:35	rafaroda	New Issue
2021-03-26 16:35	rafaroda	Assigned To	=> platform
2021-03-26 16:35	rafaroda	Modules	=> Core
2021-03-26 16:35	rafaroda	Triggers an Emergency Pack	=> No
2021-03-26 16:35	rafaroda	Tag Attached: NOR
2021-11-24 11:50	rafaroda	Steps to Reproduce Updated	View Revisions
2022-01-21 17:52	martinsdan	Issue Monitored: martinsdan
2022-02-01 08:07	alostale	Assigned To	platform => Triage Platform Base

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
There are no notes attached to this issue.