Cloud graphic versions - scenarios and examples

Scenario / Steps

Expectation

Scenario 1:

P2_New creates S3.

P1_Old attempts to edit S3.

S3 is saved in newer graphic version and hence it cannot be edit, embed, or download in older version.

P1_Old receives a message stating that S3 is saved in newer version and cannot be opened.

Scenario 2:

P2_New opens S2.

P2_New saves S2 in Cloud.

Then, P1_Old attempts to open S2.

S2 created in older graphic version can be opened and saved in the newer graphic version.

S2 is saved in newer graphic version and hence it cannot be edit, embed, or download in older version.

P1_Old receives a message stating that S3 is saved in newer version and cannot be opened.

Scenario 3:

P1_Old saves S1 and S2, where S2 is embedded in S1

P2_New saves and updates only S2.

P1_Old attempts to edit S1.

S1 is opened because it is still the same version in P1_Old.

The embedded S2 will fail to load.

Scenario 4:

P2_New creates a new S4 in Cloud.

P2_New embeds S1, S2, and S3 in S4.

S1 is in older graphic version but still can be loaded in S4 (newer version).

S2 and S3 can be embedded because they are the same graphic version as S4.

Scenario 5:

P1_Old creates a new S5 in Cloud.

P1_Old embeds S1, S2, and S3 in S5.

S1 can be embedded because they are the same graphic version.

S2 and S3 cannot be embedded due to newer version.

Scenario 6:

P1_Old download S3.

S3 cannot be downloaded because it is in newer graphic version.

Scenario 7:

Cloud repository has a graphic S3 which is in newer graphic version.

P1_Old attempts to upload a graphic with same name S3.

By selecting Option 3, the graphic can be overwritten.

Scenario 8:

P2_New has a graphic S8.

P1_Old creates locally S8, S9, and embed S8 in S9.

P1_Old uploads S9 to Cloud.

S9 is uploaded to Cloud.

S8 is prevented upload because a newer version exists in the Cloud. By selecting Option 3, the content can be overwritten.