Jschonning/w 14245254

[jschonning-sf]

What does this PR do?

Adding a new flag, --allversions. This will migrate all versions of a component (omniscript, integration procedure and flex card).

@W-14245254@
@W-14245279@

[salesforce-cla]

Thanks for the contribution! Unfortunately we can't verify the commit author(s): Johan Schonning <j***@j***.i***.s***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, sign the Salesforce Inc. Contributor License Agreement and this Pull Request will be revalidated.

[agarcia-sf]

@jschonning-sf , I am not sure if this should be done as there is a catch here.

Once you insert a new OmniScript, the save hooks will calculate the new version so, if you have version 2, 3, 4 on the source, the target will be 1, 2, 3. While this might be good to have a consistent versioning, you need to let the customer know that there was a change of version that might not match. Also, the query needs to be modified to be sort by type, subtype, language, version.

[agarcia-sf]

@jschonning-sf , I am not sure if this should be done as there is a catch here.

Once you insert a new OmniScript, the save hooks will calculate the new version so, if you have version 2, 3, 4 on the source, the target will be 1, 2, 3. While this might be good to have a consistent versioning, you need to let the customer know that there was a change of version that might not match. Also, the query needs to be modified to be sort by type, subtype, language, version.

cc. @twu-sf

[jschonning-sf]

@jschonning-sf , I am not sure if this should be done as there is a catch here.
Once you insert a new OmniScript, the save hooks will calculate the new version so, if you have version 2, 3, 4 on the source, the target will be 1, 2, 3. While this might be good to have a consistent versioning, you need to let the customer know that there was a change of version that might not match. Also, the query needs to be modified to be sort by type, subtype, language, version.

cc. @twu-sf

So it seems that I can add the same version as the source have in the target. I could sort on version just to make it more bullet proof though. That way version 1->1 would happen automatically.

This will set the version of the source in the target.

mappedOsName = mappedOmniScript[OmniScriptMappings.Type__c] + '_' + mappedOmniScript[OmniScriptMappings.SubType__c] + (mappedOmniScript[OmniScriptMappings.Language__c] ? '_' + mappedOmniScript[OmniScriptMappings.Language__c] : '') + '_' + mappedOmniScript[OmniScriptMappings.Version__c];