DSauve
Legendary Poster
I just noticed on the JDE Update Center that TR 9.2.5.0 GA was posted yesterday.
Are there any details of the "Development Client Simplification" in the 9.2.5.0 announcement? Removing the local database is all I can see. So where does an object go when you check it out and make changes?
Thanks Don. That is what I found, but didn't get much technical info out of it.Check out this document: https://docs.oracle.com/cd/E84502_01/learnjde/announcements.html
There are a new set of User Spec Repository (USR) Tables that will reside in the Central Objects Datasource. The Key on these tables will be USER ID, so each user will have their own spec records. There might be some sort of temp folder and physical footprint on the actual Development Client while you are working with the various Development Tools (FDA , RDA etc), but it will save changes back to the USR. When you do a check-in it will move from the USR to the CO Tables. Will have more details once we test this out.
Hi Craig, no published documentation yet, just from the virtual Infocus sessions I attended. If you have a quest membership you should be able to listen to the session replay. I think the official documentation should make its way to learnjde soon.Thanks! Any place you found documentation for that?
There are a new set of User Spec Repository (USR) Tables that will reside in the Central Objects Datasource. The Key on these tables will be USER ID, so each user will have their own spec records. There might be some sort of temp folder and physical footprint on the actual Development Client while you are working with the various Development Tools (FDA , RDA etc), but it will save changes back to the USR. When you do a check-in it will move from the USR to the CO Tables. Will have more details once we test this out.
Hi Brian,
It should only be one user/workstation at a time, since it's basically a check out. My concern is the serialized objects. If they don't exist locally, the developer's changes would be shared with others as he/she works.
Craig
We use essential cookies to make this site work, and optional cookies to enhance your experience.