Orphaned Objects

AFAIK, There is no way to differentiate the orphaned objects. but for each object we can see the dependents either at the time of publishing or saving. while adding them into the application and exporting them and importing into a new environment then you can see the dependents, and orphans will automatically import without errors, I know this is a very tedious job to find out the orphans. I agree with you for the suggestion.

Is there any way to find solution through appian java api ?

The tedious way to accomplish your goal is to add all objects in your environment to an application, export the application, and traverse the xml files to search for objects that are not referenced by any other object.

We are looking thru the API for possible solutions, we will let you know if we find anything.

What does "orphaned" mean in the context of the app? If you search for objects that are not referenced by other objects you will get, for example, all process models that are actions.
Is this part of DEV environment cleanup or something you are doing in PROD? I would highly discourage doing anything like this in PROD.

We are looking for objects that aren't referenced by any other objects across the entire platform that are included in the application. This is definitely something we would do in DEV. If this were part of the application export log or part of the dependencies check, it could be used to help ensure we aren't moving objects to higher level environments unnecessarily. I would have assumed the relationship between the record and action would create a dependency that could be identified in the XML for that record. I imagine it would take a combination of precedent and dependence checking to get the complete picture.

We are looking for objects that aren't referenced by any other objects across the entire platform that are included in the application. This is definitely something we would do in DEV. If this were part of the application export log or part of the dependencies check, it could be used to help ensure we aren't moving objects to higher level environments unnecessarily. I would have assumed the relationship between the record and action would create a dependency that could be identified in the XML for that record. I imagine it would take a combination of precedent and dependence checking to get the complete picture.

Hi, did you manage to find a better way of finding the orphan objects (other than the tedious way mentioned above)? I am also interested in knowing about this to solve a similar use case.