How can we Club two Different Application which are built on different class Structure
We have a scenario where we want to club to different applications which are built on different class structure. We want to use some of the properties from one application to another application. can anyone has any approach how can we do it beacuse we are facing problem with the class structure.
I'm not sure I fully understand the question. Are you saying you have two applications on sharing the same PegaPlatform database, but built on different class structures? Or are you saying you have two completely unrelated PegaPlatform systems and you want them to share data? For the latter, I'd suggest you look into Federated Case Management (FCM). I think it sounds like you're asking about the former, so I'll address that.
What you might want to consider is creating a new application and inserting it as a shared layer underneath your current applications (i.e. they both become "built on" that). Then you can point your established classes to translation classes you create down there and any properties that need to be commonly available you move. Obviously, this is a lot more work for existing applications than it would be if this had been part of the design from day one, but if you do it right, any new applications you may choose to build can use the shared backbone to allow you to flexibility with your data, where appropriate.
As per your understanding we have two applications which are built on same pega platfrom but the only difference is the Class Structure which is completely diffrent for both the applications. There is no relationship betwwen the classes also. The only similarity is that we have the same database for both the applications. Now what excatly we wnat is suppose there is a case in first application , now i want to search that case from the second application and i want to display all the information in the second application's users portal. Did you get my point now.
First, do your users have access to both applications? You are going to have problems if they can't use entire classes that your data is built upon. I don't think you can do an Obj-Open-By-Handle on an object of a class you have no access to. Anything you do at this point, short of a complete refactor is going to be suboptimal. I'm not sure if you can create an application that is built on one and containing the necessary rulesets of the other to put it all together, but you might try that. You will definitely need to search for any namespace collisions that might result in an unexpected rule being run and address them. Also, if you want to limit what your users can do with the data from the other application (read only? full updates?) you'll need to account for that in your testing/customization.
A second option would be to make an application that contains the necessary classes and properties from your "second application" and add it as a built on application to your "first application". That would allow you to open the objects and review them, but not actually perform any of the work since the flows, activities, harnesses, etc are not present.
We need some functionality to be used in multiple applications. The applications are built on different frameworks and frameworks in enterprise application. Layer which is common between applications is division layer.
In case rules in framework need to access the division layer functionality, division rule set need to added as prerequisite to framework.
Is it advisable to put division layer as a prerequisite for framework rule set? Is there any other approach to handle above mentioned scenario?