Hi fellow Personas users,
I am new to Personas development and have a question regarding normal sytem behaviour.
We have just deployed a trial set of Flavors to a QA environment. Initial effort is for 1 SMEN tran that contains launch buttons for 8 FLAVORS. When a subsequent change to a FLAVOR is imported into the QA system (eg VA01 ) the transaction for 'FLAVOR MAINTAIN' shows that the VA01 Flavor now exists as 2 seperate versions, each with a unique GUID.
This same system behaviour is seen in DEV where we develop flavours in a DEV/TEST client (120) and then export/import into the DEV transport client (110). The import to 110 creates a new GUID version of VA01. Then
This means that I need to unlink the old version from the system/group/user and then link the new FLAVOR to the required system/group/user combination. I can also then choose to delete the old version of the FLAVOR to avoid any confusion as to what is the latest version.
This same "duplication" of objects is also evident when transporting MEDIA files.
Is this standard behaviour for Personas, and if so, is it recommended that old versions should be retained for 2 or 3 versions to enable reversions in case of problems, or maybe never delete old versions.
Any advice would kindly appreciated,
Regards,
Neil.