You need to sign in to do that
Don't have an account?
GoForceGo
Packaging Value Add Apex Code....
How does one go about segregating value add in Apex/package based environment?
Here is my issue:
Let's say i define a custom object called Foo with attributes A,B,C,D.along with related business logic etc...
I package this as a "Foo package" and sell it as Foo Application.
I now want to build another application with object Zoo with it's own attributes.
However, Foo is related to Zoo and actually has a lookup field to Zoo! The moment, I add "Zoo" as a lookup field, to Foo, system automatically includes Zoo in the "Foo Package". Once Zoo is included, all the objects get pulled it and the whole thing becomes a mess - there is no way to disallow access to users once Zoo is installed.
Are there any suggestions/workarounds?
Here is my issue:
Let's say i define a custom object called Foo with attributes A,B,C,D.along with related business logic etc...
I package this as a "Foo package" and sell it as Foo Application.
I now want to build another application with object Zoo with it's own attributes.
However, Foo is related to Zoo and actually has a lookup field to Zoo! The moment, I add "Zoo" as a lookup field, to Foo, system automatically includes Zoo in the "Foo Package". Once Zoo is included, all the objects get pulled it and the whole thing becomes a mess - there is no way to disallow access to users once Zoo is installed.
Are there any suggestions/workarounds?
James
What might work is to deploy the Apex code separately. I don't want to deploy code from Eclipse, since I want to protect the IP.
I will have to see if I can package the code separately from the underlying objects.
I will have to play around with it.