Copy app data from one app to another | updating apps
Couple of items. Is there a way to copy the contents of one app and copy it (for example, files in a file library) and replicate it to a similar/same app in another workspace?
The goal is to have several apps, some with pre-existing or pre-configured content, published. I can then bring down both app & content to a new workspace.
But sometimes, I update content in one app after publishing it and want to copy it from app to app. Is this possible?
Also, we really need a way to update apps. Evolution of apps & workflow need to be supported better. Scenario: As new things come to light I someones update apps along the way, these updates I would like to push up to my published apps, either on an individual basis, or as a pack.
The workspaces that have previously grabbed that app are now out of date. We need an AppStore like (!) mark that signals an app is in need of an update/refresh, and we can then push it down.
If any of this is possible today and I'm not aware of how, please enlighten me.
Thank you!
-
I too would like to see app and app content updates possible as Mike requested.
Currently we have a workaround that is not very elegant, is limiting and sometimes breaks. What we did is create a private and public workspace for the same content we are working on. We always work on the content in the private workspace and every now and then we archive the apps in the public one then clone the private apps to it.
Justin's suggestion of simply making app content or "items" private until ready to publish would be a big step up. This way we could continue updating "item" content in one place/workspace whether it is private or has gone public. We would also like the option to control whether comments on published content that are made by members of the private portion, are private or public. Also the option to control the roles for access to the public content (view, modify, comment). In effect this would be a workspace that is private but can have a public appearance that reveals only specific 'items' and specific related comments that have been made public and their associated apps of course.
I think for our case, this is definitely a more elegant solution than maintaining multiple copies of the same app and content in different workspaces. It may not solve all of Mike's issues, and since I am posting on his initial post, I would just like to re-iterate that we could also benefit from what Mike describes, which I understand to be a kind of app and content updates mechanism.
Please sign in to leave a comment.
Comments
4 comments