Import Object as a new object in different appilication in same environment.

Question

I have list of objects I want to reuse in different application. How can I import object as new object with New Application Prefix. Duplicating each object will take time. My goal here is to make objects which are reusable for future.
Please let me know if more information needed.

Harshit Bumb (Appyzie) · Answer

No other way apart from duplicating all of these objects. To make it worse, there is no automated way to duplicate objects and you'll have to do everything MANUALLY

Mathieu Drouin · Answer

There is no automated way of duplicating objects in Appian AFAIK. Would suggest you make a feature request via Appian support.

Mike Schmitt · Answer

My suggestion: identify any objects you want to have as "global reusable" objects shared between different applications, and migrate them to a new, centralized application, folder structure, and naming convention (luckily these days renaming rules/constants is possible - in the old days this was a disaster). 
 As others have said, creating duplicates of everything is time consuming and a little bit wasteful (especially as it doesn't add any particular benefit). If you have 5 such objects it should take you 15 minutes. If you have hundreds, then that's quite a bit more of an effort, and whether you really want to undertake this will depend on how urgent it is.

davel001150 · Answer

There are pros and cons to all approaches. 
 Making bespoke versions of each object for each environment: Reinventing the wheel all the time, which is a huge waste of effort, but you keep track of your objects and don't have to worry about stomping on other people's toes. 
 Duplicating the objects you want to reuse and putting them in your application: Less time consuming, and you have objects you know work to start with, and they're now yours and if the original gets edited it won't break your stuff, you can edit it without breaking their stuff, but still largely time consuming. 
 Adding object to your app and leaving it alone after that: Pretty quick and painless, still some wasted time; but now you have to watch out for that object ever being edited. If they find a bug or fix something, or add features, it could break your app and not theirs (they code their app, the app it came from, around the change). 
 Leaving object where it is and using it: You don't need to do anything, but you're completely at the mercy of the owner of that object. Any changes, and you probably won't be notified, and there goes all your stuff. 
 Migrating to Global Reusable Objects library: Everyone knows this is the stuff that gets reused, everyone understands these don't get changed; no one breaks your stuff, you don't break others', however if there IS a bug or you DO need to improve it, you can't. You need to get approval from a committee first. Plus, if someone else needs changes, you have to go through all this crud making sure your app won't break for a change you don't even want. And it takes time to set up, and all of the objects have to be completely solid and generalized for common use. 
 All have good. All have bad. Choose good you like with bad you can live with.