Rank: Newbie
Groups: Member
Joined: 6/14/2016(UTC)
Posts: 1
|
Hello,
Is there a way to manage stale UserData intelligently in the system? Every time a customer saves a design, we get a new Saved State, which is great because we can have a history of saved states. However, over time, this has grown to be 15GB on my system. There are some Saved States that are simply not necessary, and were superceded by multiple subsequent Saved States.
Is. there a way to manage the old saved states? In some cases, I need clients to be able to resume the last saved state for a particular item. In other cases, the saved states are disposable.Does Customers Canvas track a history of Saved States that are related to each other?
For instance, for Customer X (in their own UserData subfolder)
Job 1 - SavedStateID 12345 > 12346 > 12350 > 12360
Job 2 - SavedStateID 12370 > 12371
Job 3 - SavedStateID 12361
Is there any internal mechanism by which I can identify that 12345 12346 12350 and 12360 are related and I only need to keep the last 2 StateIDs? (Aside from me building something in my own database to manage this)
|
|
|
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 10/20/2015(UTC)
Posts: 52
Was thanked: 14 time(s) in 13 post(s)
|
Originally Posted by: dbrown@marketconnections.com  Hello,
Is there a way to manage stale UserData intelligently in the system?
Unfortunately, we don't have an algorithm which defines or manages state files somehow. It was assumed that customers take responsibility for all the logic of working with the state files. Please let me know if you have any other questions. Best regards, Kate
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.